Skip to content
PicAnchor
OverviewTeamsReportsPlansFAQ
Sign in (opens in a new tab)
Language11 languages
  • EnglishEnglish
  • Bahasa IndonesiaIndonesian
  • FilipinoFilipino
  • 日本語Japanese
  • 한국어Korean
  • LietuviųLithuanian
  • Bahasa MelayuMalay
  • ไทยThai
  • Tiếng ViệtVietnamese
  • 简体中文Chinese (Simplified)
  • 繁體中文Chinese (Traditional)
Get the app
OverviewTeamsReportsPlansFAQSign in (opens in a new tab)Get the app

Legal

Privacy policy

Effective date: 9 July 2026  ·  Last updated: 20 November 2026

On this page

  1. 1. Who we are
  2. 2. The data we collect
  3. 3. Who controls your data (controller and processor)
  4. 4. How we use data
  5. 5. Legal basis and consent
  6. 6. Sharing and third-party services
  7. 7. Storage, location, and retention
  8. 8. Security
  9. 9. Your rights
  10. 10. Children
  11. 11. Changes to this policy
  12. 12. Photo verification registry
  13. 13. Customer proof links
  14. 14. People who contact us
  15. 15. Contact
On this page
  1. 1. Who we are
  2. 2. The data we collect
  3. 3. Who controls your data (controller and processor)
  4. 4. How we use data
  5. 5. Legal basis and consent
  6. 6. Sharing and third-party services
  7. 7. Storage, location, and retention
  8. 8. Security
  9. 9. Your rights
  10. 10. Children
  11. 11. Changes to this policy
  12. 12. Photo verification registry
  13. 13. Customer proof links
  14. 14. People who contact us
  15. 15. Contact

This policy explains how PicAnchor handles personal data. Because PicAnchor is used by businesses to document their own field teams, parts of this policy distinguish between data we control and data our business customers control. Please read Section 3 carefully.

1. Who we are

PicAnchor ("PicAnchor", "we", "us") is a field-documentation application and web dashboard that lets organisations capture photos stamped with a verified time and location, and manage those photos across a team. This policy is published by Baturlabs Ltd, a company registered in England and Wales ("the Operator"), contactable at hello@picanchor.com.

This policy applies to the PicAnchor mobile app, the PicAnchor web dashboard, and the picanchor.com website (together, the "Service").

Not every feature this policy describes is available on every platform or in every version of the Service. Where a feature - such as accounts, company sync, or paid plans - is not offered on the platform or version you are using, the sections describing that feature simply do not apply to you.

2. The data we collect

We collect only what the Service needs to function. What is collected depends on how you use it.

