Information We Process

This policy explains what information Si Driver processes, what is stored, and what may be shared with third-party services, based on how the application is actually built. It covers: your driver account, delivery itinerary screenshots you upload, the route information extracted from them, gate/access code data submitted through the Gate Code feature, and the route and access information used while you drive a route.

Driver Accounts and Sign-In

Si Driver uses driver accounts. You sign in with your email address and a one-time code sent to that email; sign-in is provided by Supabase Auth. Anyone with a verified email address can create a driver account this way — a new account becomes an active driver account automatically, unless it has been suspended.

For your account, Supabase Auth stores your email address and your sign-in sessions. Si Driver’s own driver record stores only your account identifier, your account status (for example active or suspended), your role, and when the record was created and last updated. Your status and role are set by Si Driver’s server, never by the app on your device.

Protected driver features — including Gate Codes and access information for your stops — require you to be signed in. Each request is checked on Si Driver’s server, and signing out ends that sign-in session on the server, not only on your device.

Delivery Itinerary Screenshots

You may upload delivery itinerary screenshots so Si Driver can extract your route. Uploaded screenshot image data is transmitted to OCR.Space, our OCR (text-recognition) service provider, solely to extract the text from the image.

Si Driver does not intentionally persist the uploaded screenshot image file after OCR processing completes. On your device, the screenshot’s object URL/blob reference and preview are revoked and cleared once processing finishes — including when processing fails, not only when it succeeds.

Screenshots are not stored in Supabase Storage by Si Driver, and they are not stored as image, base64, or blob data in Si Driver’s local storage on your device. We do not control, and cannot make claims about, how OCR.Space itself handles or retains data once it receives it — that is governed by OCR.Space’s own privacy practices.

Extracted Route Information

Once a screenshot is processed, the extracted route information — delivery addresses, stop order, apartment/unit information where present, and route-analysis results such as mileage, driving-time, and estimated finish time — is used to build your current route.

Delivery addresses may also be transmitted to OpenRouteService/HeiGIT as necessary for geocoding and route/mileage calculation.

Gate Codes

Gate/access code information you intentionally submit through the Gate Code feature is stored in Si Driver’s Supabase database, so it can be found by other drivers. Depending on how a code is submitted, this may include: the address, the gate/access code, an optional note, its working/broken status, and the date it was added.

Only submit gate or access information you are authorized to use for legitimate delivery or access purposes.

Route Sessions and Access Information

While you drive a route, Si Driver can show access information (for example gate, door, or call-box details) for your current stop and your next stop. To do this, the server keeps a short-lived route session linked to your driver account. For each stop it stores an opaque stop identifier and a one-way fingerprint (a cryptographic hash) of the stop’s address — not the address text itself. A route session is active for at most 24 hours.

Each time access information is shown to you for a stop, the server records that access: your driver account, the route session and stop, whether information was found, the identifiers of the matched address and place in Si Driver’s address database, which access records were returned, and the time. This record does not contain the access codes or notes themselves, or the address text.

Third-Party Services

Si Driver relies on the following categories of third-party services to operate:

• OCR.Space — processes uploaded screenshot images to extract text.
• OpenRouteService/HeiGIT — processes delivery addresses to calculate geocoding, mileage, and driving time.
• Google Maps and Apple Maps — when you choose to open a route, address/route information is passed to them through the navigation URL, sent directly from your device.
• Supabase — provides sign-in (Supabase Auth, including sending your one-time sign-in code by email) and stores Si Driver's database: driver accounts, the Gate Code database, access information, and route sessions.
• Vercel — hosts and runs the application.

Each of these third-party services processes information according to its own privacy policy. We do not make claims about how long OCR.Space, OpenRouteService/HeiGIT, Google, Apple, Supabase, Vercel, or any other third party retains data, as we have not independently verified that from their current policies.

Local Device Storage

Si Driver uses your browser’s local storage to keep your current route available on your own device — so it remains visible if you navigate to another part of the app, or close and reopen your browser — without needing to re-upload or re-scan. This locally stored data includes the extracted addresses, route-analysis results, and any matched gate codes for your current route. It does not include screenshot image, base64, or blob data.

When you sign in, your sign-in session is also kept on your device so you stay signed in: in your browser’s local storage on the web, or encrypted with the Android Keystore in the Si Driver Android app. It is removed when you sign out. Access information shown for your stops is kept only in memory while you use it and is not written to your device’s storage.

This local data stays on your device until you clear it (using the “Clear Route” option), start a new scan, or clear your browser’s site data. Si Driver’s server does not store your route’s address list or route-analysis results; it keeps only the route session and access records described above.

Data Retention

We retain information only as follows, based on how the Service is actually built:

• Delivery itinerary screenshots: not intentionally persisted by Si Driver after OCR processing completes.
• Extracted route information: kept in your browser's local storage until you clear it, start a new scan, or clear your browser's site data.
• Gate Codes: remain stored in Supabase, since they are intentionally part of the shared Gate Code database.
• Driver account: your Supabase Auth account and Si Driver driver record are kept while your account exists. Deleting the account also removes your driver record and your route sessions.
• Route sessions and access records of what was shown to you: kept in Supabase, without a fixed deletion period.

We do not apply a fixed deletion period to this data beyond what is described above, and we do not control or guarantee when any third-party service deletes data it has received.

Security

We use reasonable technical measures designed to protect information handled by Si Driver. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

User Choices / Data Deletion Requests

You can currently:

• Sign out at any time, which ends your sign-in session on the server and removes it from your device.
• Use "Clear Route" on the Route page to remove your current route from local storage.
• Clear your browser's site data at any time to remove anything Si Driver has stored on your device.

There is currently no in-app option to delete your driver account. Questions about your account can be sent to the contact address below.

There is currently no user-facing option to delete an individual gate code you or another driver submitted, since Gate Codes are shared, community-contributed reference data.

Children's Privacy

Si Driver is designed for delivery drivers and is not intended for use by children under 13. We do not knowingly collect information from children under 13.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Continued use of Si Driver after changes take effect constitutes acceptance of the updated policy.

Contact

Questions about this Privacy Policy can be sent to support@appaidriver.com.