DropVera Privacy Policy

Effective October 15, 2026

This policy describes the DropVera mobile application and related support pages operated by DropVera LLC, including service availability in the United States and Australia.

Information DropVera processes

• Account data: email address and authentication/session identifiers.
• Driver settings: optional home market, earnings targets, mileage preferences, vehicle label/type, efficiency, fuel/electricity price, and vehicle-cost assumptions.
• Offer and shift data: payout, miles, time estimates, costs, offer decisions, gross earnings, mileage, and driver-entered shift costs.
• Private delivery actuals: optional pickup-wait time, drop-off time, and drop-off difficulty saved for an accepted offer so DropVera can improve that driver's future estimates. These actuals stay private to the account and are not added to Community aggregates unless the driver separately submits Community feedback.
• Private trip records: optional trip date, mileage, business/personal/commute classification, purpose, origin/destination text, vehicle label, notes, and retained edit history.
• Actual expense records: optional expense date, amount, category, merchant, and notes.
• Receipt photos: optional user-selected receipt images uploaded to private Supabase Storage and linked to the associated expense/account.
• CSV imports: validated supported trip/completed-shift record fields are imported to the account; the original CSV file is not stored as an uploaded account file.
• Community contributions: structured pickup and eligible shared-destination reports, ratings, wait/drop-off times, issue tags, and optional notes.
• Community searches and place-directory data: search terms and eligible shared-place directory fields.
• Private driver memory: customer/delivery experience notes linked to the submitting driver and not published as customer profiles.
• Support data: support request text and optional contact email. DropVera derives a SHA-256 network fingerprint for support-form abuse prevention; the rate-limit table stores the hash rather than the raw network address and removes limiter rows after 48 hours.
• Service data: subscription/customer entitlement status, security/audit records, technical service logs, and privacy-minimized product-usage events used to measure aggregate activation, retention, and Plus purchase/restore health. Product-usage events are limited to an account identifier, allowlisted event name, app/build label, platform, country code, and timestamp; they do not include offer values, earnings, precise location, customer memory, search terms, support text, or other free-form payloads. Logs may include IP address, IP-derived approximate city/region, device/browser or anti-abuse request fingerprints, request path/search parameters, response status, and timing metadata.
• Free-tier advertising data: for eligible Free-tier advertising, Google Mobile Ads / AdMob and Google's User Messaging Platform may process IP-derived general location, device or app identifiers, ad impressions/interactions, and technical diagnostic or performance information to deliver and measure ads and prevent fraud or abuse.

On-device features

Offer screenshot OCR: user-selected screenshots are processed on-device to prefill editable offer fields. DropVera does not upload or store the screenshot through this OCR feature.

Optional automatic mileage: location permission is requested only after a driver explicitly enables Automatic mileage during an active shift. Precise location samples are processed on-device, including in the background when needed for the active tracking session. Walking-speed movement is filtered out. DropVera does not upload or retain a route history through this feature; the device keeps the running total and latest accepted point needed for the next distance segment. Only aggregate mileage is saved with the shift. Tracking stops when disabled, the shift ends, or the user signs out.

DropVera does not send precise Automatic-mileage coordinates, private customer notes, offer details, shift earnings, or community report text to AdMob as custom targeting data.

Advertising and privacy choices

DropVera may display Google AdMob banner advertising to eligible Free users on approved non-driving screens. DropVera suppresses its banner placements while a shift is active, on the Offer Analyzer decision flow, and while an active DropVera Plus entitlement is present.

The current integration requests non-personalized banner ads and uses Google's User Messaging Platform to gather applicable privacy choices before eligible advertising starts. Non-personalized advertising can still involve processing such as IP-derived general location, device/app identifiers, ad interactions, diagnostics, analytics, and fraud-prevention signals.

Where Google's privacy options are required, DropVera exposes Ad privacy choices in Profile so the user can revisit applicable choices. Platform- and region-specific options may differ.

DropVera does not sell personal information to advertisers. DropVera does not intentionally use account records, profitability history, private driver memory, precise mileage coordinates, trip/expense records, receipt photos, or community report text to build custom advertising audiences.

Approximate location and search metadata

