Creating an account requires an email address. You can sign in three ways: email and password, Sign in with Google, or Sign in with Apple. When you use Google or Apple, we receive only what that provider shares to identify your account — typically your email address — never your password.
Your email address is never shown to other spotters.
By default, your sightings and lists are signed with a handle taken from the part of your email address before the @ — so amelia@example.com posts as @amelia. Other spotters see that handle. They never see the full address.
If you'd rather not show it, open the profile menu on the feed and choose Privacy, then turn on Hide my user name. New posts are then signed @anonymous instead. The same screen has an option to rewrite the handle on everything you've already posted.
Posting anonymously changes only what other spotters see. Your posts remain linked to your account internally, so you can still edit and delete them, and so blocking and reporting keep working.
Squawk1200 asks for your location only at the moment you attach a photo to a sighting. It's used once, to suggest the nearest airport for that sighting — either from the photo's embedded GPS data or your device's position if you shoot from within the app.
Your exact coordinates stay on your device. To find nearby airports, the app rounds your position to an approximate area — roughly a ten-kilometre grid — and only that approximate area is sent to our server. The precise position is never transmitted and never stored.
We don't track your location in the background, keep a location history, or use it for anything beyond that single suggestion.
Camera access is requested only when you choose to take a photo for a sighting. Photos you attach are uploaded to our storage and linked to the sighting — that's the only time an image leaves your device.
The rest of what we hold is what you type in: tail numbers, aircraft models, airport codes, captions, and any spotting lists you build. This is the data the app is built around — your logbook.
Squawk1200 is a shared feed, not a private diary. Sightings you post, and any list you mark public, are visible to other Squawk1200 users, along with the handle described in § 02. Lists you keep private stay private — only you can see them.
Every sighting posted by someone else has a ••• menu offering Report Sighting and Block Spotter.
When you report a post, we store what you reported, the reason you chose, any note you added, and who posted it, so the report can be reviewed and acted on. Reports are visible only to you and to us — never to the person you reported.
When you block someone, we store that you blocked them so their sightings and lists stay hidden from you. Blocks are private; the blocked spotter isn't told. You can undo a block at any time under Privacy.
Squawk1200 runs on Supabase for authentication, our database, and photo storage. Google and Apple are involved only at sign-in, to confirm who you are.
We don't run advertising, and we don't use analytics or tracking SDKs. We don't sell your data or share it with data brokers.
Your sightings and lists stay in your account until you remove them or delete your account.
To delete a single sighting, open it and use the edit screen — there's a Delete Sighting button there.
To delete your entire account, open the profile menu and choose Delete Account. This happens immediately and cannot be undone.
Deleting your account permanently removes the account, every photo and caption, your handle everywhere it appeared, your lists, and your blocks and reports. One thing is kept: the bare sighting record — aircraft, airport, and date — with nothing connecting it back to you.
If you'd rather every trace be erased entirely, or can't reach the in-app option, write to the address in § 12 and we'll handle it.
Squawk1200 isn't directed at children under 13, and we don't knowingly collect information from them.
If this policy changes in a meaningful way, we'll update the effective date above and, where it affects you materially, let you know in the app.
Questions about this policy, your data, or content you've reported — john@itmovesco.com.