CategoryWhat it includesWhen
Admin accountEmail address and password (stored encrypted), company name you enter. Optionally, company details you enter: an address, a phone number and a contact email. They are stored with the company and visible to that company's members, used in company details and on Site reports, not shown to anyone outside the company unless you include them in a Site report you export and share, and deleted with the account.When an admin signs up for the dashboard.
Subscription dataProduct, transaction reference and status (active, free trial, ended), from Apple or Google, to apply your company's plan; kept while the company account exists.When a company subscribes to a Fleet plan in the app.
Billing data (web plans)For a plan bought on the web: the company name, billing address and tax or company registration number the admin enters, the admin's email, the plan, its status and dates, and the invoices. Card details are typed on Stripe's page and never reach us: we see only the card's brand, last four digits and issuing country (we also keep the country of the buyer's IP address at the time of purchase, as evidence of where the buyer is), and Stripe's references for the customer and subscription. Invoices and tax records are kept for 6 years; the rest is kept while the company account exists.When an admin buys a plan on the web.
Worker identityThe display name your admin registers for you and a join code. Workers do not provide an email or password; sign-in is anonymous and linked only to a worker entry your admin created.When a worker joins a company by name + code.
Photos & their stampThe photos you capture, and the information stamped on them: date and time, GPS coordinates, a reverse-geocoded address, and any note you type.Each time a photo is captured and synced.
ProjectsIf your company uses Projects: the project name, reference, dates and times, customer name and phone number, places (addresses, map links and coordinates), notes, the workers assigned, and who marked it complete or approved it and when. Entered by the company's admin and visible to that company's admin and to the workers assigned. An admin can archive a project and then delete it: its photos and site reports are kept and no longer belong to a project (unless the admin also moves the photos to Recently Deleted), its assignments are removed and its customer links stop working; all of a company's projects are deleted at once when the company account is deleted. Deleting a worker removes their assignments and their name from completion and approval records.When an admin creates or edits a project, or a project is marked complete or approved.
Site reportsIf your company uses Site reports: the report header (title, job reference, project, site address, date, who prepared it, and the company name, address, phone number and email you choose to show); the text written on each page (location, item, observation, action required, who is responsible, due date, status); and a copy of each page's photo. Each page also keeps what was stamped on its photo when it was added: time, address, coordinates, the worker's name and the company name. Photos added from a phone's library are uploaded with all location and camera details removed; only the date the photo was taken is kept. We also record who last changed each report and field and, if two people change the same text, the text that was replaced, for 30 days. A report can be opened by the person who created it and by the company's admins, and by no one else. It is kept until it is deleted (Section 7).When a report is created or edited and the phone or dashboard syncs it.
Customer linksWhat Section 13 lists, shown read-only to anyone who holds the link. For each link we keep who made it, its expiry date, whether it is revoked, how many times it was opened and when it was last opened; never who opened it.When an admin (or a worker the company allows) creates a link. Deleted 30 days after it is revoked or expires.
Proof registrationA fingerprint of the photo file, its verification code, the capture time and whether that time came from the network or the device clock. Never the image (Section 12).Each time a photo is captured, with or without an account.
Support requestsWhat you send from Help > Contact support in the app: the type of request, your message, the reply email you give (optional) and a screenshot or photo if you attach one. If "Include app details" is on, also the app version, phone model, system version, app language, and your company and role; never your location. If you are not signed in, a random identifier the app creates for this form, used only to limit sending to 5 an hour. We store it in our database (Section 7), email it to our support inbox (Zoho Mail), use it only to answer you, and delete it after 12 months.When you send a support request.
LocationDevice GPS location, used to stamp photos and detect falsified ("mock") location. Location is used at the moment of capture; we do not continuously track device location in the background.While capturing a photo, with your permission.
Technical dataBasic information needed to operate and secure the Service, such as whether a photo has been synced and the time zone it was captured in. The app and the dashboard use no analytics or crash-reporting services and collect no hardware identifier - no IMEI and no advertising ID; a worker's device is linked to their account only by a random, app-generated identifier that keeps one worker account bound to one device. The picanchor.com website uses Vercel Web Analytics to count page views. It sets no cookies, stores nothing on your device, and does not identify you or track you across other websites. We see only totals, such as pages visited, the referring site, country and device type. To show prices in your currency, the website uses your approximate country, which our host works out from your IP address. We do not store it. If you choose a country at the bottom of the page, the website remembers it on your device. The website opens in the language that matches your country. If you choose a language, the website remembers it in a cookie on your device.During normal use.

The PicAnchor app works locally without an account. If you never sign in as an admin and never join a company as a worker, photos stay on your device and are not sent to our servers. A fingerprint and the capture time are registered so your photo can be verified later (Section 12); your location and the photo itself never leave your device unless you use an account.

3. Who controls your data (controller and processor)