An optional Home market is stored with the user profile. Normal online requests generate security/operations logs that may retain IP address, IP-derived approximate city/region, and request search parameters. Community search terms may therefore appear in service logs. In an ad-enabled Free build, Google Mobile Ads may also process IP address to estimate general location for advertising, analytics, and fraud-prevention purposes.

How information is used

DropVera uses data to authenticate accounts, personalize profitability estimates, learn from a driver's own private delivery actuals before falling back to eligible Community estimates, track shifts and mileage, maintain private trip/expense/receipt records, import and export supported records, return community search results, operate privacy-thresholded community intelligence, measure aggregate product activation and retention, prevent abuse, respond to support requests, check or restore subscription entitlement status through RevenueCat, process purchases when checkout is enabled, troubleshoot errors, secure the service, and — for eligible Free-tier users in an ad-enabled build — deliver and measure advertising subject to applicable privacy choices.

Service providers and disclosure

DropVera uses providers needed to operate, secure, distribute, and monetize the service, including Supabase and hosting/network infrastructure for backend, authentication, database, and private receipt storage; Apple and Google for app distribution and store billing; RevenueCat for subscription/entitlement synchronization when configured; and Google AdMob / Google Mobile Ads and User Messaging Platform for eligible Free-tier advertising, privacy controls, ad measurement/analytics, and fraud prevention when ads are enabled.

Google documents that its Mobile Ads SDK may process IP address, user interactions, diagnostic/performance information, device/app identifiers, and advertising data. The exact data available can depend on platform capabilities, privacy choices, and the final production configuration.

Australian users, privacy requests and overseas processing

DropVera LLC is based in the United States. Australian user information is therefore likely to be processed outside Australia. DropVera's primary Supabase backend project is hosted in Canada. Other service providers, including Google, Apple, RevenueCat, and their subprocessors, may process information in the United States and other countries where they operate. Canada and the United States are the main identified overseas processing locations for the current service configuration, although provider infrastructure and subprocessors can change over time. Where Australian privacy law applies, DropVera will take reasonable steps required by that law in relation to applicable overseas disclosures and provider arrangements.

Australian users may ask to access or correct personal information associated with their DropVera account, subject to applicable legal exceptions. Use DropVera Support or email support@dropvera.app. DropVera may need to verify account ownership before providing or changing account information.

To make a privacy complaint, contact DropVera Support and describe the concern and the account/contact information needed to investigate it. DropVera will review the complaint and respond within a reasonable period. If Australian privacy law applies and you remain dissatisfied after giving DropVera a reasonable opportunity to respond, you may also have the right to contact the Office of the Australian Information Commissioner.

Community privacy

DropVera does not intentionally publish individual customer profiles. Raw customer/delivery feedback is private to the submitting driver. Shared destination intelligence is limited to eligible shared/public-facing or multi-unit places. Single-family/private residences are not eligible shared-destination profiles. Shared aggregates are withheld until minimum contributor thresholds are met.

Do not submit customer names, unit numbers, gate codes, phone numbers, email addresses, order numbers, or other unnecessary personal information in community reports.

Retention and deletion

Account-owned operational data is generally kept while the account is active and is removed or de-identified through account deletion, subject to security, fraud-prevention, legal, advertising/transaction-record, and other required retention obligations. De-identified shared-place directory records and aggregates may remain because they describe shared places rather than an individual account.

Support requests may be retained as reasonably needed to resolve the request, prevent abuse, document privacy requests, or meet legal obligations. Separate support rate-limit fingerprints are retained for no more than 48 hours.

Deleting a DropVera account removes account-owned application records, including associated private receipt objects, subject to provider/legal retention obligations. It does not itself cancel an Apple App Store or Google Play subscription; manage subscription renewal through the applicable store.

You can permanently delete your account inside the app or through the web deletion portal.

Your choices

Automatic mileage, trip/expense records, receipt photos, CSV import, Community contribution, and the local daily shift reminder are optional. You can use manual mileage without granting location access. Advertising/privacy choices are presented through the Google consent flow where applicable and can be revisited from Profile when the provider requires a privacy-options entry point.

Use DropVera Support or email support@dropvera.app for privacy questions or requests.