Privacy policy

Mehmet Erturk, trading as Drover, is the data controller for information collected directly through this website, beta list, support, and Drover service operations. Contact: admin@newdrover.com.

Website and beta list

When you join beta updates, we collect your email address, submission time, browser user-agent, country code supplied by Cloudflare, referrer, website origin, product name, and a random submission identifier. We use this to operate the beta list, distinguish Drover from other products using the same private Sheet, prevent or diagnose intake problems, and send requested product updates.

Your browser stores a masked email hint and join time in local storage so the page can remember that it accepted your submission. It is not used to track you across sites.

Drover app and host

Drover must process paired-device keys and identifiers, verified host identity, Herdr session topology, connection state, and the terminal-backed content needed to show and control your session. This data is used to provide the product, authenticate the paired endpoints, and protect commands from misrouting.

Connection and push metadata

Cloudflare services may process opaque host/device routes, public network addresses, connection timing, region, encrypted signaling, short-lived relay credentials, and encrypted traffic. Push routing may process an APNs token/environment, opaque identifiers, preference state, and a RevenueCat entitlement identity. Push payloads are designed as generic wake hints; they do not include commands, paths, hostnames, or terminal content.

Purchases

Apple processes App Store purchases and billing data. RevenueCat processes anonymous App Store entitlement identifiers and subscription status so Drover can determine access to Pro capabilities. Drover does not receive your full payment-card number.

Support

If you contact us, we process your email address, message, and any diagnostics you choose to provide to answer the request and improve reliability. Please do not send credentials, pairing secrets, private keys, source code, or unredacted terminal output.

• Google Sheets: the private beta-list record described above.
• Cloudflare: website hosting, signaling, encrypted relay fallback, minimal routing state, and push delivery infrastructure.
• Apple: TestFlight/App Store distribution, APNs delivery, and in-app purchase.
• RevenueCat: subscription entitlement verification.
• Your paired endpoints: end-to-end encrypted Drover session content between iPhone and Drover Host.

We do not sell personal data and do not share it for cross-context behavioral advertising. Providers may process data in countries outside yours under their own infrastructure and applicable transfer safeguards.

Where laws such as the GDPR apply, we process beta-list data based on your consent, support and requested service data to perform a contract or take requested pre-contract steps, security and minimal operational metadata for our legitimate interests in delivering and protecting the service, and records when needed to meet legal obligations. You may withdraw beta-update consent at any time.

Beta-list records are kept until the beta communication purpose ends, you ask us to delete them, or they are removed during a retention review. We review inactive marketing records no later than 24 months after the last meaningful product update or interaction. Support messages are kept only as long as needed to resolve the issue and maintain reasonable business or legal records.

Operational routing and entitlement records are retained only for their service, security, billing, or legal purpose. Paired-device and local app/host data remains on your devices until you revoke, reset, uninstall, or remove it. Backup and provider deletion can take additional time.

You may ask to access, correct, export, restrict, object to, or delete personal data, and may withdraw consent where processing is based on consent. Email admin@newdrover.com. We may ask for reasonable verification before acting.

You may clear the website’s local storage through browser settings. App Store subscriptions are managed in your Apple account. Pairings can be revoked through Drover’s device controls when available; uninstalling removes app-local data subject to device backups.

If applicable, you may complain to your local data-protection authority. Mandatory rights in your jurisdiction remain unaffected.

newdrover.com currently installs no analytics, advertising pixels, or cross-site cookies. The beta form uses local storage only as described above. We do not use your data for solely automated decisions that produce legal or similarly significant effects. If analytics is introduced later, this policy and any required consent interface will be updated first.

Drover uses cryptographic pairing, authenticated end-to-end encryption, verified host identity, minimal push payloads, and fail-closed input behavior. No system is perfectly secure. Keep your phone and host updated, protect device access, revoke unfamiliar pairings, and report suspected issues through the security page.

Drover is a developer tool and is not directed to children under 16. Do not provide personal data if you are below the minimum age required to consent in your jurisdiction.

We may update this policy as the beta and service evolve. Material changes will be identified by a new effective date and, when appropriate, announced through the website, app, or beta updates.

Privacy questions and requests: admin@newdrover.com. Also see the terms of use.