This is important for understanding your rights.

  • When a business uses PicAnchor to document its team - the photos, reports, worker names, and related records belong to and are controlled by that business (the admin's company). That business is the data controller. PicAnchor acts as a data processor, storing and processing the data on the business's behalf and under its instructions. If you are a worker, requests about your data (access, correction, deletion) are normally directed to your employer/the company that registered you, who decides how that data is used and retained.
  • For your PicAnchor account itself - such as an admin's email used to sign in, and the website - the Operator is the data controller.

4. How we use data

  • To provide the core function: stamping photos with verified time and location, and proving they have not been altered.
  • To sync photos to a company's private storage and show them in that company's dashboard.
  • To let admins manage workers, generate reports (PDF "report"), and apply a consistent stamp across a team.
  • To save Site reports to your company account, show them to the person who wrote them and the company's admins, keep their edit history, and fill in company details on them.
  • To remind you of upcoming work. If you allow notifications, the app schedules reminders for the projects assigned to you on your device. A reminder shows only the project name and start time, never the customer, phone number, address or notes, and nothing about reminders is sent to us.
  • To operate, secure, and improve the Service, and to provide support.
  • To apply your company's subscription from Apple or Google (we receive its status and references only).
  • To take payment for web plans, issue invoices, keep tax records, and check that a card is from the country whose price is being paid.

We do not sell personal data. We do not use your photos or location to build advertising profiles, and the Service does not display third-party advertising.

5. Legal basis and consent

We process personal data where you (or the business you work for) have given consent, where it is necessary to provide a service you have requested, and where we have a legitimate interest in operating and securing the Service. For web payments we rely on the contract with the company that buys, on our legal duty to keep invoices and tax records, and on our legitimate interest in preventing misuse of country pricing. For workers, the lawful basis for processing field documentation generally rests with the employing company that registers you and instructs the documentation. The Operator is established in the United Kingdom, and we handle personal data under the UK General Data Protection Regulation (UK GDPR).

6. Sharing and third-party services

We share data only with service providers that help us run the Service, and only as needed:

  • Cloud hosting and database - photos and records are stored with Supabase, our hosting and database provider, on our behalf, in private, access-controlled storage. Supabase runs on Amazon Web Services infrastructure in Tokyo, Japan (AWS ap-northeast-1). Each company's data is isolated from every other company's data.
  • Vercel (hosting for picanchor.com and the dashboard, and website page-view counts).
  • App stores and payments - Fleet plans (Pro and Pro+) are bought inside the app as subscriptions through the Apple App Store or Google Play. Apple and Google process the payment; we do not receive or store your card details. We receive the subscription's status and the store's references for it (the product, the transaction reference, and whether it is active, in a free trial or has ended) and link them to your company so that its plan can be applied.
  • Stripe (web payments) - plans bought on the web are paid by card through Stripe, which processes the payment and sends us the plan's status and references: a customer and subscription reference, the card's brand, last four digits and issuing country, and the invoice. Stripe issues the invoices on our behalf. For its own legal and fraud-prevention purposes Stripe is an independent controller and handles card data under its own privacy policy (stripe.com/privacy). Stripe may process data outside the United Kingdom under its own safeguards. Here, Stripe means Stripe Payments UK Ltd and Stripe Payments Europe Ltd.
  • Maps / reverse geocoding - GPS coordinates may be sent to a mapping service to produce a human-readable address for the stamp.
  • Legal - we may disclose data where required by law or to protect rights and safety.

7. Storage, location, and retention

Synced photos and records are stored in private cloud storage provided by Supabase, hosted in Tokyo, Japan (AWS ap-northeast-1). Supabase provides that storage on Amazon Web Services infrastructure, which acts as our sub-processor. How long a synced photo is kept depends on the company's plan when the photo is uploaded: 1 year on a paid plan (Pro or Pro+), 30 days on Free, after which it is automatically deleted from storage. If a plan ends, photos uploaded during the plan are still kept for 1 year, and new photos follow the Free limits. If a company upgrades, its Free photos are kept for 1 year too. On Free, a company can store up to 100 photos uploaded while on Free. Photos uploaded during a paid plan don't count toward it. Once that limit is reached, further photos remain on the worker's device and are not uploaded until space is freed or the plan is upgraded. Businesses that control their data may also delete workers and photos at any time from the dashboard. Photos deleted from the dashboard are held in Recently Deleted for 30 days, where an admin can restore them, and are then removed from storage; photos kept after a worker is removed retain only the worker's name as recorded at the time of capture, so the documentation remains intact.

Site reports and the copies of photos inside them are not part of the photo schedule above. They are kept until the company deletes them. A deleted report, or a page removed from a report, is held for 30 days, where it can be restored, and is then removed from storage together with its pictures. The record of replaced text is removed after 30 days. If a worker is removed from the company, their reports stay available to the company's admins and keep the worker's name as the author, so the documentation remains intact. When a company account is deleted, all of its Site reports and their pictures are deleted with it.

Customer links are deleted 30 days after they are revoked or expire, whichever comes first (Section 13).

Verification registry entries are kept indefinitely, and that is deliberate: a verification code printed on a photo or a report must still work years later, for someone who was never our customer. You can ask us to erase an entry (Section 9). A photo synced to a company is deleted from company storage on the schedule above; its registry entry is not, so a photo can be gone from a company's dashboard while its verification code still answers.

Anonymous sign-ins (how a worker joins a team without an email or password) are deleted automatically, together with their sessions, once they belong to no team and have been neither created nor used in the last 90 days. One is kept while it still owns files it uploaded, or if it was used to create or accept a team invite link or to set up a company.

8. Security

We protect data with measures including isolated per-company access controls (so one company cannot see another's data), private storage that is not publicly accessible, encrypted transmission, and features that help detect changes to photos, built into the stamp (network-derived time, mock-location detection, and a digital fingerprint on each photo). No system is perfectly secure, but we work to protect your data in line with industry practice.

To stop worker join codes being guessed, we limit repeated failed attempts to join a company. To do that we store a scrambled, one-way form of the network address and an anonymous session identifier for up to two hours. They are used only for that limit, are never linked to photos or an account, and are deleted automatically.

9. Your rights

Subject to applicable law, you may request to access, correct, or delete your personal data, and to object to or restrict certain processing. Because much of the data is controlled by the business that uses PicAnchor (see Section 3), workers should usually direct these requests to their employer/the company that registered them. For data the Operator controls, or if you are unsure who to contact, write to hello@picanchor.com and we will help route your request.

You can also ask us to erase a verification registry entry (Section 12) by writing to hello@picanchor.com; there is no in-app control for this today. The entry then answers only "revoked" to anyone who looks it up: the capture time and the time source are removed and cannot be recovered. We keep the fingerprint itself, the verification code and the time we first received them, because releasing the fingerprint would let someone else register the same file later and claim an earlier date for it. We also keep a count of how many times the same file was submitted and when it was last seen. Erasure cannot be undone.

10. Children

PicAnchor is a tool for workplaces and is not directed to children. We do not knowingly collect personal data from anyone under the age of majority in their jurisdiction. If you believe a minor has provided data, contact us and we will remove it.

11. Changes to this policy

We may update this policy as the Service evolves or as the law requires. We will revise the "Last updated" date above and, for significant changes, provide a more prominent notice.

12. Photo verification registry

The registry holds no pictures. Nothing in this section involves the photo itself leaving your device; photos are uploaded only when you sync them to a company (Sections 2 and 7).

When you take a photo, the app sends four things to our verification registry:

  • a digital fingerprint of the photo file (a SHA-256 hash - a short code computed from the file's contents; the photo itself cannot be reconstructed from it)
  • the photo's verification code - the short code printed on the photo itself, which is what someone types at verify.picanchor.com
  • the capture time
  • whether that time came from the network or from the device clock

Nothing else is sent. No location, no names, no account details, no device identifiers. The registry itself records the moment it received them, from our own clock, and, if the same file is submitted again, how many times and when it was last seen. The registry cannot tell where a photo was taken or who took it.

Registration happens for every photo you take and cannot currently be switched off in the app. If you do not want photos registered, contact us (Section 15).

This exists so that a photo can be verified later: anyone with the photo, or its verification code, can check at verify.picanchor.com when the file was registered and whether it has changed since. Because verification depends on the record being durable, fingerprint and capture-time entries are retained indefinitely.

To stop the registry being flooded, we limit how many registrations can come from one network address in a given period. To do that we store a scrambled, one-way form of that address for up to two hours. We do not store the address itself, and we create no permanent identifier for your device or installation - registrations from the same device are not linked to each other.

13. Customer proof links

A company's admin, or a worker where the company allows it, can create a link to one project to send to a customer. Anyone who has the link can open it in a browser without an account. It is read-only.

  • What it shows. The project's name, status and dates; the company's name and logo; the project's photos with their date, time, time zone and address, and whether the time was verified; and the project's Site reports, including the text, pictures, addresses and any names, phone numbers or emails written into them. It does not show the customer's name or phone number, the project's notes or any join codes.
  • Who can see it. Anyone who has the address, including anyone it is forwarded to. There is no sign-in. The company chooses who receives a link and is responsible for that choice.
  • How long it lasts. A link stops working 90 days after it is created unless the admin sets another date. The admin can revoke it at any time and it stops working at once. We store only a one-way fingerprint of the link's address, so we cannot show an old address again. A link is deleted 30 days after it is revoked or expires, whichever comes first. After that, the company can no longer see that the link existed or how many times it was opened. The company's photos and Site reports are not affected.
  • Opened. The company sees whether a link has been opened, how many times and when it was last opened. We do not record who opened it: the count carries no name, account, IP address or cookie. Opens by the admin's preview and by link-preview tools are not counted; some automated visits may still be.
  • Rate limit. To stop abuse we limit how many requests can come from one network address. We keep a scrambled, one-way form of that address, never the address itself, for up to two hours (the same short-lived mechanism as in Section 12).
  • Worker names. Off by default. Only if the admin turns it on does the page show which worker took each photo, and turning it off removes the names from the page. A name already printed on a photo's stamp is part of the picture and stays visible; turning the option off cannot remove it.

The page loads no third-party scripts or fonts, sends no referrer and asks search engines not to index it. Photos load through addresses that expire after 10 minutes. The Site report PDF and the photo download are put together in the visitor's browser.

14. People who contact us

This section is for people who reach us through a form in one of our Facebook or Instagram ads, or by email, rather than through the PicAnchor apps.

What we collect. Your name, email address, phone number, company name, team size and what you need site photos for.

Why. To answer your request, for example to send the sample report you asked for. Our legal basis is steps you asked us to take before any contract (UK GDPR Article 6(1)(b)). We follow up only on your request: at most two short reminders, then we stop. We send no newsletters unless you ask for them.

Who handles it.

  • Meta collects the form on its platforms under its own policy and passes the answers to us.
  • We use Zoho Mail to send and receive email.
  • WhatsApp is used only if you gave a phone number and we message you about your request.
  • Zoho Sheet is our lead log.

What we do not do. We do not sell this information and we do not share it for other companies' marketing. It never goes into the photo registry (Section 12). The PicAnchor apps contain no Meta tracking code.

How long. If you do not become a customer, we delete it 12 months after our last contact with you. If you do, the account sections of this policy apply.

Your rights. You can ask for a copy, a correction or deletion, or object, by writing to hello@picanchor.com. You can also complain to the Information Commissioner's Office (ICO) at ico.org.uk.

15. Contact

Questions about this policy or your data: hello@picanchor.com.
Operator: Baturlabs Ltd, a company registered in England and Wales, registered address Unit 20 Yarrow Business Centre, Chorley PR6 0LP, United Kingdom.

PicAnchor

The camera app for field teams.

Product How it works Teams Plans Get the app Check a photo guide PicAnchor vs a phone camera For construction For inspections For delivery For facilities For incidents
Check and manage verify.picanchor.com (opens in a new tab) Dashboard (picanchor.app) (opens in a new tab)
Company hello@picanchor.com Privacy Terms (opens in a new tab)
Language11 languages
  • EnglishEnglish
  • Bahasa IndonesiaIndonesian
  • FilipinoFilipino
  • 日本語Japanese
  • 한국어Korean
  • LietuviųLithuanian
  • Bahasa MelayuMalay
  • ไทยThai
  • Tiếng ViệtVietnamese
  • 简体中文Chinese (Simplified)
  • 繁體中文Chinese (Traditional)

© 2026 Baturlabs Ltd, registered in England and Wales, company no. 17294002.

Google Play and the Google Play logo are trademarks of Google LLC. Apple and the Apple logo are trademarks of Apple Inc., registered in the U.S. and other countries and regions. App Store is a service mark of Apple Inc.