1. Overview
This policy describes how Stealth handles your information. It covers getstealth.net, email sign-in, licensed access, downloads, and the Windows and iPhone applications. Stealth is responsible for the personal information it handles as described in this policy. For privacy questions or requests, email support@getstealth.net.
We use information to sign you in, maintain account and license records, deliver software and requested emails, secure the Service, and answer support questions. The account backend does not request or store the coordinates you choose in the apps, your route history, your Apple ID password, or the contents of your phone. We do not sell personal information or use the account website for targeted advertising.
2. Information you provide
When you create or sign in to an account, we receive your email address and sign-in code request. When you accept the Terms and Privacy Policy, we record the policy version and time of acceptance. If a free access grant is assigned to your email, we record the grant duration, status, and issue time. We receive information you choose to include when contacting support, such as an order reference or description of a problem.
3. Account, authentication, and license records
Our Cloudflare D1 database stores an account identifier, email address, creation time, and policy consent. Sign-in challenges and access-verification values are protected in storage. A sign-in code expires after five minutes and is limited to a small number of attempts. After sign-in, the website sets the __Host-stealth cookie to keep your session for up to 30 days. It is Secure, HttpOnly, and SameSite=Lax. You can remove it by signing out; the backend stores only a digest of its token and removes expired sessions. The cookie is used for account sign-in and security, not advertising or cross-site tracking. Checkout uses an essential __Host-stealth-checkout cookie for up to one hour to return the purchasing browser to its account. After a completed checkout, a new account can be signed in automatically. Opening an existing account still requires its normal email verification. The website does not use advertising or session-replay cookies. If enabled at Cloudflare, privacy-focused Web Analytics collects aggregate page-view and performance information without advertising cookies; Cloudflare may process standard request metadata under its privacy notice.
For account access, the backend records the plan, whether access was purchased or granted, creation and expiration times, revocation status, and activated device platform. It stores an installation identifier and a protected device access token to enforce the stated Windows and iPhone device limits. Administrators can create or change a license only after server-side account authorization. License management actions are logged with administrator identity, action, time, and relevant expiration values. Account and license queries are restricted to the authenticated account; administrative operations require server-side authorization.
4. Location and application data
The account and licensing API does not ask for or store your selected coordinates, spoofing destinations, route paths, or location history. Recent searches and saved locations are stored locally on your computer or iPhone unless you choose to share them. Clear history in desktop Settings removes locally saved recent searches and location history.
The Windows dark map uses CARTO Dark Matter through a Stealth-hosted Cloudflare tile proxy. Cloudflare processes your connection metadata and the requested tile coordinates, which identify the map area and zoom level being viewed. The proxy sends tile coordinates and our server-held API key to CARTO; it does not forward your account token, email, or search text. CARTO receives the proxy connection and service request metadata. Tile requests are not written to our account database. Local developer overrides may request CARTO tiles directly.
Other desktop map styles and fallback tiles use OpenFreeMap, OpenStreetMap, or Esri ArcGIS Online. Desktop fallback place searches use the public Photon service at photon.komoot.io through the local app or directly from the browser; reverse place-name lookup may use OpenStreetMap Nominatim. Road routes use the FOSSGIS-operated routing.openstreetmap.de service. When Apple MapKit JS is configured, Apple handles map display, search, and related map features. The iPhone app uses Apple MapKit for map display, place search, and directions; route-speed-limit lookups may send route areas to overpass-api.de.
Map, search, and routing providers receive the search text, coordinates, route points, or map area needed for the requested feature and normal request metadata, such as the connecting IP address and app information. Their own terms and privacy policies govern that processing. FOSSGIS states that route requests are saved in its server log. The desktop app also downloads developer-support files from GitHub. Apple credentials, pairing files, and signing material are not sent to our account API; do not include them in support messages.
5. Permissions, technical and security information
Local Network permission supports communication with the local developer connection. Map location permission lets the app display or return to your real location; it is separate from the location you select for simulation. Optional background location access supports enabled background features, and optional notifications support renewal reminders. The welcome and setup guides offer the same permission requests as App permissions. iOS controls the actual permission dialogs, and you can change permissions in iPhone Settings. Declining a permission can limit its related feature. Permissions alone do not guarantee background execution.
When a browser or app connects to our website, Cloudflare may process an IP address, request time, user-agent information, URL, and security telemetry to route requests, resist abuse, and maintain availability. The Worker derives short-lived identifiers from IP addresses and email addresses for rate limiting; it does not keep a plain IP-address history in the account tables. Cloudflare may maintain operational logs under its own service practices. The Windows app writes local diagnostic output to log.txt. The iPhone app keeps a limited in-memory app log and can save device diagnostic logs to idevice_log.txt. These files stay on your device unless you choose to share or send them; they may include device or app names, process names, error details, and other information present in system logs. Review and redact logs before sharing them. We do not run advertising or session-replay tools. If Cloudflare Web Analytics is enabled, it measures aggregate page views and performance without tracking people across sites.
6. Email
Brevo processes your email address and message content to deliver the one-time sign-in code and access-grant notices you request. Treat sign-in codes and account links as private. The sender used for transactional messages is access@getstealth.net. We send account and service messages, not unrelated marketing through the login-code flow. Brevo records delivery, bounce, and abuse-prevention metadata. Its transactional open and click tracking is configured to anonymize recipient-linked events. Transactional previews are not stored and logs are retained for one month under the current Brevo account settings.
When you email support@getstealth.net, Cloudflare Email Routing forwards the message to our support Gmail inbox. Google processes the message, sender details, attachments, and conversation history so we can read and respond. Replies sent through Brevo also pass through its email infrastructure. Their privacy notices apply to their processing: Cloudflare and Google. We use support correspondence to handle your request and keep relevant records for follow-up, security, and disputes.
7. Hosting and service providers
Cloudflare hosts the website assets, Worker application, D1 account database, and R2 software downloads. Brevo delivers transactional email. Their privacy information is available in Cloudflare’s Privacy Policy and Brevo’s Privacy Policy. CARTO, Photon (Komoot), Apple, OpenFreeMap, OpenStreetMap Foundation services (including Nominatim and its public tile service), FOSSGIS (routing.openstreetmap.de), the public Overpass API instance, Esri ArcGIS Online, and GitHub provide map, search, routing, imagery, or app-support features as described above. These providers process information as needed for the features you request, may process it in regions outside your country, and operate under their own terms and privacy notices. See CARTO privacy, Komoot privacy, Apple Maps privacy, OpenFreeMap privacy, Nominatim usage policy, OpenStreetMap tile usage policy, OpenStreetMap Foundation privacy policy, FOSSGIS routing service and policy, FOSSGIS privacy notice, Overpass public instance usage information, OpenStreetMap attribution and data license, and Esri privacy statement. Service API secrets and database bindings are held in server-side configuration. Session and device credentials are used by the browser or app to authenticate its own requests; they must not be shared.
8. Stripe payments, subscriptions, and trials
Stripe processes payments through Stripe Checkout, including payment fields embedded in our website, and its billing portal. For a signed-in purchase, we send Stripe your account email, an internal account reference, selected plan, and purchase reference. For a purchase without signing in, Stripe collects the checkout email and provides it to us to create or link your account and deliver access. Stripe collects the payment and billing details you enter and processes payment security and fraud-prevention information under its Privacy Policy. Stealth does not receive or store your full card number or card security code.
We store Stripe customer, checkout, subscription, invoice, and payment references, plan and amount, subscription and payment status, trial and paid-access end times, cancellation status, and refund or dispute events. Verified Stripe notifications update access records. These records let us deliver access, show billing status, prevent duplicate purchases, and resolve payment problems.
The three-day trial requires a payment card and is available on eligible recurring plans, not Lifetime. We record trial eligibility and redemption against your account and a digest of your normalized email. This digest and associated billing records may remain after account deletion to prevent repeated trial claims and meet recordkeeping obligations; a digest is pseudonymous data, not a promise of anonymity. Checkout displays the charge, billing interval, and trial end before you confirm. A purchase is linked to the account associated with the checkout email. If no account exists, we create one automatically. Access to an existing account still requires its normal email verification. Payment details are entered in Stripe-controlled fields or pages, including when those fields appear inside our website.
9. Downloads and file delivery
The Windows setup file, Windows updates, and iPhone installation packages are delivered from Stealth-managed Cloudflare R2 storage through our download routes. Windows checks release metadata and downloads an update when you choose it. These requests expose the requesting IP address and normal connection metadata to Cloudflare. Release checks do not include your selected map locations or Apple password. Download access is not itself recorded as a successful use of licensed location features. Keep your installer from the official domain and do not share private account information with other people.
10. Apple sign-in, app signing, and local connection
Your Apple account for installing or refreshing the iPhone app is separate from your Stealth email account. The installation and refresh tools communicate with Apple for authentication, developer certificates, and provisioning. Apple credentials and signing material are not submitted to the Stealth account API. On iPhone, the password is used for sign-in and is not saved by Stealth; authentication sessions, signing material, and authentication-helper state are stored in the iPhone Keychain for subsequent refreshes. On Windows, the signing helper can retain an Apple session when you choose to save your Apple ID; temporary sessions are cleared by the app on normal exit when that option is off.
The iPhone refresh flow uses SideStore’s authentication helper at ani.sidestore.io to obtain authentication-support data. That service receives connection metadata and authentication-helper requests; it is distinct from the Stealth account backend. Apple authentication and developer services are governed by Apple’s privacy information. Your device pairing file and provisioning data are sensitive local credentials. Do not upload them to support or Discord.
LocalDevVPN is a separate app used to establish the on-device developer connection. Stealth does not operate it as a general internet VPN or promise that it hides your IP address or anonymizes internet traffic. Its connection configuration and Apple developer-device tools are needed for supported mobile features. Profile refresh renews the existing installation; it does not download and install a newer Stealth app version. App updates are installed through Windows.
11. Purposes and legal grounds
Depending on the law where you live, we process information to perform the account or license service you request; to comply with legal obligations; and for legitimate interests such as protecting accounts, preventing credential abuse, maintaining reliable downloads, and responding to support. Where required, we ask for consent. You may withdraw consent where consent is the legal basis, although doing so may prevent the related feature from operating. Local privacy law may provide additional rights or require more specific disclosures.
12. Retention
Updated Stealth apps report the number of spoofing sessions on each platform and elapsed spoofing seconds to display your account usage. Reports contain a random session identifier, platform, installation identifier, and elapsed seconds, linked to your account through your device credentials. They do not contain locations, searches, or routes. These usage records are kept while your account exists and are deleted when you delete your account. Usage from older apps is not available.
Unredeemed sign-in challenges are removed after expiration and scheduled cleanup. Expired sessions and temporary rate-limit counters are routinely deleted. Account, license, device, consent, administrator audit, and any transaction records are kept while reasonably needed to provide the Service, support a license, prevent fraud, resolve disputes, or meet legal obligations. When data is no longer needed, it is deleted or de-identified where practical. Provider logs and backups may persist for the provider's normal retention period.
13. Your choices and rights
You can sign out in the Windows or iPhone app. Contact support@getstealth.net to request device removal or account deletion; available account controls may also provide these actions. Account deletion revokes active access, removes registered device records, invalidates Stealth sessions, deletes account usage records, and replaces the account email with a non-deliverable identifier. It does not remotely erase files from your devices or guarantee immediate contact with an offline app. An ongoing subscription must be canceled and reach its end before self-service account deletion is allowed. That self-service restriction does not remove a statutory right to request deletion; contact email support for a request that the account controls cannot complete. Use Manage billing first; contact email support if you cannot access it. We retain license and audit records only as needed for security, service administration, dispute resolution, or legal obligations. Depending on your location, you may have rights to request access to, correction of, deletion of, or a copy of personal information; object to or restrict some processing; withdraw consent; or complain to a data-protection authority. Contact support@getstealth.net to make a request. We may ask for information needed to verify your identity and protect another person’s account. We will respond within the period required by applicable law. Some records may be retained where a legal exception or valid obligation applies. If we cannot grant a request, we will explain the reason and any available appeal. To ask us to review a privacy decision, reply to that response or email support@getstealth.net with “Privacy appeal” and the original request reference. You may also complain to the privacy authority for your location. In the UK, you can contact the Information Commissioner’s Office; in the EEA, contact your national data-protection authority. We do not deny service or charge a penalty solely because you exercise an applicable privacy right.
14. Age requirement
Stealth is intended for adults aged 18 or older, as stated in our Terms. We do not knowingly offer accounts or collect personal information from people under 18. If you believe a minor has provided information, contact us so we can review and take appropriate steps to remove it, subject to legal retention requirements.
15. International processing
Our infrastructure providers may process data in countries other than the one where you live. Where a transfer safeguard is required by law, we or the relevant service provider will use an available lawful mechanism. Contact support if you need information about the safeguards applicable to your request.
16. Security
We use transport encryption, protected server-side secrets, hashed authentication and license credentials, rate limits, and access controls appropriate to the information handled by the Service. No network service or storage method can be guaranteed perfectly secure. If a security incident affects your information, we will assess it, take appropriate steps to contain it, and notify affected people and authorities where the law requires. Using infrastructure or payment providers does not remove Stealth’s responsibilities for the information it handles. You also help protect your account by controlling your email inbox, not sharing sign-in codes, keeping devices updated, and reporting suspected compromise promptly.
17. Third-party websites, Discord, and support
You can contact email support or choose Discord. Discord processes your community account, messages, attachments, and connection information under its Privacy Policy. Public channels can be read by other members. Use email for private account, billing, or privacy requests, and share only the information needed to resolve the problem. Joining Discord is optional.
The website and apps may link to community, map, platform, download, or support services not operated by Stealth. A link does not make their privacy practices ours. Information you submit directly to another service is controlled by that provider. Avoid putting sign-in codes, precise home addresses, or device pairing details in public community posts.
18. Changes to this policy
We will update the effective date and version when this policy changes. If a new feature materially changes the information collected or how it is used, we will update this notice before enabling that collection and request consent where required. We will notify account holders or request renewed agreement where applicable law requires it. The prior version may be retained for compliance and audit.
19. Contact
Send privacy, account, or support requests to support@getstealth.net. Please include the account email and describe the request, but do not include your password, sign-in code, or Apple credentials. We will use the details you provide to verify and respond to the request.
Free-trial abuse prevention
To limit free trials across different email accounts, we retain a hashed identifier derived from Stripe’s card fingerprint and the trial purchase reference. We do not receive or store your full card number or security code. This identifier is used only for trial eligibility and related abuse prevention, and may remain after account deletion so creating another account does not reset the trial limit.
Numbered U.S. address searches
When you select a numbered-address lookup in the Windows app, the street address, city and state are sent to the U.S. Census Bureau geocoder to estimate its map position from address ranges. This lookup does not establish that a building exists or identify its entrance. It is separate from the existing map and autocomplete providers. Avoid submitting an address you do not want the provider to receive. The app temporarily caches lookup results to avoid repeating requests.