Antlerstack Privacy Policy
Version: 1 Effective date: 7 November 2026
This policy explains what personal data Antlerstack collects, why, who we share it with, how long we keep it, and the rights you have. It applies to the Antlerstack mobile app, website and API (the "Service"). Words defined in our Terms of Service have the same meaning here.
The short version:
- We collect what you give us to run your account and your logs, including precise locations and photos, plus a small amount of technical data to keep the Service secure.
- You choose what is public. Private logs are visible only to you. Public logs, public spots and your profile are visible to other members.
- We have no advertising, no analytics trackers and no data brokers, and we do not sell or share your personal data for advertising.
- You can delete your account in the app at any time. Some public, community content stays after deletion, credited to no one. Section 8 explains exactly what and why.
1. Who we are
The controller of your personal data is Antlerstack, based in the United Kingdom ("we", "us").
Contact us about privacy at [email protected].
2. The data we collect
2.1 Data you give us
| Category | What it includes | Who can see it |
|---|---|---|
| Account details | First and last name, email address, username, password (stored only as a secure hash), country, time zone | Your username and country are public. Your name and email are private to you |
| Sign in with Apple / Google | A unique identifier from Apple or Google, and the email address and name they share with us. If you use Apple's "Hide My Email", we receive a relay address, not your real one. With Sign in with Apple we also keep a token Apple issues, stored encrypted, so that we can disconnect Antlerstack from your Apple ID when you delete your account | Private |
| Profile | Profile photo, tagline, website address, social media handles (Instagram, YouTube, TikTok, Facebook, X) | Public to other members |
| Preferences | Unit system (metric/imperial), log colour choices, notification settings | Private |
| Logs | Record type and details: for deer finds, species, find type, points, side, condition, weight and trophy score; for fishing catches, species, length, weight, method, water body and whether released; for camping stays, nights and method; for trail cameras, make, model, direction, battery and card state. Plus notes, date and time, and whether the log is public or private | As you choose (see section 3) |
| Locations | The precise GPS coordinates of a log or spot, the elevation, any what3words address you type in, and the spot a log is attached to | As you choose (see section 3) |
| Photos | Photos you attach to logs and spots, and your profile photo | See section 3.3 |
| Spots | Name, type, category, location, amenities, public/private setting, and photos of the place | Public spots are public; private spots are visible only to you |
| Community activity | Likes on logs, ratings of spots, amenity updates, badges earned, your trophy cabinet selection | Likes and your trophy cabinet are public: anyone who can see a log can see who liked it. Amenity updates are recorded against your account but not shown publicly |
| Reports and blocks | Reports you file (the reason and any description), and members you block | Private. The member you report or block is not told who you are |
| Moderation records | Decisions we make about your content or account (what was removed or restricted, the rule it broke, who decided and when), and a record of each email we sent you about a moderation decision or about the outcome of a report you filed | Private to you and our moderators |
| Acknowledgements | Which version of the Terms, this Privacy Policy and the Land Access & Outdoor Safety Notice you accepted, your confirmation that you meet the minimum age (not your date of birth, which we never ask for), when, and the app version | Private |
| Messages to us | Anything you send us by email, including support requests and complaints | Private |
2.2 Data we collect automatically
| Category | What it includes | Why |
|---|---|---|
| Device identifier | A random ID the app generates the first time it is needed and stores in your device's secure keychain, plus the platform (iOS or Android), and when each device first and last signed in to your account. On iOS this ID survives deleting and reinstalling the app. It is not an advertising identifier and is never used for tracking | Account security and abuse prevention (see section 4) |
| Push token | A token issued by Expo, Apple or Google that lets us send notifications to your device | To send the notifications you have enabled |
| Security and technical data | IP address, request times, app version, and error information in server logs; access tokens that keep you signed in | Security, rate limiting, preventing abuse and fixing faults |
| Crash and error reports | When the app crashes or our servers hit an error: the device model, operating system, app version, the part of the app or server that failed, and what led up to it. Reports are set up to leave out your account details, IP address, the content of your logs and your location | Finding and fixing faults |
| Elevation | If you save a location without an elevation, we look one up from its coordinates | To show elevation on your log or spot |
2.3 Data that stays on your device
The app keeps a copy of your own logs, spots and queued changes in a database on your phone so it works offline, along with downloaded offline maps and spot data, your settings, and which of our legal documents you have acknowledged, so that an acknowledgement you make without signal still counts and reaches us later. Your Insights (charts and patterns from your own logs) are calculated entirely on your device and are never sent to us. When you share a log as an image, the image is created on your device and handed to the app you choose; share images deliberately never include where the log was recorded.
2.4 Device permissions
The app asks for the following permissions, and only uses them for the stated purpose. You can withdraw any of them in your device settings; the related features will then stop working.
| Permission | Used for |
|---|---|
| Location (while using the app) | Pinning where you found or logged something, centring the map on you, and suggesting nearby spots. The app does not track your location in the background |
| Camera and photo library | Taking or choosing photos to attach to logs, spots and your profile. The app only accesses the photos you pick |
| Notifications | Telling you when you earn a badge or when someone likes your log |
Photo metadata: before a photo leaves your device, the app re-encodes it, which removes the embedded metadata (including camera details and any GPS location stored in the photo). The server re-encodes it again when it arrives.
2.5 What we do not collect
We do not use advertising identifiers (IDFA/AAID), advertising networks, third-party analytics, cross-app tracking, or data brokers. We do not collect health, biometric or payment data. We do not intentionally collect special category data; please do not include it in your logs, notes or photos.
3. Who can see what you post
3.1 Public and private
Each log is public or private, and, separately, its location is public or private. You choose both when you save a log and can change them later. Trail camera logs are always private.
- Private logs are visible only to you.
- Public logs can be seen by any signed-in member, including the species and details, notes, date, photos and your username. Their exact location is shown only if you make the location public.
- A log at a spot takes its location from that spot. If the spot is public, the log's location is shown with it.
3.2 Spots
Public spots (their name, exact location, category, amenities and photos) are visible to every member, appear on the community map, and are included in the offline spot data files that members download with offline maps. Making a spot public cannot be undone. Public spot data does not say who created the spot, but photos of a spot are credited to the member who took them.
3.3 Photos
Photos are stored with a cloud storage provider and delivered through a content delivery network. Every photo, including a photo on a private log, is stored at a web address that is long, random and practically impossible to guess, but is not password-protected. We only ever give a private photo's address to you. If you share that address yourself, anyone who has it can view the photo. Please keep this in mind when deciding what to photograph.
3.4 Your profile
Your public profile shows your username, tagline, profile photo, country, website, social media handles, when you joined, your public log statistics, your badges and your trophy cabinet. It is visible to signed-in members, except members you have blocked or who have blocked you.
3.5 Blocking
If you block someone, or someone blocks you, neither of you can see the other's logs, photos, profile, trophy cabinet or likes.
4. Why we use your data, and our legal basis
Under UK and EU data protection law we must have a legal basis for each use of your data.
| Purpose | Data used | Legal basis |
|---|---|---|
| Creating and running your account, signing you in, and providing every feature you use: storing and showing your logs, spots, photos, map, badges, profile, likes, trophy cabinet and preferences | Account, profile, logs, locations, photos, spots, community activity, push token | Contract: we need it to provide the Service you asked for |
| Showing your public content to other members, and including public spots in offline downloads | Public logs, public spots, profile | Contract |
| Looking up elevation for a location | Coordinates | Legitimate interests: providing useful information about your logs and spots |
| Sending notifications you have enabled | Push token, activity | Contract (you can turn each type off in Settings) |
| Sending security emails (password changed, new device signed in) and password reset codes | Email, device identifier | Legitimate interests: protecting your account. These cannot be switched off |
| Keeping the Service secure: rate limiting, detecting and preventing fraud, spam, abuse and ban evasion, and investigating misuse | Device identifier, IP address, technical data, account data | Legitimate interests: keeping the Service and its members safe |
| Finding and fixing crashes and errors | Crash and error reports | Legitimate interests: keeping the Service working |
| Checking text you submit against a prohibited-words list | The text submitted | Legitimate interests: keeping the Service free of objectionable content |
| Handling reports, moderating content, and enforcing our Terms (including banning accounts) | Reported content, reports, account and device data | Legitimate interests: keeping the Service safe; and legal obligation where the law requires us to act on illegal content |
| Emailing you when we remove your content or restrict your account (with our reasons and how to appeal), and telling you the outcome of reports you file | Email, moderation records, reports | Legal obligation where the law requires it, and otherwise legitimate interests: fair and transparent moderation. These cannot be switched off |
| Keeping a record of which version of our documents you accepted | Acknowledgements | Legitimate interests: being able to show what was agreed; and establishing and defending legal claims |
| Keeping backups | All data in our database and photo storage | Legitimate interests: being able to recover from failures and attacks |
| Responding to your messages and requests | Contact details and message content | Legitimate interests, or legal obligation for data protection requests |
| Complying with the law and responding to lawful requests from authorities | Any relevant data | Legal obligation, or legitimate interests in preventing harm |
| Establishing, exercising or defending legal claims | Any relevant data | Legitimate interests |
Where we rely on legitimate interests, we have weighed our interests against your rights and you have the right to object (section 9). We do not rely on consent as the legal basis for our core processing; the device permissions your phone asks for are operating-system controls, not consent under data protection law.
4.1 Automated decisions
Two automated checks can affect you:
- Prohibited-words filter. If text you submit contains a word on our list, the app will not accept it and will ask you to change it.
- Banned devices. If a device has previously been used by an account we banned, a new account cannot be registered from that device. This protects members from people returning after being banned. Because devices can be shared, this can occasionally affect someone who did nothing wrong. If you think it has affected you, contact [email protected] and a person will review it.
Neither check produces a decision about you beyond the Service. All report and ban decisions are made by a person.
5. Who we share your data with
We do not sell your personal data, and we do not share it for targeted advertising. We share it only as follows.
5.1 Other members
As described in section 3.
5.2 Service providers
These providers process data on our behalf, under contracts that require them to protect it and use it only on our instructions:
| Provider | What they do | Location |
|---|---|---|
| DigitalOcean, LLC | Hosts our servers and database | Canada (Toronto) |
| Cloudflare, Inc. | Stores photos, map files and backups; delivers content; protects against attacks; scans images for known child sexual abuse material; forwards emails you send to our addresses | Global network; USA |
| Resend (Plus Five Five, Inc.) | Sends account, security and moderation emails | USA |
| Expo (650 Industries, Inc.) | Routes push notifications to Apple and Google; delivers app updates (each check sends your IP address, device platform, app version and a random install identifier, never your account details) | USA |
| Apple Inc. and Google LLC | Deliver push notifications to your device (APNs and Firebase Cloud Messaging) | USA |
| Google LLC (Gmail) | Holds the emails you send to our addresses, and our replies | USA |
| Sentry (Functional Software, Inc.) | Receives crash and error reports from the app and our servers so we can fix them | European Union (Germany) |
5.3 Independent third parties
- Apple and Google sign-in. If you use Sign in with Apple or Google, they process your data under their own privacy policies. We receive only the identifier, email and name they share with us.
- Elevation lookup. To estimate elevation, we send the coordinates only (with no account information) to Open-Elevation (open-elevation.com), a free public elevation service.
- App stores. Apple and Google process data about your download and use of the app under their own policies.
- Apps you share to. When you share a log image, the app you choose receives it under its own policy.
5.4 Legal and safety reasons
We may disclose data to the police, courts, regulators or other authorities, or to others, where we believe in good faith that it is required by law or legal process, needed to protect anyone's safety or to prevent crime, fraud or abuse, or needed to establish, exercise or defend legal claims. We report child sexual abuse material to the relevant authorities.
5.5 Change of ownership
If Antlerstack is transferred to a company we set up to run it, or to another organisation, your data may be transferred with it. The new owner will be bound by this policy, and we will tell you before your data becomes subject to a different privacy policy.
6. International transfers
Some of our providers are located, or process data, outside the UK and the European Economic Area, mainly in the USA. Where that happens, we make sure your data is protected by an approved safeguard: an adequacy decision or the UK Extension to the EU–US Data Privacy Framework where the provider is certified, or the UK International Data Transfer Agreement / Addendum and the EU Standard Contractual Clauses. Contact us for more information.
7. How long we keep your data
| Data | How long |
|---|---|
| Account, profile, logs, spots, photos, preferences | While your account exists, until you delete them or your account |
| Access tokens (keeping you signed in) | Up to 180 days, or until you sign out, reset your password or delete your account |
| Password reset codes | 15 minutes |
| Photo uploads that were never attached to a log or spot | 24 hours |
| Push tokens | Until you sign out, turn off notifications at device level, or delete your account |
| Server logs | Kept in a fixed amount of space and overwritten automatically as newer entries arrive. They are also cleared each time we update our servers |
| Crash and error reports | 30 days |
| Database backups | 30 days, then automatically deleted |
| Reports you file, and moderation records | For as long as needed to keep the Service safe and handle any repeat problems |
| Device identifiers | See section 8 |
| Acknowledgement records | See section 8 |
| Content and data retained after account deletion | See section 8 |
8. Deleting your account
You can delete your account from Settings → Delete account in the app, or at https://antlerstack.com/delete-account/ if you no longer have the app. Deletion is immediate and permanent.
Deleted straight away: your name, email address, username (replaced with a placeholder), password, tagline, website and social handles, time zone, profile photo, badges, trophy cabinet, notification settings, push tokens, your links to Apple and Google sign-in, and every access token (signing you out everywhere). If you used Sign in with Apple, we also ask Apple to disconnect Antlerstack from your Apple ID. You will stop being shown as the author of anything.
Deleted shortly afterwards (usually within minutes): your private logs and their photos, private spots with no other logs attached, and their photos.
Kept, credited to no one:
- Your public logs and their photos, and photos you added to public spots, unless you tick the option to delete your public content too when you delete your account, in which case they are deleted as well.
- Public spots you created. A public spot is a real place that other members have logged at and rely on, so it stays, but it does not identify you.
- Likes and ratings you gave, because deleting them would change other members' scores.
- Reports you filed and moderation records.
- Your country, which on its own does not identify you.
Kept for security and legal reasons:
- Device identifiers linked to the deleted account are kept so that someone who was banned cannot return simply by deleting their account and making a new one. They are kept indefinitely and used for nothing else.
- Acknowledgement records (which versions of our Terms, this policy and the Land Access & Outdoor Safety Notice the account accepted, its confirmation of the minimum age, and when) are kept indefinitely against the anonymised account. They are evidence of the terms under which the public content that remains was published.
Backups: deleted data remains in encrypted database backups for up to 30 days. Backups are only used to restore the Service after a failure, and deleted data is not restored to the live Service except where a whole-system recovery makes that unavoidable, in which case we will delete it again.
If you want your public content erased but have already deleted your account without selecting that option, contact [email protected]. Because the account no longer identifies you, you will need to help us find the content (for example, by describing it and its location).
9. Your rights
Depending on where you live, you have some or all of these rights:
- Access: ask for a copy of your personal data.
- Rectification: ask us to correct inaccurate data. You can edit most of your data in the app. Your email address cannot currently be changed in the app; contact us to change it.
- Erasure: ask us to delete your data. You can do this yourself by deleting your account (section 8).
- Restriction: ask us to limit how we use your data.
- Portability: ask for the data you gave us in a machine-readable format.
- Objection: object to processing based on legitimate interests. We will stop unless we have compelling legitimate grounds, or need it for legal claims.
- Not to be subject to solely automated decisions with legal or similarly significant effects, and to ask for human review (see section 4.1).
To exercise a right, email [email protected]. We may need to confirm your identity first, usually by asking you to write from the email address on your account. We will respond within one month, which may be extended in some cases; we will tell you if so. We do not charge a fee unless a request is manifestly unfounded or excessive.
Complaints: if you are unhappy with how we handle your data, please contact us first. You also have the right to complain to the UK Information Commissioner's Office (ico.org.uk, 0303 123 1113) or, if you live in the EU/EEA, to your local data protection authority.
9.1 Additional information for US residents
Depending on your state (including California, Colorado, Connecticut, Virginia, Utah and others), you have the right to know what personal information we collect, use and disclose; to access, correct and delete it; to obtain a portable copy; and not to be discriminated against for exercising these rights.
- Categories we collect: identifiers (name, email, username, device ID, IP address); customer records; internet or other electronic network activity (security logs); precise geolocation; audio/visual information (photos); and inferences we do not make. We do not profile you.
- Sources: you, your device, and Apple or Google if you use their sign-in.
- Purposes and disclosures: as set out in sections 4 and 5.
- We do not sell personal information or share it for cross-context behavioural advertising, and have not done so in the past 12 months. We do not use or disclose sensitive personal information (including precise geolocation) for any purpose other than providing the Service you requested.
- You may use an authorised agent to make a request. We will verify the request as described above.
To exercise these rights, email [email protected].
9.2 Additional information for other regions
If you live in Canada, Brazil, Australia or another country with data protection law, you have the rights that law gives you, and can exercise them by emailing [email protected].
10. Security
We protect your data with measures including: encryption in transit (HTTPS) for all communication with the Service; passwords stored only as salted hashes; access tokens stored in your device's secure keychain; photos re-encoded to remove hidden data; encrypted backups held separately from our main systems with separate credentials; rate limiting and attack protection; and restricted, authenticated access to our administrative tools. We will notify you and the relevant regulator of a personal data breach where the law requires it.
No system is completely secure. Please use a strong, unique password and tell us straight away if you suspect your account has been compromised.
11. Children
The Service is not intended for anyone under 16, and we do not knowingly collect personal data from them. Everyone who signs up is asked to confirm that they are 16 or over. We do not ask for a date of birth or otherwise check ages.
If you are a parent or guardian and think your child under 16 has an account, contact [email protected]. We will look into it. Where we have good reason to believe an account belongs to someone under 16, we may ask the account holder to confirm their age, and may close the account.
12. Changes to this policy
We may update this policy from time to time. Each version has a version number. If we make a material change, we will tell you in the app before it takes effect, and ask you to acknowledge the new version. The version you acknowledged, and when, is recorded against your account.
13. Contact
Antlerstack Email: [email protected]