Legal
Privacy Policy
Effective date: 3 November 2026
Last updated: 3 November 2026
Agama is a field companion for reptiles and amphibians: browse species, log what you find, plan trips, and keep a life list. This policy explains what we collect, what we deliberately refuse to collect, who can see what, and what you can do about it. It covers the Agama app and the agamaapp.com website. It describes version 1.0.3 of the app; §13 lists how older versions differ.
Agama is operated by Ramon Duran Romaña, Groot Begijnhof 40, 3000 Leuven, Belgium ("we", "us"). For anything in this policy, write to support@agamaapp.com.
1. The short version
- We never store the exact location of a wild animal. A record keeps a country, the name of a broad area and at most one point rounded to a grid of roughly 2 km.
- Photo location metadata is removed on your phone, before anything is uploaded.
- Your photos are kept in private storage. In the app they are shown through links that stop working after an hour. By default your followers can see them, and you can turn that off.
- You can export your observations as a spreadsheet, and you can delete your account and its contents from inside the app.
2. What we collect
Information you give us
| What | Why | Notes |
|---|---|---|
| Email address | Sign-in, password reset, essential service messages | Handled by our authentication provider |
| Sign in with Apple or Google | Signing in without a password | We receive your email, your account ID at that provider and the name it gives us: Apple only if you choose to share it, Google every time, with the address of your Google profile picture. That name fills in your first and last name, which you can change before you finish signing up and at any time in Settings |
| Password | Sign-in | Stored only as a salted hash; we never see it |
| First name, last name, @handle | How you appear to others and how people find you | Visible to anyone signed in, and shown with any reference image of yours we accept. If you own a trip, also shown to anyone who opens an invite link to it, whoever on the trip shared it |
| Profile photo | Optional profile detail | Visible to anyone signed in |
| Observations | The core of the app | Species (and subspecies), date or approximate date, time, country, broad area name, a point rounded to roughly 2 km, counts, life stage, how it was found, notes and whether they are private, the trip, and the people you tag |
| Trips | Planning and logging trips together | Title, dates, countries, notes, members, day journals, planned stops (rounded the same way, with their names and notes), target species and a cover photo |
| Photos you upload | Attaching your own images to species and observations | See §3 and §5 |
| Follows | Following people and being followed | Who you follow, who follows you, and follow requests |
| Great finds and suggested IDs | Taking part in other people's records | Each one is shown to the observer with your name, and people who can see the observation can see who called it a great find |
| Checklists | Your own target lists, and lists you take | Title, description and species. A checklist you publish can be seen by anyone signed in. When you take someone else's checklist, its owner can see that you took it |
| Feedback | Answering you and fixing problems | Your message, up to three screenshots, your app version and phone system, and any replies |
| Reports and blocks | Keeping Agama safe | What you reported, your reason and note, and who you blocked |
| Supporter status | Lifting the free limits | Plan, start and end dates, and why you cancelled if you choose to tell us |
| Terms acceptance | Recording what you agreed to | The date and the version you accepted |
| Preferences | Making the app behave the way you want | Naming, units, taxa filter, species-name language, photo licence, notification switches, privacy switches, and whether you share usage statistics. Your theme and interface language stay on your phone |
Information collected automatically
- Approximate location, only if you allow it. While you use the app, Agama takes one rough reading of your position at a time: when you open Explore, start a new observation, open the species list, or tap a button that asks for your location. It uses it to fill in the country and suggest a broad area for an observation, and to show what has been recorded near you. It never reads your location in the background. See §3 for what is kept and §6 for who receives it.
- Usage events. When you use a feature, the app records a short event against your account: what it was (for example "observation logged" or "Explore opened") and a broad detail such as how you found the animal. Never a place or a note. We use these to see which parts of Agama people use. You can turn this off in Settings → Profile & privacy → Share usage statistics.
- Your app install. A random ID the app creates on first launch and keeps on your phone, your platform, system version, app version and update, and when the install was first and last seen. We use it to see who still runs an old version and to tell them an update is out.
- Push token. If you allow notifications, the token your phone gives us so they can reach it.
- Crash reports. See Sentry in §6.
- Server logs. Our providers log the IP address and time of each request, to keep the service running and secure.
We do not use advertising identifiers, and Agama contains no advertising SDKs. The only third-party code that reports on how the app runs is Sentry, for crashes and performance (§6).
3. What we deliberately do not collect
This is the part that matters most for wildlife, so we are specific about it.
- No exact wildlife coordinates, ever. An observation is stored with a country and a broad area (a national park, a mountain range, an island, an administrative region), and at most one point rounded to a grid of 0.02 degrees: about 2.2 km north to south, and narrower east to west away from the equator (about 1.4 km in Belgium). That point is the centre of the area you named; if you used your location or picked a spot on the map, the grid cell you were in, even when the name you choose is a whole region; for a record imported from iNaturalist, that record's own point rounded to the grid. Our database rounds every stored point to the grid, including points written by older versions of the app. The point draws trip maps (yours, and the map of a trip for the people who can see that trip) and the map in your year reel, tells which US state a record is in, and lets us recognise when you and a trip mate logged the same find. Planned trip stops are kept the same way.
- No photo EXIF or GPS metadata. Every image is re-encoded on your device before upload, which discards all embedded metadata, including GPS coordinates, camera serial numbers and timestamps. Before that, the app reads one thing on your phone: the day the photo was taken, to suggest the date of your observation. The original file never leaves your phone.
- No continuous or background location tracking. Location is read only while you use one of the features in §2, one reading at a time.
- One thing we cannot strip: what you type. Notes, day journals, area names and the names and notes of planned stops are free text, stored as written, and so are place names an import brings in from iNaturalist. Area names are shown to everyone who can see the observation and cannot be made private. Notes are shared with the people who can see the observation, and day journals with your trip mates, unless you mark them private. A friend who accepts your tag on an observation gets a copy of a note you did not mark private. If you write a precise locality there, the people who can see it will read it. Agama cannot police what you choose to write.
- No sale of personal data. We do not sell, rent, or share your personal information for advertising or profiling, and we do not build advertising profiles.
4. Why we process your data, and on what legal basis
For users in the EU/EEA and the UK, our legal bases under the GDPR are:
| Purpose | Legal basis |
|---|---|
| Creating and running your account | Performance of a contract |
| Storing and displaying your observations, trips, checklists and photos | Performance of a contract |
| Showing your profile and content to people according to your settings | Performance of a contract |
| Notifications in the app, such as a new follower or a trip invite | Performance of a contract |
| Notifications on your phone | Your consent, given and withdrawn in your phone's settings |
| Answering feedback you send | Performance of a contract |
| Managing your Supporter subscription, if you buy one | Performance of a contract |
| Essential service emails (password reset, account notices) | Performance of a contract |
| Keeping the service secure, preventing abuse and reviewing reports | Legitimate interests |
| Crash reports and app versions, to fix problems | Legitimate interests |
| Usage events, to see which parts of Agama to improve | Legitimate interests, with a switch in Settings to turn them off |
| Suggesting people you may know | Legitimate interests |
| Telling you a new version of the app is out, or reminding you once to start your life list, in the app, by a notification or by email | Legitimate interests. These are sent whatever your notification switches in Settings say; your phone's own settings still apply, and you can ask us to stop the emails at any time |
| Backups, so a failure does not lose your records | Legitimate interests |
| Reviewing photos proposed as reference images | Legitimate interests, and your choice to propose one |
| Recording why you cancelled Supporter, if you choose to tell us | Your consent |
| Complying with legal obligations | Legal obligation |
Where we rely on legitimate interests, you can object at any time by writing to support@agamaapp.com. For usage events you can also use the switch in Settings.
We do not rely on consent for the core service, except where stated (for example device permissions for camera, photo library, location and notifications, which you grant or refuse in your operating system and can change at any time).
5. Who can see what
- Anyone signed in can see your name, @handle and profile photo, how many people you follow and follow you, and whether you are a Supporter (with the month you started).
- Your followers. Agama uses one-way follows. By default anyone signed in can follow you, and right away sees your observations with their dates and broad areas, your life list, your trophies, your trips (including a trip you are on right now, and its countries), your photos, the notes you did not mark private, and the lists of who you follow and who follows you. In Settings → Profile & privacy you can Require approval to follow and approve new followers first, and turn off Show photo gallery to followers to hide your photos from your followers in your gallery, their feed and your observations. Two things stay visible: trip mates see the photos on a shared trip, and the cover photo you set for a trip that is visible to followers is shown with the trip to the followers of everyone on it. Each trip has a Visible to followers switch, which hides the trip itself but not the finds logged on it; only the trip's owner can change it. You can remove a follower, and you can block accounts.
- Blocking someone ends any follow between you and hides your observations, photos, trips, lists and suggestions from each other. They can still find your name, @handle and profile photo in search. It does not remove them from a trip you share, and it does not stop them joining with an invite link they already have: remove them from the trip too.
- People suggestions. Agama may suggest your profile to people who do not follow you, for example because you share a trip or friends, have records in the same country, or have been active lately. The suggestion can name that country.
- Trip members see everything logged on a shared trip, whoever logged it: observations, places on the trip map, photos and shared notes. The owner or a co-owner adds members, and anyone who opens a trip invite link in the app joins the trip. The link keeps working and the app cannot turn it off, so share it only with people you want on the trip; someone you remove can rejoin with the same link. To stop a link, write to us. A trip that is visible to followers also shows on each member's profile, with who went, to that member's followers.
- Links you share. Anyone who has a trip invite link, signed in or not, can see the trip's name and dates, the owner's name and @handle, the countries it has records in, and how many species and observations it has. Never an area or a spot.
- Shared observations. When a friend accepts your tag on an observation, their copy, with any note you did not mark private, is shown to their followers under their settings. A trip mate who taps I was there on your find also gets a copy, with its date and area but not your note. People who can see either copy can see that you logged it too, and whether it was a new species for you.
- Checklists you publish can be seen and taken by anyone signed in. You can see who took yours.
- Photos are stored in a private location. In the app they are shown through signed links that stop working after an hour. Links to feedback screenshots in the emails we send ourselves work for up to 30 days.
- Reference images are public. If you propose one of your photos as a species' reference image and we accept it, that image becomes public: anyone can see it, in Agama or at its web address, signed in or not, credited with your @handle, under the licence you chose. This is the one case where Agama itself makes a photo you uploaded public, and it only ever happens because you proposed it. See the Terms of Service for the details. Keep in mind that trip mates can share what they see: the cover photo you set for a trip is the default picture on their trip share card, and a trip report they export includes everyone's shared notes.
- Reports you make go to us for review.
6. Service providers and third parties
These are all the services that receive personal data from Agama.
| Provider | What they do | What they receive |
|---|---|---|
| Supabase | Hosts our database, authentication and file storage, in the EU (Ireland) | All account data and content described above |
| Sentry | Crash and performance reports, in the EU, so we can find and fix problems | When the app is opened and whether it crashed, the error, your device model, system and app version, your account ID (never your email or name), and a short trail of the screens you opened, the buttons you tapped and the addresses of the requests the app made just before. Never your photos, notes or the content of your records |
| Expo | Delivers push notifications and app updates | Your device's push token and the text of each notification, for example a friend's name and a species. When checking for updates, a random ID for this install, your platform and app version |
| Apple / Google | App distribution, in-app purchases, Sign in with Apple or Google if you use it, delivery of push notifications, maps, and your phone's own place-name lookup | Governed by their own privacy policies. The trip map and the map you pick a place on are Apple Maps on iPhone and Google Maps on Android, which load the area on screen. When you use your location, search for a place, tap a point on a map or save an area name you typed, your phone's own map service receives that position (rounded to the grid in §3), point, text or name with its country, to find a place name or its centre. Opening a trip map does the same for your records on it that have no point yet. On sign-in we receive your email, and a name as described in §2. If you subscribe, they are the seller and process your payment; we never receive your card details |
| RevenueCat | Checks and manages the Supporter subscription (receipts, renewal status) | For every signed-in user, your Agama account ID and basic device and app details, so the app can check whether you are a Supporter. If you subscribe, your purchase and subscription status from Apple or Google. No email, photos or observations |
| Resend | Sends our emails: sign-in and password reset, Supporter confirmations, service announcements, and our own alerts about feedback | Your email address, your first name and the message. For feedback, an email to us with what you wrote, your account ID, your app version and phone system, and links to your screenshots that work for 7 days. Once a week, a summary to us with each message of the week, its sender's @handle and screenshot links that work for 30 days |
| Cloudflare and Google | Forward and store the email sent to support@agamaapp.com | Everything you email us, and our own feedback alerts and weekly summaries, kept in our mailbox |
| GBIF | The occurrence counts behind Explore and the species list, and region search | The species, country or region you look at, region names you type, and a position: for "near you" your approximate position rounded to the grid in §3, or the point of a place you searched. Each is used for that search only. Never your observations |
| Photon (komoot) | Place-name search when you name an area, and matching places when you import records | The place text you type or import. For an imported iNaturalist record that has only coordinates, that point rounded to the grid in §3. Nothing else from your records |
| iNaturalist | Importing your observations, and hosting most reference images | If you import from iNaturalist, the username you enter, to read your public observations. Your phone loads reference images straight from iNaturalist's servers (stored with Amazon Web Services), so they see your IP address and which image is shown |
| Wikimedia Commons | Hosting some reference images | Your phone loads those images straight from Wikimedia's servers, so they see your IP address and which image is shown |
| Cloudflare | Hosts agamaapp.com, and keeps a weekly backup copy of stored photos | Website visitors' IP addresses, and a copy of the photos and screenshots in our storage |
| GitHub | Runs our scheduled jobs: the backup, the daily cleanup that deletes the photos of deleted accounts, and a weekly usage summary | Data passes through while a job runs. The job logs keep counts, not file names or contents |
The Home world map and the map on a trip share card are drawn on your phone from outlines shipped inside the app, so nothing is sent to draw them.
Scientific names and taxonomy come from the Catalogue of Life, most common names from iNaturalist, and checklists and occurrence evidence from GBIF. Native or introduced status draws on the sources listed in the Terms of Service. Reference images come from iNaturalist, Wikimedia Commons and Agama users, credited to their photographers. Beyond what the table says, these sources receive none of your data.
We do not use advertising SDKs. If this list changes, we will update this section before it happens.
Our website. agamaapp.com sets no cookies and runs no analytics, and its fonts and images are served by the site itself. Cloudflare, which hosts it, handles your IP address to deliver the pages. A page for a shared link asks our database at Supabase for the trip summary it shows, so Supabase sees your IP address too. On an iPhone, Safari may ask Apple for the app's details to show its download banner.
7. International transfers
Our database and file storage are hosted by Supabase in the EU (Ireland), and crash reports by Sentry in the EU. Some providers in §6 are based in, or process data in, the United States, including Apple, Google, Expo, RevenueCat, Resend, GitHub and Cloudflare. Where we use a provider there, the transfer is covered by the EU-US Data Privacy Framework or the European Commission's Standard Contractual Clauses. iNaturalist and Wikimedia are different: we have no contract with them. Your phone contacts them directly to load images and, if you import, to read your iNaturalist records, and their own privacy policies apply.
8. How long we keep things
- Account data and content: for as long as your account exists.
- After you delete your account: your profile, observations, photos, checklists and the trips only you are on are deleted from our live database straight away, and the photo files within a day. Our backups lose them within 30 days. People who took a checklist you published lose it too.
- What stays with other people: a trip you shared passes to the member who has been on it longest. It keeps its name, dates, countries, notes, planned stops and target species, without your name; your observations, photos and day notes on it are deleted, and so is its cover photo if you set it. Copies of your finds that friends or trip mates added to their own lists stay with them, with any note you did not mark private.
- What we keep without your name: feedback you sent, why you cancelled Supporter if you told us, and usage events. These, and the same records of people who keep their account, are deleted after two years. Feedback emails already in our mailbox keep your account ID or @handle until we delete them, which you can ask us to do.
- Our providers' own records: RevenueCat keeps the record it holds under your account ID, which exists for everyone who has signed in, and Apple, Google and RevenueCat keep their purchase records. Crash reports expire at Sentry, email records at Resend and server logs at our providers, under their own retention periods.
- One exception: a photo of yours that we accepted as a species reference image stays in the app with your credit, because it has become part of the shared reference data other people rely on. You can ask us to remove it and we will act on that request. See the Terms of Service.
9. Your rights
You can export your observations as a spreadsheet, and delete your account and its contents (see §8 for what stays), from Settings, without contacting us. Photos are not part of the export: for a copy of them, or of anything else we hold about you, write to us.
Depending on where you live, you also have the right to access, correct, delete, restrict or object to our processing of your personal data, to data portability, and to withdraw consent where we rely on it. Write to support@agamaapp.com and we will respond within the time the law allows (one month under the GDPR). You may also complain to your local data protection authority; in Belgium that is the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données).
10. Security
Photos are stored in a private bucket and shown in the app through links that expire after an hour, access to database rows is enforced per user at the database level, traffic is encrypted, and passwords are hashed by our authentication provider. No system is perfectly secure, but we do not store the information that would do the most damage if it leaked: the exact spot of a find. The closest we keep is the rounded point in §3.
11. Children
Agama is not directed at children under 16, and we do not knowingly collect their personal data. If you believe a child has created an account, write to support@agamaapp.com and we will remove it.
12. Changes to this policy
If we make a material change, we will tell you before it takes effect, in the app or by email, and the next version of the app will ask you to accept the new text. The "last updated" date at the top always reflects the current version.
13. Older versions of the app
Versions of the app before 1.0.3 differ in a few ways. Update the app to get the behaviour described above.
- They send the position Explore and the species list use, and the position from your location button, to GBIF and to your phone's map service as the phone read it (a rough reading), not rounded to the grid.
- They send Sentry the full address of each request, which can include that position, what you typed in a search and the iNaturalist username you import from, and the app's console messages.
- On iPhone, they check the internet connection with Google about once a minute while the app is open, which shows Google your IP address.
- On Android, they ask for precise location (though they only take a rough reading) and list a microphone permission they never use.
- They have no Share usage statistics switch. If you turn it off in a newer version, our database stops accepting usage events from your account in every version. You can also write to us.
- Versions before 1.0.2 put a code on the share card for a new species. It opens a page with the species and your name and @handle, and links made then still work.
Contact: support@agamaapp.com · Ramon Duran Romaña, Groot Begijnhof 40, 3000 Leuven, Belgium