Privacy Policy
This policy explains how the Dryv website and iPhone beta handle information, including website visits, messages, search, route planning, maps and turn-by-turn navigation.
Who Is Responsible
Yves Sibony operates the Dryv website and is responsible for the website data described here. For privacy questions or requests, write to support@dryvroutes.com.
Summary
Website audience measurement
We count visits, page views, returning browsers, roadbook access and clicks towards TestFlight to understand use of this website. Website measurements are kept separate from app activity, contact messages and mailing-list subscriptions. We do not use them for advertising or campaign attribution.
A random browser identifier expires after 90 days; returning does not extend it. A visit ends after 30 minutes without a measured page view. Temporary visit and duplicate-submission records are deleted after 48 hours. Aggregate totals are kept for up to 12 months. Reports use fixed periods and withhold sparse breakdowns. A browser is not necessarily one person.
Turn this off to stop audience collection and clear its browser identifiers. Your choice stays off until you enable it again, provided your browser retains the preference. Clearing browser storage can remove it. This does not affect your access to the website, PDFs or the app.
Epoqu’Auto page counter
For /epoquauto, we keep a separate daily total of page requests to estimate use of the link shared at Epoqu’Auto. This counter stores only the UTC date, the page name and the total, for up to 12 months. It does not read cookies, use browser identifiers or retain individual requests, network addresses or referrers. Repeat requests and automated requests can be included, so it is not a count of people or QR scans.
We do not run browser audience measurement on this page or connect its counter to later page views, PDF access, TestFlight clicks or subscriptions. The anonymous request total continues regardless of the browser audience preference above. Other pages retain their ordinary audience settings. Hosting providers still process the technical information described below to serve and secure the website.
Website messages and updates
Contact messages are sent to support@dryvroutes.com through Mailjet. Their contents are removed from the delivery queue when the receiving mail server accepts the message. Failed or uncertain deliveries remain available for follow-up for at most 30 days. Messages received in our inbox are separate from this temporary queue. Contacting us does not subscribe you to updates.
Updates require confirmation by email. Unconfirmed requests expire after 48 hours. Confirmed subscriptions are managed through Mailjet; each update includes an unsubscribe link. We keep the confirmation record while you are subscribed and remove it within 48 hours after Mailjet reports that you have unsubscribed or can no longer receive updates. Mailjet may retain suppression records to prevent further unwanted email. We disable email-open and email-click tracking.
To prevent form abuse, we use keyed hashes of email and network addresses in short-lived rate-limit counters. These counters expire at the end of the hour or day and are cleared during scheduled maintenance. They are separate from audience measurement.
Where website information is stored
Cloudflare hosts the website databases: audience measurements in one database, and the contact delivery queue, pending subscriptions, confirmation records and abuse counters in another. The beta feedback form uses a separate Cloudflare database. Mailjet sends contact and confirmation emails and holds the confirmed updates list. Feedback that has been reviewed also has a local support record.
Contact messages and email copies of questionnaire answers are forwarded to Yves Sibony's Gmail inbox so we can read them, reply and follow up. Google therefore processes the contact details and message contents in those emails. Replies may come from sibonyves@gmail.com. Contacting us does not add your address to the Mailjet updates list.
We keep correspondence needed to answer and follow up on enquiries, separately from the temporary delivery queue. We review closed conversations 12 months after the last reply and delete those no longer needed, keeping unresolved matters and necessary business records. Deleting a queue entry does not delete that correspondence.
After an unconfirmed request expires, we also check its Mailjet recipient record. We remove records created only for those confirmations, while preserving subscriptions, unsubscribe protection and records needed for other correspondence. We keep the address and delivery references while cleanup or a necessary review is pending. Mailjet anonymises erased recipients immediately and completes deletion within 30 days. Its separate delivery statistics can remain for 90 days on our current plan.
Cloudflare database recovery history can retain deleted records for a further 7 days on its Free plan or 30 days on its Paid plan. Those recovery copies are not used for audience reports or mailing lists. Deletions and unsubscribes must be reapplied before a restored database is put back into service.
The website databases are stored in the European Union. This does not mean all processing stays there: Cloudflare operates a global network, and provider support and email services may process data outside the European Economic Area. Cloudflare and Mailjet publish data-processing terms and transfer safeguards, including standard contractual clauses. Our support inbox uses consumer Gmail, not Google Workspace. Google's handling of information is described in its privacy policy.
Hosting and email providers also process technical information needed to deliver and secure their services. This includes network addresses and delivery or security logs. These records are separate from our audience statistics; we do not use them to identify visitors for marketing.
Why we use website information
Subscriptions to updates rely on your consent, which you can withdraw through the unsubscribe link. We rely on legitimate interests to answer enquiries, review feedback, protect the forms from abuse and understand use of the website through limited audience statistics. Providing contact details in the beta feedback form is optional. The contact form needs an email address so we can reply.
iPhone beta
- Dryv does not require an account.
- Dryv uses location to provide search results, routes, and navigation.
- Search queries are not stored as standalone search history.
- Route and navigation data may be cached to make routing and rerouting faster and smoother.
- Eligible navigation drives may contribute exact locations and UTC timestamps to improve future ETA estimates. These traces are stored without a stable account, installation, client, or device identifier.
- Dryv records limited beta-use events and optional route ratings to understand how the beta works and improve route quality.
- Beta feedback is optional. If you answer the feedback form, Dryv stores your answers and any contact method you choose to provide.
- Some older beta builds may still send limited startup, map-rendering, navigation, and off-route diagnostics while those builds remain supported.
- Dryv does not sell personal information.
Information Dryv Processes
Location
With your permission, Dryv processes location to show your position, bias search results, calculate routes, follow progress during turn-by-turn navigation, and support rerouting. Route and navigation caches may contain route endpoints, progress, geometry, and related navigation state. Eligible navigation drives may also contribute the measured-location trace described below.
Search
Dryv processes search text and optional map or location context to return relevant places, roads, areas, and route destinations. Search queries are not stored by the server as standalone search history. Recent searches may be stored locally on your device to support autocomplete.
Routing and Navigation
Dryv processes route requests, route geometry, route alternatives, route progress, and navigation state to provide routes and turn-by-turn navigation. Route data may be cached to provide faster routing. Navigation data may be cached to provide smoother navigation and rerouting.
Driven-Route Data for ETA Improvement
When active navigation records enough real movement to be useful, Dryv may retain the measured location updates already delivered to the navigation system. A trace can include exact latitude and longitude, UTC date and time, horizontal accuracy, measured speed and course with their reported accuracies, an indication that a sample was simulated, and compact snapshots of the initial route and later reroutes. Dryv collects this information only to derive better future road, turn, and surrounding-context travel-time estimates. It is not used to create a user-facing journey history, for advertising, or for cross-app tracking.
Each trace has a random identifier used only for that drive. The public gateway may use the app's normal authentication and client identifier transiently to protect the upload and apply quotas, but removes that identity before analytical storage. Dryv does not store an account, installation, client, device, advertising, or App Attest identifier with the trace, and does not join driven-route traces to the separate product-use event ledger.
Anonymous App Identifier
Dryv may use an anonymous app install or client identifier to keep routing and navigation sessions working across requests. This identifier is not an account and is not intended to identify you by name or email address.
Beta Usage Measurement and In-App Route Feedback
Dryv records limited product-use events about app opens, permission state, route-planning milestones, route-option review, route choice, map and sheet interactions, and navigation progress milestones. These events may include timestamps, app version and build, random session or interaction identifiers, route and request identifiers, selected option, interaction counts and durations, navigation distance or progress totals, and reroute count. The product-use event ledger does not contain search text or raw location samples. Submissions use the anonymous app client identifier described above, which is stored by the analytics system as a protected digest rather than as an account identity.
If you rate a proposed route in the app, Dryv stores the rating, selected reasons, any optional detail you type, and technical context needed to associate the rating with that proposed route. To understand route feedback, Dryv may temporarily retain the corresponding exact route snapshot, including its endpoints and geometry. Dryv uses this information to understand beta usability and route quality, not for advertising or cross-app tracking.
Beta Feedback
Dryv may invite beta users to answer an optional feedback form after enough local app use. The prompt counters are stored on your device and are not uploaded by the prompt itself. If you submit the form, Dryv stores your selected answers, free-text answers, form language, submission time and how the form was opened. If opened from the app, it also stores the platform, app version/build and a random one-time feedback session identifier. We do not copy the page URL, referring URL, browser header or inferred country into the questionnaire record or its email. The session identifier is used only so the app can confirm that the form was successfully submitted before resetting local feedback prompt counters.
The feedback form may ask for an optional contact method. You can leave it blank. If you provide one, Dryv may use it only to follow up about your feedback or the beta.
Diagnostics and Server Logs
Dryv may process technical logs needed to operate the beta, investigate bugs, prevent abuse, and maintain security. Logs may include request times, endpoint paths, status codes, IP addresses, app build or client metadata if sent by the app, and error information.
Some older beta builds may upload app-status, startup, map-rendering, navigation-session, and off-route diagnostics while those builds remain supported. Those diagnostics may include app and route identifiers, route progress, matched or off-route state, relevant active-navigation location samples, accuracy, speed, course, timestamps, and technical status or error information. Build 13 and later do not upload this generic diagnostic history; they use the purpose-limited driven-route data described above instead. Dryv does not use diagnostics for advertising or tracking.
Third Parties and Data Sources
Dryv uses Cloudflare for DNS, HTTPS, public traffic routing, and static website hosting. Dryv also uses Cloudflare to receive optional feedback form submissions, store the questionnaire answers, and send feedback notifications to Dryv support. Dryv is distributed through Apple services such as TestFlight and App Store Connect.
Dryv uses geographic and map-related data derived from sources including OpenStreetMap, Copernicus programme data, CORINE Land Cover, and the National Land Cover Database. These datasets are used to build Dryv's map and routing data; Dryv does not send your live app requests to those data-source projects.
The app uses MapLibre to render maps on device. Dryv may use sources such as Wikimedia, Wikidata, Wikipedia, and Panoramax to provide imagery, place information, and route context when those features are used.
During the current beta, route explanation and related inference may use a local Qwen model running on Dryv-controlled infrastructure. Dryv does not send these prompts to a hosted third-party large language model provider unless this policy is updated.
Retention
Search queries are not stored as standalone search history. Route cache, navigation cache, and operational logs are kept only as long as needed for beta operation, debugging, security, and performance. Cache contents may remain until they expire, are invalidated, or are cleaned during maintenance. Legacy diagnostic uploads from older beta builds are normally pruned after about 30 days.
An unprocessed driven-route trace, or one whose processing failed, may be retained without a fixed time limit so that the measured drive is not silently lost. Once Dryv has validated the complete trace and durably produced acceptable road, turn, and surrounding-context observations, it deletes the raw point-by-point trace and every managed copy. Failed or unvalidated processing does not trigger deletion. Derived timing and quality observations may persist across future map and ETA-model generations, but they do not retain the original GPS points or a client identity.
Detailed beta-use events and in-app route ratings are retained for up to 13 months, after which small-group-protected aggregate counts may be kept for longer-term product analysis. A route snapshot without feedback is normally pruned after about 24 hours. A snapshot associated with route feedback may be retained for up to 90 days. Local events waiting for a successful server acknowledgement remain on the device within a bounded queue and are deleted after acknowledgement.
Questionnaire answers and any contact details you provide are kept in Cloudflare D1 for 12 months from submission, then removed by daily cleanup. If an unresolved support issue still needs the submission, we retain it until that issue is resolved. The feedback emails remain in our Gmail support inbox so we can read them, reply and follow up. Reading or replying to an email does not delete the structured answers in D1. Inbox correspondence is reviewed separately; messages needed for an ongoing conversation are kept. These records are separate from anonymous website audience measurements.
Your Choices
For website information linked to you, you may request access, correction or deletion, restriction of processing, and portability where applicable. You may object to processing based on legitimate interests and withdraw consent to updates at any time, without affecting earlier lawful processing. Contact support@dryvroutes.com. You may also lodge a complaint with the CNIL or your competent data protection authority. Anonymous totals cannot be traced back to your email address.
You can deny or revoke Location permission in iOS Settings. Some Dryv features, including turn-by-turn navigation and location-aware search, require location access to work.
Because Dryv does not use accounts, there is no account to delete. If you want to ask about data associated with your anonymous app identifier, contact support.
Feedback questions are optional. If you submit feedback without a contact method, Dryv will not be able to follow up with you directly about that submission.
Security
Dryv uses HTTPS for public app traffic and limits public access through a gateway that exposes only the beta app endpoints. Accepted driven-route files are encrypted at rest, and raw access is restricted to the automatic ETA-processing path and explicit audited operator access. No method of transmission or storage is perfectly secure, but Dryv is designed to keep the public beta surface narrow.
Age and Driving
Dryv is not directed to children under 13. Dryv's driving and turn-by-turn navigation features are intended for licensed drivers or people who are otherwise legally allowed to operate a vehicle in their location.
Changes
This policy may be updated as the beta changes, especially if telemetry, accounts, or additional third-party services are introduced.
Contact
For privacy questions, contact support@dryvroutes.com.