Privacy Policy
Last updated: October 29, 2026
This Privacy Policy explains how 10Point ("10Point," "we," "us," or "our") collects, uses, and shares information when you use our app and services on iOS, Android, and the web (PWA at 10point.app) (collectively, the "Service").
Website: 10point.app Contact: info@lunos.dev
1. Who This Policy Applies To
This Policy applies to anyone who uses the Service. You must be at least 13 years old to use the Service. The Service is not intended for children under 13 and is intended for users located in the United States. See Section 11 ("Children's Privacy").
2. Summary of What We Do (and Don't Do)
2.1 What the Service Does
10Point is a wildlife habitat mapping tool. It provides interactive maps with habitat density overlays, wind condition data and forecasts, public land access boundaries, location search, AI-written Hunt Brief reports for an area you choose, and user waypoints (pins), folders, colors, and preferences.
2.2 What We Do Not Do
• No advertising and no ad networks
• No selling of personal data
• No sharing of personal data with third parties for their marketing
• No tracking of your device location history or movement patterns
• No storage or transmission of your device location between sessions
2.3 Device Location Permission
10Point requests foreground location permission ("while using the app") to center the map on your current position and to surface nearby features. Your device location is used in-session only — we do not log, store, or transmit location history. Waypoints you place are GPS coordinates you choose manually, not automatic captures of where you have been. If you use place search, your device position may be sent with the search text as a location hint (see Section 3.7).
2.4 Product Analytics
We use PostHog, a product analytics service, to understand how the Service is used — for example, which features are popular and where users encounter problems. When you are signed out, PostHog uses an app-generated identifier. When you sign in, we associate analytics events with your app account ID so we can understand usage across authenticated sessions. Events may include feature interactions, page views, subscription tier, platform, and app version. We do not intentionally send your email address, precise device location, waypoint coordinates or names, or location-search text to PostHog. We do not use PostHog for advertising, cross-app tracking, or cross-site behavioral advertising. You can learn more about PostHog's privacy practices at posthog.com/privacy.
On a successful account deletion, we delete the PostHog person profile linked to your account ID and queue its historical events and any recordings for deletion. PostHog processes the queued historical-data deletion asynchronously, so those records may remain for a limited time after your account deletion succeeds.
3. Information We Collect
We collect information in three main ways: (1) information you provide, (2) information generated by your use of the Service, and (3) information from third parties you choose to use (like Google or Apple sign-in).
3.1 Account Information (Optional)
Accounts are optional for basic use. If you create an account, we collect your email address and authentication credentials (email/password, Google OAuth, or Sign in with Apple). Passwords are managed by Supabase Auth and stored as a hash — we do not store plaintext passwords.
If you sign in with Google or Apple, we receive the provider-specific account identifier and email address the provider makes available. Apple may provide a private relay email address instead of your personal address. We do not collect phone numbers, physical addresses, or social profile data.
When Apple supplies a revocable refresh credential after a successful Sign in with Apple callback, our authenticated gateway validates it and stores a server-side encrypted copy only so we can revoke the Apple authorization when you delete your account. After that transfer succeeds, the app removes provider credentials from its persisted authentication session. We do not use the refresh credential for another purpose.
3.2 User-Generated Content
When you are signed in, we sync the following to our database (via Supabase): waypoints (GPS coordinates you choose, label, notes, color, folder assignment), folders (name, color, visibility toggle), Hunt Lineups (nickname and the waypoints in the lineup), Hunt Brief library entries (the title and the area you framed; the generated report itself is a file kept in our file storage on Cloudflare, see Section 3.8), and preferences (selected state, selected species, layer and display settings, and, on the web, your last map position: the map's center, zoom, bearing and tilt). A waypoint whose sync is pending or has failed may remain stored locally on your device until it syncs successfully, you discard it, or you delete your account. Deleting your account clears that local copy on the device you delete it from; on your other devices it stays until it syncs, you discard it, or you clear the app's data.
Waypoint labels and notes, folder names, Hunt Lineup nicknames, and Hunt Brief titles are text you type. They are stored with your account, and our database access rules limit reading them to your account. The Service has no feature that shares them with other users. In the iOS and Android apps you can export waypoints to a GPX or KML file, which includes their labels, notes and folder names; the app hands that file to your device's share sheet, and where it goes from there is your choice.
On the web, your owner-scoped last map view may also retain waypoint coordinates locally for navigation continuity after server sync. This local map state is removed on the device you delete your account from, or when you clear the site's data.
When you are not signed in, waypoints and folders you create are kept only for your current session. They are not saved and are cleared when you close or reload the app, and they are never sent to our servers. Sign in to save them.
App preferences (such as your selected state, species, layer settings, and — on the web — your last map view) are stored locally on your device for convenience and are not sent to our servers when you are not signed in.
3.3 Subscription and Purchase Information
If you subscribe to 10Point Pro (a monthly or annual plan at the price shown before purchase), purchases are handled by the Apple App Store (iOS), Google Play (Android), or Stripe (web) managed through RevenueCat. We do not store your credit card number or full payment details. We may receive or access limited subscription-related information such as subscription status, product identifiers, transaction timestamps, and an app-specific RevenueCat user ID. For signed-in users, that identifier is linked to the user's 10Point account so subscription access can follow the account across devices.
Founding Member Pricing
These terms apply only to members who joined during the Founding Member offer.
• Your founding subscription renews at $19.99 per year under the terms of this offer.
• Anon Hedonic LLC, which operates 10Point, may change these terms, including the renewal price, at its discretion. A price change applies only at a renewal after we notify you, and you can cancel before it takes effect.
• If your subscription ends, the founding price is not guaranteed on a later subscription.
• Restoration or resubscription is subject to your billing provider’s rules and the price shown when you resume or subscribe.
• The founding price is tied to your account and is not transferable.
3.4 Standard Technical Data
Even without analytics SDKs, some technical data is processed when you access the Service, including through our hosting and security providers (e.g., Cloudflare). This may include IP address, user-agent and device/browser type, request timestamps, and basic diagnostic/security logs. We use this information primarily for security, reliability, and abuse prevention — not for advertising.
3.5 Cookies and Similar Technologies
We use only essential cookies or local storage needed to maintain sessions (e.g., Supabase auth tokens) and keep you signed in. We do not use third-party tracking cookies for advertising.
3.6 Connectivity Status
Our native apps may detect whether you are online or offline to show user-facing status messages. We do not transmit data while offline and we do not track offline behavior.
3.7 Location Search
When you search for a place, the search text you type is sent through our gateway to Mapbox, along with a coordinate that Mapbox uses to rank nearby results. Depending on the situation, that coordinate is the center of the map you are viewing, a point you have selected, your device's current position (if you have allowed location access), or the center of the state you are viewing. If none of these is available, the request asks Mapbox to use its IP-based default instead. The request also carries a random search-session identifier. We do not send your account ID or email address to Mapbox.
3.8 Hunt Brief (AI-Written Reports)
When you ask for a Hunt Brief, the app sends the area you framed on the map (a bounding rectangle), the state, and the hunt date and time-of-day window to our servers, together with your account ID so the request is tied to your account. Our servers compute habitat, terrain, and weather evidence for that area on a compute service hosted by Amazon Web Services (AWS).
The written report is then generated by Anthropic (Claude). What we send Anthropic is a summary computed from that evidence for the area you drew: coarse map cells, each about 150 meters across, inside that area, area sizes, scores, reason and risk codes, the state, the dates, and climate or weather summaries. We never send Anthropic your device's location, your name, your email address or your account ID, and the Hunt Brief request takes no text that you write, so no free text goes to Anthropic. Anthropic handles data under its own terms and privacy policy, which we do not control. Reports are labeled as written by AI.
A Hunt Brief is sent to Anthropic only when you choose to run one. If you don't use Hunt Brief, nothing is sent to Anthropic.
Before your first Hunt Brief, the app asks whether you allow us to send Anthropic the summary described above. Nothing is sent until you choose Allow; if you choose Not now, nothing is sent and you are asked again next time. When you choose Allow, your choice is saved to your account with the time you made it, so you are not asked again on your other devices. You can turn it off at any time in Account, under Hunt Brief, Anthropic processing; that is saved to your account with its time too, and after that the app asks again before your next brief. The app also keeps the time of each choice on the device where you make it. If we change the AI provider, the app asks again before your next brief.
Your Hunt Brief library keeps each report, its title, and the area you framed until you delete the brief (see Section 7).
3.9 Install Identifiers
Some of our providers use a random identifier for each app install. PostHog uses an app-generated identifier while you are signed out (see Section 2.4). Before you sign in, RevenueCat uses an anonymous app user ID in the iOS and Android apps. Expo's update service receives a random install identifier (the EAS Client ID) whenever the app checks for updates. These are random values generated for the install, not advertising IDs. When you sign in, we link your account ID to the PostHog and RevenueCat identifiers. We do not send your account ID to Expo.
3.10 App Diagnostics
The app sends a small number of performance and reliability events to PostHog: frame timing during wind playback, graphics quality tier changes, slow purchases, and map data or satellite imagery that failed to load. These events describe the app's behavior (timings, counts, tiers, platform, and which data source failed); the satellite-imagery event also includes a coarse region label for the map view (for example, "conus").
4. How We Use Information
We use collected information to:
• Provide and operate the Service (maps, overlays, location search, waypoint sync, preferences)
• Generate and store the Hunt Brief reports you request
• Create and manage accounts and authenticate users
• Process subscriptions and maintain access to Pro features
• Store and sync user content (for logged-in users)
• Understand product usage and improve the Service (via PostHog analytics), including app performance and load-failure diagnostics
• Deliver app updates (via Expo's update service)
• Maintain security, prevent abuse, and protect the Service
• Provide support and respond to inquiries
• Comply with law and enforce our terms
We do not use your information for targeted advertising.
5. How We Share Information
We share information only as needed to run the Service, comply with law, or protect rights.
5.1 Service Providers
Supabase — Authentication, database, user data storage. Data shared: email, password hash (Supabase-managed), waypoints (including labels and notes), folders, Hunt Lineups, Hunt Brief titles and framed areas, preferences.
RevenueCat — Subscription management. Data shared: app-specific user ID (an anonymous ID before you sign in on iOS and Android, linked to the 10Point account once signed in), subscription status, transaction metadata.
Stripe (via RevenueCat) — Web payment processing. Payment info is processed by Stripe, not stored by us.
Apple App Store / Google Play — App distribution and in-app purchases. Standard platform data per their policies.
Google OAuth — Optional sign-in. Data shared: Google account ID, email.
Sign in with Apple — Optional sign-in. Data received: Apple account identifier, email address when Apple makes one available, and a revocable refresh credential when Apple provides one. After validation, the refresh credential is stored encrypted solely for authorization revocation when the account is deleted.
Mapbox — Location search (geocoding). Data shared: the search query text, a random search-session identifier, and a coordinate used as a location hint (the map center, a selected point, your device's position, or the center of the state you are viewing; see Section 3.7). Requests go through our gateway; we do not send your account ID or email address.
Cloudflare — Edge hosting, CDN, Workers. Our gateway runs on Cloudflare Workers and relays search and Hunt Brief requests; generated Hunt Brief reports are kept in Cloudflare storage. Data shared: standard request metadata (IP, user-agent, logs for performance/security) and the Hunt Brief data described in Section 3.8.
Anthropic (Claude) — Writes Hunt Brief reports. Data shared: a summary computed from habitat, terrain, and weather evidence for the area you drew (coarse map cells about 150 meters across inside it, area sizes, scores, reason and risk codes, state, and dates). Not shared: your device's location, your name, email address, account ID, or any text you write. Nothing is sent to Anthropic unless you run a Hunt Brief. See Section 3.8.
Amazon Web Services (AWS) — Hosts the compute service that builds the Hunt Brief evidence. Data shared: the area you framed (bounding rectangle), state, hunt date and time-of-day window, and your account ID.
Expo (EAS Update) — Delivers app updates. Data shared: a random install identifier (EAS Client ID), platform, app runtime version, and the identifier of the update the app is running. If the app's previous launch ended in a fatal error, the update request may also include a short error message (capped at 1,024 characters). We do not send your account ID.
PostHog — Product analytics. Data shared: app-generated identifier when signed out; 10Point account ID when signed in; feature interactions, page views, subscription tier, platform/device type, and app version. We do not intentionally send email addresses, precise device location, waypoint coordinates or names, or location-search text to PostHog. PostHog data is used solely to understand and improve the Service, not for advertising or cross-app tracking. Successful account deletion removes the linked PostHog person profile and queues its historical events and any recordings for asynchronous deletion.
Protomaps — Basemap tiles. Data shared: tile requests (generally no user account data).
5.2 Legal and Safety Reasons
We may share information if we believe it is reasonably necessary to comply with law, regulation, legal process, or government request; enforce our Terms of Service; detect, prevent, or address fraud, security, or technical issues; or protect the rights, property, or safety of users, the public, or 10Point.
5.3 Business Transfers
If we are involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to standard confidentiality protections.
6. Where Information Is Processed
We operate in the United States (Michigan-based). Our vendors (e.g., Supabase, Cloudflare, RevenueCat, Stripe, Mapbox, Anthropic, AWS, Expo) may process data in the U.S. and potentially other locations where they operate.
7. Data Retention
Logged-in users: We retain your account data and synced content (waypoints, folders, preferences) as long as your account is active or as needed to provide the Service. On the web, an owner-scoped local map-state cache may also retain waypoint coordinates for navigation continuity until you delete your account from that browser or clear its site data.
Hunt Briefs: Deleting a brief in the app removes it from your library, and we then delete its stored report file. If that file deletion fails, the file can remain in storage; contact us and we'll delete it. A record of the request, including its title and framed area, is kept so that usage limits stay accurate, and is removed when your account is deleted. Deleting your account also deletes every remaining report file.
Non-logged-in users: Waypoints and folders are kept only for your current session and are cleared when you close or reload the app. Preferences may remain on your device until you clear the app or site data.
Deleting content: You can delete individual waypoints and folders in-app. Deleted items are removed from your account data in Supabase (subject to typical technical delays for backups).
Account deletion: You can delete your account (a) in-app under Account → Delete Account, (b) on the web at 10point.app/delete-account, or (c) by contacting info@lunos.dev. The deletion service first deletes the PostHog person profile linked to your account ID and queues its historical events and any recordings for deletion. It then removes your linked RevenueCat customer profile, active Supabase account, server-synced waypoints, folders and Hunt Lineups, and synced preferences. Deleting your account deletes your account record and your Hunt Brief request records. Deleting your account also deletes the report files for all your Hunt Briefs. If those files cannot be deleted, the app shows an error instead of confirming the deletion, and you can try again. Unless that error says the app couldn't confirm whether account deletion finished, your account was not deleted. If it does say that, tap Delete Account again to check and finish the deletion, or contact us. A report that finishes while your account is being deleted is normally deleted automatically shortly afterward; if you think one remains, contact us and we'll delete it. PostHog processes historical event and recording deletion asynchronously. Limited records may remain temporarily in backups or be retained when required for security, legal compliance, accounting, fraud prevention, chargebacks, or dispute resolution.
Subscriptions: Deleting the RevenueCat customer profile cancels a subscription purchased through RevenueCat Web Billing on 10point.app. It does not cancel an App Store or Google Play subscription; cancel those separately to prevent future charges.
Sign in with Apple: When an encrypted revocable refresh credential is available, we automatically use it to revoke the Apple authorization during account deletion. If no revocable credential is stored, account deletion still completes and the confirmation directs you to remove 10Point under Sign in with Apple in Apple Settings.
Analytics: Account deletion resets the PostHog identity on that device, deletes the linked PostHog person profile, and queues historical events and any recordings tied to the former account ID for deletion. The queued historical-data deletion may complete asynchronously.
Payment records: Payment platforms may retain transaction records as required for tax, accounting, fraud prevention, chargeback handling, dispute resolution, and legal compliance under their own policies.
8. Your Choices and Controls
• Use the Service without an account (limited to local-only data storage)
• Access and update account info through the app or by contacting us
• Delete your content (waypoints/folders) in-app
• Request account deletion (see Section 7)
9. U.S. State Privacy Rights
Some U.S. state laws provide additional rights (e.g., California, Virginia, Colorado). Depending on your state of residence, you may have rights to request access to personal information we hold about you, request deletion, request correction, and opt out of certain types of processing.
We do not sell personal information and we do not share it for cross-context behavioral advertising. To make a request, contact info@lunos.dev. We may need to verify your request (for example, by confirming access to the email address on the account).
10. Security
We use reasonable administrative, technical, and organizational safeguards designed to protect information. However, no method of transmission or storage is 100% secure. You are responsible for keeping your login credentials confidential.
11. Children's Privacy (COPPA)
10Point is not intended for children under 13 and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us personal information, contact info@lunos.dev and we will take steps to delete it.
12. Changes to This Privacy Policy
We may update this Policy from time to time. If we make material changes, we will update the "Last Updated" date and may provide additional notice in the app or on 10point.app.
13. Contact Us
If you have questions or requests related to privacy, contact: Email: info@lunos.dev Website: 10point.app
© 2026 10Point. All rights reserved.