Privacy policy
The short version
Recce is used on productions under NDA, so we collect as little as we can. No ads, no analytics, no tracking, no third-party SDKs, no selling or sharing your data, and no AI training on your content.
You sign in with a Recce account. Projects you keep on your phone stay on your phone. Projects you put in the cloud are end-to-end encrypted: their photos, clips, names, notes, boards, schedules, references and LUTs are encrypted on your devices with keys only you and your team hold, so we can't see any of it. What we can see is listed below. Looking up a shot's address and maps goes straight from your phone to the map services named below.
On your device
Recce keeps everything it makes on your phone: projects, captured stills, storyboards, lens kits, and settings live in the app's local storage. Stills are added to your Photo Library only if you turn that on. Exports — images, PDFs, video — leave the device only when you share them yourself. A project leaves your phone only if you put it in the cloud (below).
Your account and Recce Team
Recce Team is the cloud side of Recce: your projects on all your devices, shared with your crew, and on the web at recce.team. Here is what it keeps.
Account. Your email address, name, crew color, and profile picture if you add one. Your password never reaches us: your device sends a one-way value derived from it instead. If you sign in with Face ID, we store the passkey's public key, never anything biometric.
Your projects. For projects you put in the cloud we store, encrypted so we can't read them: the photos, clips, previews, log masters, originals (when a project keeps them in the cloud), LUTs and their names, camera profiles, boards, schedules, notes, scene names, references, and the camera settings and address saved with each shot. GPS coordinates are removed before anything is stored. What stays readable to us, because the service needs it: the project's name (use a working title if it matters), who is in it and what they can do, when things were made and their sizes, the order of frames on a board, and which frames have a heart in a shared gallery. A project made before encryption existed stays readable to us until its owner encrypts it from the project menu. Your personal reference library (images you keep outside any project on recce.team) is encrypted too, with a key only your account holds.
Sharing. Who is in each project, what they can do, and the invitations you send by email or link. Phones in the same project can also sync directly with each other on a local network; that traffic is encrypted with a key for that project and doesn't pass through us.
Devices and security. The devices you're signed in on, when they were last used, and an approximate place worked out from the network address, so you can spot a sign-in that isn't you. Records of sign-ins, downloads and account changes, kept for up to 12 months to protect your account.
Subscription. Apple handles payment. We receive only what's needed to know your subscription is active: a transaction ID, the product, and its renewal and expiry dates. Never your card or Apple ID.
We use this only to run Recce: sign you in, store and sync your projects, show them to the people you share with, send sign-in codes and invitations, keep accounts secure, and know whether your subscription is active.
These companies process it for us, on our instructions and for nothing else: Cloudflare hosts Recce Team and stores projects and the database, in the United States (Cloudflare's privacy policy); Resend sends sign-in codes and invitation emails (Resend's privacy policy); and Apple handles App Store purchases. We share data with anyone else only if the law requires it, and we'll tell you when we're allowed to.
Who can see your projects. You and the people in projects you share. Because projects are end-to-end encrypted, nobody at Scratch Test, and nobody who got into our servers, can see what's in them. If you lose both your password and your recovery key, we can't recover it for you either.
Addresses and maps
All of this starts from a shot's location, so none of it happens for frames captured without one.
Addresses. When you capture a frame with location, Recce asks Apple for the street address at that spot and saves it in the shot. Frames captured within about 150 m of the last lookup reuse that address.
Location map. Opening a tagged shot in the gallery shows a small Apple map of the spot. Recce also starts downloading the sun map's data for that area in the background, so the sun map is ready when you tap through.
Sun map. Tapping the location map opens the sun map, which draws the ground, buildings and trees around the shot, lit by the sun. While it loads it shows an Apple map, and it asks Apple for the place's time zone so times read in local time.
These are the services involved:
Apple provides the map, addresses and time zones through Apple Maps. See Apple's privacy policy.
Amazon Web Services stores the ground heights (the Terrain Tiles dataset, kept on Amazon S3 by the Linux Foundation's Mapzen project) and the tree heights (the canopy map made by Meta and the World Resources Institute, kept on Amazon S3 by Meta). See the AWS privacy notice. Because each dataset sits in its publisher's own storage, the publisher may see those requests too, under the Linux Foundation's privacy policy or Meta's privacy policy.
OpenFreeMap provides building outlines and heights, streets and water, drawn from OpenStreetMap. See OpenFreeMap's privacy policy.
Each of these services sees a standard web request: your phone's IP address and the map tiles or spot it asked for, which shows roughly the area you're looking at. Recce adds nothing that identifies you, and nothing from your projects is sent.
Downloads are kept in the app's cache on your phone, so a place you've opened before can draw again without a connection. iOS may clear that cache when storage runs low. The DIRECTIONS button hands the shot's coordinates to your maps app.
Permissions
Recce asks for up to four permissions, and only the first is required:
Camera. The viewfinder is a camera app. Without it there is nothing to frame.
Photo Library (add only). Used only to save your captured stills to Photos, if you turn that on. Recce cannot read your existing photos.
Location (while using the app). Tags each captured frame with where the shot was found, so scout boards can show it. The tag is stored in the shot on your device and used for the address and maps described above. Exports include the address unless you turn that field off, and the coordinates only if you turn them on. Decline it and everything works, untagged.
Microphone. Asked for only when you turn on Record Sound in Settings, to record sound with video takes. The sound stays with the take on your phone until you export it.
Keeping and deleting
Your projects stay in the cloud until you delete them, or delete your account. Deleting your account signs you out everywhere and deletes your account, your projects and their files right away; the remaining records are removed within 31 days. Photos you added to someone else's project belong to that project. Teammates' originals in a project you delete are kept for them for 30 days, then deleted. You can download a copy of your account data at any time from your profile on recce.team.
Your rights
Wherever you live, you can ask us to access, correct, export or delete your data, and a person will answer within 30 days. California residents have these rights under the CCPA/CPRA; we don't sell or share personal information as those laws define it. People in the EU and UK have rights under the GDPR; our legal basis is providing the service you signed up for, and our legitimate interest in keeping it secure.
Children
Recce is made for professional use. It isn't directed at children under 13, and we don't knowingly collect their data.
Security
Data is encrypted in transit and at rest, your password is never sent to us, sign-in can ask for a second factor, and projects can be end-to-end encrypted. No system is perfectly secure; if a breach affects your data we'll tell you as the law requires.
Changes
If this policy changes, the new version will be posted at this address with a new effective date, and we'll tell you in the app or by email if the change is significant. The Terms of Use cover the subscription.
Contact
Scratch Test · [email protected]