Privacy Policy
1. Who is controller, surface by surface
The same person's data can sit on several surfaces with a different responsible party on each. This table is the map; the sections below give the detail. "Local" means the bytes never leave the device they were made on.
| Surface | Controller | Processor | Where the bytes are | Kept for |
|---|---|---|---|---|
Farmer's record (field.html) | the named buyer who requested it | none — nothing the farmer records reaches us from the page before Send; a short link reads the request's own words from the mailbox (§3) | the farmer's phone | 90 days on the phone; an unsent record is never pruned |
Hand-off mailbox (/api/handoff) | the buyer | Protosonic; Netlify runs the function, Cloudflare holds the bytes | an EU-jurisdiction object store (Cloudflare R2) | 14 days by default (1–30), applied on touch; no sweep job |
Due-diligence desk (dds.html) | the operator | none — local | the operator's device | until exported or cleared |
| Screen with Whisp (desk, signed in, only when pressed — or, if you switch on automatic screening where offered, when a farmer's plot arrives) | the operator | Protosonic passes the plot outline on (/api/whisp, on Netlify); FAO's Whisp is a separate recipient (§7) | the outline: FAO's Whisp service; Whisp's answer: the operator's device and the desk copy (§4) | Whisp's terms say FAO does not store or retain the outlines it is sent; the answer: as the desk |
| Satellite pictures (desk, signed in, only when pressed; only where this deployment has switched them on) | the operator | Protosonic receives one plot's box (/api/sentinel, on Netlify) and asks about a 5 km square around it; Element 84 (the catalogue) and Amazon Web Services (the archive's host) are separate recipients (§7) | the box: our function, while it runs; each picture: the operator's page view, and a cache in the EU store (§9) under a keyed hash of the box | the page view; the cache: 30 days (pictures near 2020) or 2 days (the latest), then deleted as described in §7 |
| Filing deployment (configured deployments) | the operator; the European Commission for what it receives | Protosonic; Netlify as sub-processor | transient in the function | not retained; decommissioned at end of order |
Account (account.html) | Protosonic | Netlify; an e-mail provider for the sign-in link; Google or Microsoft as identity provider if you choose Continue with Google / Microsoft | an EU-jurisdiction object store (Cloudflare R2); the journal, the vault and the anchors beside it | until the account is closed; a journal entry until you delete it or the account is closed |
The request link sent to a phone (/api/message, when a provider is configured) | the buyer | Protosonic; Netlify runs the function; Twilio (United States) carries the message | the supplier's phone number and the buyer's name and link pass to Twilio and are not stored here; the chat is linked to the request as a keyed hash of the number (never the number) until the request closes; the record files a supplier sends back over WhatsApp, Telegram, LINE, Viber, WeChat or Zalo pass through that provider into the buyer's mailbox exactly as the page's own send would | not retained by us; Twilio's own message logs under its terms |
Team (/api/team) | the team's owner for the roster; each member for their own account | Protosonic; Netlify runs the function, Cloudflare holds the bytes | the EU object store — the team's name, its members' addresses and roles, and standing invitations (an address, a role, a date); nothing else | until the member leaves or is removed, the team is disbanded, or the account closes; an invitation for 14 days |
Saved companies (/api/companies) | the operator who saved them | Protosonic; Netlify runs the function, Cloudflare holds the bytes | the EU object store, beside the desk bundle — each company's legal and trading name, addresses, registry code, EORI and VAT numbers, a contact role, e-mail and phone, as typed | until you remove the company or close the account |
| Payments and subscription | Protosonic | Stripe as payment processor; Stripe holds the customer record. Revolut Pay is a method on Stripe's pages, not a second processor | Stripe (EU) — we never receive a card number or Revolut credentials | Stripe's own retention; tax records as law requires |
API key (x-osfp-key) | Protosonic | Netlify runs the function; Cloudflare holds the bytes | the EU object store, on the account record — a SHA-256 hash of the key, never the key | until you revoke it or close the account |
| The meter (closed and one-sided counts) | Protosonic | Netlify runs the function; Cloudflare holds the bytes | the EU object store, on the account record | counts only — no record, no fingerprint, no content, ever |
| Enquiry e-mail | Protosonic | an EU hosting provider (Germany) hosts the CRM we operate; Netlify runs the same-origin door | a CRM we operate ourselves — not a third-party inbox product | up to 24 months after last contact |
| Stamp, plot, Phone Sync, map tiles | Protosonic for the hashed abuse counters only | — | your device; a digest passes through our relay | not retained; counters expire with the UTC day |
| Checking a stamp or a chain | nobody — no personal data reaches anyone | — | your device only; no server is on this path | nothing is created, so nothing is kept |
2. The farmer's record — what a farmer is owed under Art. 13, in plain words
If you are a farmer, forest owner, cooperative officer or agent using the plot page from a buyer's link, this is what you should know before you press Send.
- Who asked for it. The buyer named on the page. That buyer is the controller of the record you make for it; we are not, and nothing you record on the page reaches us except a fingerprint at seal time and, when you press Send, the deposit to the buyer's mailbox (section 3). One thing reaches us before that: when the link you were sent holds only the request code (the short link a text message carries), the page asks the buyer's mailbox for the request's own words as it opens — who is asking, for which product and in which language. That request carries the code and, as every web request does, your phone's network address; nothing you have recorded goes with it.
- What it contains. The map of your plot (a point or a shape), whether the trees were planted or natural, the species, the country, the quantity if you declared a harvest, the time your phone said it was, a photo only if you chose to attach one, and a code that identifies this phone. That phone code is a persistent identifier: records made on the same phone can be linked to each other.
- Why the buyer needs it. EU Regulation 2023/1115 obliges the buyer to hold the location of every plot its wood came from and to keep that for at least five years. That legal duty is the buyer's basis for asking; a photo or a plot name beyond it rests on the buyer's interest in evidence that can be checked and on your choice to add it.
- Where it goes. To the buyer's own files on the buyer's own computer. The buyer files a statement in the EU Information System that carries your plot's location; authorities in the country the furniture is sold in can see that statement.
- How long. Your phone keeps a copy for 90 days and then removes it; a record you never sent is never removed by us. The buyer keeps it for at least five years.
- What it proves and does not. A stamped record fixes what you declared and when. It does not prove your harvest was legal, that the forest was not cleared, or that a photo shows this plot or came from a camera.
- Your rights. To see, correct, withdraw or complain about the record, contact the buyer named on the page; a sealed record cannot be edited, but it can be withdrawn by an amendment record, and the buyer can delete it from every store it controls. You may also complain to your national data-protection authority or to the Estonian Data Protection Inspectorate about our part (the mailbox).
This notice is in English here; the plot page shows its short form in the language you chose.
3. The hand-off mailbox
Supplier hand-off (dds.html → field.html): a request link carries a random token; the supplier's phone posts the sealed plot record and its stamp to our same-origin /api/handoff/<token> mailbox (the EU-jurisdiction store named in §9, strong consistency), where it waits for the buyer's desk to collect it. A request expires 14 days after it was made (the buyer can choose 1–30): after that, the next touch of that token — a post, a pull, a request-summary read or a close — deletes the request and everything posted to it. There is no separate clean-up job: an expired entry that nobody touches again stays in the store, unread by us, until it is touched. The buyer's desk can close a request early, which deletes it at once. The mailbox holds the declared record and its seal; it cannot alter either and we do not read them. The token in the link can only post, and read the request summary below: collecting and closing need a separate desk key that the mailbox gives the buyer's desk alone and keeps only as a one-way digest, or the account that made the request, so one supplier holding the link cannot read another supplier's record. A request made without an account before this version of this notice keeps its earlier rule, under which its token could also collect and close it, until it expires (at most 30 days). Posts are counted against a hashed per-IP daily limit. Request summary: a plot page opened from a short link (the request code alone, as a text message carries it) reads /api/handoff/<token>/summary as it opens — the request's own words (the buyer's name, product, species, country, crop, language and expiry), never a deposit. That read carries the code and the phone's network address, and is counted, like posts and pulls, against a hashed per-network daily limit.
Roles. The buyer whose desk created the link is the controller; Protosonic is the buyer's processor for the mailbox, under a data-processing agreement attached to the buyer's order, and Netlify, Inc. (United States) is our sub-processor for storage. Retention is the 14-day (1–30) expiry above, applied when the token is next touched. Limits: 256 KB per deposit, 20 deposits per request, 30 requests created, 40 posts, 120 reads and a separate 120 request-summary reads per network per UTC day, declared-plot deposits only. Deposits are stored as posted, in the clear: "we do not read them" is a promise, not a lock, until deposits are encrypted to a key carried in the request link.
4. The due-diligence desk — on the operator's device, and, when signed in, a copy under the account
Due-diligence desk (dds.html), signed out: the operator's identity, product line, supplier and buyer contact details, plot geometry, evidence fingerprints, assessment and statement records stay in this browser's storage on your device; nothing leaves it. So do the sealed records a supplier sends you (with the word the supplier uses for each file it names) and the list of documents you asked each supplier for (since 25 September 2026); none of them goes into a statement or an authority pack. Sealing a record sends only its SHA-256 digest, with a fresh nonce, to the drand beacon operators and our /tsa/* relay, exactly as the stamp tool does. Exports are files you download. If you separately opt into optional usage sharing, selected named actions from this page are sent as described below; your desk content is not included.
Screen with Whisp — the one desk button that sends a plot's outline (since 26 September 2026). Signed in, after you have agreed once on that browser and only when you press Screen with Whisp, the desk sends the chosen plots' outlines to FAO's Whisp service through our /api/whisp, and keeps Whisp's answer as evidence on the product. Where this deployment offers it, you can also switch on automatic screening under Your company (off unless you do): then each plot a farmer sends back through one of your request links is screened when it arrives. What goes, to whom, and for how long is in §7.
Satellite pictures — a plot's box, never its outline (since 27 September 2026, where switched on). Signed in, and only when you press Satellite pictures, 2020 and now on a product under Your products, the desk sends one plot's box — four numbers — to our /api/sentinel and shows the two pictures that come back. The outline stays on your device and is drawn over the pictures there. What goes, to whom, and for how long is in §7.
Signed in — the desk syncs to the account (since 16 September 2026): after every save, seal, import or deletion the desk sends its whole bundle to /api/workspace, so the same desk is there on any browser you sign in on. What that bundle holds is what the desk holds: the operator record; every product with its supplier and buyer names, addresses and e-mail addresses, species and plot geometry; assessments, mitigations, statements and seals with their envelopes — never the files themselves. It is up to 2 MB, kept with the five previous versions before each overwrite, stored as sent in the EU-jurisdiction store named in §9, not encrypted on the device before it leaves (a passphrase on every browser is the friction sync exists to remove; a lock is a later option), and read by no code of ours: the server merges nothing and looks at nothing. For this copy the operator is the controller and Protosonic is the processor, under the terms. The account page shows the copy, its versions and a delete button; signed out, nothing is sent. Retention: on the device until you export or clear it — a cleared browser profile or a private window loses it, and the exported bundle is the record you keep for the EUDR five-year period; under the account until you delete the copy or close the account.
Saved companies — the one piece of desk data a function of ours reads. Signed in, the desk can keep company details under your account and fill its operator fields from them on any browser: for each company, the legal and trading name, one or more addresses, the registry code, the EORI and VAT numbers, a contact role and the e-mail and phone you typed. Unlike the desk bundle above, these are not stored-as-sent-and-read-by-nobody: the /api/companies function reads them to show them to your signed-in desk and to your own API key, and /api/stamp reads the one a call names, to write its names, numbers and the chosen address — never the contact — into that stamp's journal row, with the product and lot the call sent, if any. That row stays yours: in a team, the team's view of the journal lists your stamps to your teammates without the company, the product or the lot. An API key can read them and cannot change them. They are never sent to a timestamp authority, never put into a stamp or an envelope, never part of the nightly anchor, and never sent to anyone else; the list itself is never published. A fill only puts them into the desk's own operator fields, which are published, as before, only where you publish them. The numbers are checked for their shape only; nothing looks them up. They are usually a company's details; where a sole trader's name and home address, or a named person's e-mail, is typed they are personal data, and for them the operator is the controller and Protosonic the processor, under the terms. Retention: until you remove the company from the desk or close the account.
5. Statement filing — configured deployments only
Statement filing (dds.html, configured deployments only): the public site holds no Information System credentials, so its /api/dds/* function refuses every call. Where an operator asks for it, Protosonic operates a dedicated deployment that holds that one operator's Information System web-service key as your processor, in the deployment's environment configuration and never in the browser. When you press File, the statement you built (operator, product, quantity, plot geometry, supplier and reference details) is sent through that same-origin function to the EU Information System under your credentials. The Commission's conformance test is run on the acceptance environment before any production filing. The operator is the controller of the transmission, the European Commission is an independent controller of what the Information System receives, and Protosonic is the operator's processor. The function retains nothing; the deployment and its configuration are destroyed when the operator ends it.
6. The account, the payment and the meter
The account. Sign-in is a link sent to your e-mail address — the same message carries an 8-character code, which is how the OpenStamps app signs in, since no cookie of this site can reach a page served from the app — or Continue with Google or Continue with Microsoft; there is no password. Google and Microsoft sign-in are a top-level redirect to the provider and back: this site never loads either as a page script. The browser is sent to accounts.google.com or login.microsoftonline.com; token exchange and the address lookup run on our server (oauth2.googleapis.com and openidconnect.googleapis.com; login.microsoftonline.com and graph.microsoft.com). We receive the work e-mail the provider asserts for that account, and nothing else from that flow is used to set a plan or a price. A personal Microsoft account's address is verified by Microsoft; a work or school account's address is accepted only when Microsoft states that the organisation owns that e-mail domain, because a tenant administrator can otherwise type any address. There is no other door: no page of this site loads a sign-in script from a third party. In the app, the session is a signed value the app keeps on the device and presents as a header, never a cookie; signing out forgets it. Protosonic is the controller of the account data — your e-mail address, a signed session cookie, the plan, the period's included and used counts, the top-up balance and the one-sided count — processed to perform the contract with you (GDPR Art. 6(1)(b)). For the contents of the desk bundle — which, since 16 September 2026, the desk writes to the account by itself after every change while you are signed in, and reads back on every browser you sign into; the five versions before the latest write are kept alongside it — the operator remains controller and Protosonic is processor. It is stored as sent and read by nobody; it is not encrypted on your device before it leaves, and this page says so rather than implying otherwise. The journal. Since 16 September 2026 a stamp made from a signed-in browser, or through an API key, is also kept under the account: the sealed envelope (the SHA-256 of the file, a beacon round and the timestamp authorities' tokens over that digest), the purpose it was sealed under, the page it came from, and a name you may type — by default the file's name. Never the file, and never a place, with one exception: a stamp made through an API key that names a saved company also keeps, in its row, that company's names, numbers and chosen address — a place — and the product and lot the call sent (see Saved companies above). Stamps made on the farmer's page, or while signed out, are not journaled. Each entry can be renamed, downloaded or deleted from the account page. The page reports whether the requested change is confirmed or remains pending. Limited records may remain to prevent deleted material from reappearing after recovery; removing one entry does not itself confirm full account or backup erasure. The nightly anchor. Every night a hash of every journal entry (its id, content id, digest, sealing time and a hash of its envelope — never its name, never the account) is folded into one root across all accounts and that root is stamped and published at /api/anchors; the published anchor carries the root, a count, a beacon round and the authorities' tokens, and nothing that identifies an account or an entry. A deleted entry's hash remains in past anchors, which is what makes the anchor a proof of existence at a time. A published journey (/u.html?p=…) is what an operator chose to make public about one product from the desk: the sealed records ticked, their stamps, and what those records declare — a place, a time, a species. It carries no account and no person's name unless the operator wrote one into a record; on a Studio or higher plan it may also carry a brand kit the operator typed on the desk — a brand name, a colour, a tagline and a logo image of up to 32 KB — stored with the pack and served publicly with it until the operator clears it or withdraws the page; the link is a random token; hosted publication, brand changes and withdrawal controls are temporarily unavailable. When those controls are available, the operator can withdraw it from the desk and the page goes with it. Anyone who scans the code fetches that pack and checks it on their own phone; we log nothing about who scanned. Managed renewal, on for paid plans unless switched off, appends a fresh timestamp token to an entry's renewal chain before its authority's key lapses; it reads the content id and the chain, never the file. Mail from us is off unless you switch it on there: a plain-text receipt when a stamp is recorded (its name, fingerprint, content id and beacon round — never the file, never a token) and a statement on the first of each month (last month's stamps by kind, the plan, the balance), both to the address on the account, through the same provider as the sign-in link, with no tracking. One notice is on unless you switch it off there: a warning when the account's qualified stamps or vault space run low (counts only), sent once each time it happens. Switch either off on the account page at any time. Storage is the EU-jurisdiction object store named in §9; the sign-in e-mail goes through an e-mail provider if one is configured, and we will name it here on the day a deployment configures one. Without its configuration the account function answers 503 and does nothing. Retention: until the account is closed; the desk bundle and its kept versions are deleted when you delete them from the account page or close the account. Closing is requested on the account page. Retirement and deletion of the journal, desk versions, saved companies, API-key access and account record can remain pending while storage and recovery checks are incomplete. The checked result is shown on the account page; a request does not confirm erasure of every retained backup copy. Two things remain: Stripe's record of what you paid — invoices are kept by Stripe and by us for the period Estonian accounting law requires, which is seven years — and a marker under the hash of your e-mail address saying that an account with it was closed, kept so the same address does not receive a second trial; it holds a date and nothing else.
The payment — Stripe is our processor, and it holds the customer record. Card details and Revolut Pay are entered on Stripe's own hosted checkout and billing portal, not on this site: we never see, receive or store a card number or Revolut credentials, and no payment page is served from here. Revolut Pay is a method on Stripe's pages; we are not a Revolut merchant and we have no separate Revolut account. Stripe Payments Europe, Ltd. (Ireland) acts as our payment processor and, for its own regulatory duties, as an independent controller. The data involved is your e-mail address, billing name and address, VAT identification number if you give one, and the status of your payments and subscription — that is all; we do not receive anything about the card itself beyond its brand and last four digits as Stripe displays them to you, and we do not receive Revolut account details. If you pay with Revolut Pay, Stripe shares what that method needs with Revolut under Stripe's own arrangements. Purpose: to take payment and to meet our tax obligations (GDPR Art. 6(1)(b) and 6(1)(c)); VAT determination is performed by Stripe Tax. Retention: Stripe keeps the customer record under its own policy; we keep what accounting and tax law requires us to keep, which in Estonia is seven years for the underlying documents.
The API key — we store a hash, never the key. A key is generated in your account and shown to you once. What is stored on the account record is a SHA-256 hash of it, with the label you chose, the time it was made and the time it was last used. We cannot show you the key again and we cannot recover it, because we do not have it; that is the point. Revoking a key marks the hash revoked. Retention: until you revoke it or close the account.
The vault — ciphertext, a salt and a check value; never a key, never a file. If you keep a stamped file in the vault, it is encrypted on your device (AES-GCM under a key derived on your device from your passphrase) before it is sent; what we store under your account is that ciphertext, the file's SHA-256 (which the stamp already commits), the name and size you gave it, the date it was stored, the retention date five years on, and whether you set a legal hold. We also store the salt the key derivation uses and a check value that lets your browser tell a right passphrase from a wrong one; neither yields the key. We cannot read a vaulted file or recover a forgotten passphrase. File deletion and account closure may remain pending while recovery and storage checks are incomplete. The account page reports the checked result; requesting deletion does not itself confirm erasure of stored material or backup copies. The vault's hold flag blocks ordinary file deletion until it is lifted; it is not immutable provider storage or a complete legal-hold policy.
The meter — counts, and nothing else. To bill for qualified stamps we keep, on your account record, numbers: how many qualified stamps the current period included, how many were drawn, how many top-up stamps remain, how many stamps went out one-sided, and when the period rolls. The meter never receives a record, a file, a fingerprint, a plot, a species, a supplier or a customer of yours. The relay it protects is the same pipe described in section 7: a digest with a fresh nonce passes through it and nothing is retained. Counting how many times you stamped tells us nothing about what you stamped, and that separation is deliberate.
7. The tools that keep your files on your device
Optional inspection read link (not available yet). When enabled, choosing a read link uploads an inspection pack encrypted on your device. The decryption key stays in the link fragment and is not sent to our server. We hold the encrypted copy, its account association, size and expiry for the selected 1–30 days in the EU evidence store. Reads end at expiry; an hourly cleanup removes expired copies. Withdrawal and account closure also remove the held copy. A recipient who already downloaded it may keep that copy. Cleanup or closure remains pending when storage cannot confirm it; requesting deletion does not confirm erasure of backup copies.
Local evidence-pack handover. Choosing Continue to review or Edit a copy stores an unencrypted temporary copy of the pack, including its original attachments, in this browser's IndexedDB. No pack bytes are uploaded and the link contains only a random local reference. The destination removes the stored copy when opened. A handover stops opening after two minutes; abandoned copies are removed on the next handover-storage operation, or when you clear this site's browser data, not by a background timer. Download the pack and any review receipt to keep them. Optional stamping similarly passes the downloaded pack to the stamp tool on this device; only its fingerprint is sent to timestamp authorities when stamping.
- Browser stamp tool: file hashing and sealing run locally; we never receive your file. At stamp time the browser fetches the current public randomness round from the drand beacon operators (api.drand.sh, drand.cloudflare.com — no file data is sent) and, to close the time bracket, sends the file's SHA-256 digest (not the file) with a fresh nonce through our same-origin
/tsa/*relay to two RFC 3161 timestamp authorities: freetsa.org and DigiCert (timestamp.digicert.com). The relay is a pipe — we do not retain the digest — and the TSA receives a digest it cannot reverse into your file. Verification sends nothing anywhere: it runs offline on your device. - Plot or source declaration (try.html): if you allow it, the browser reads device GNSS in order to declare a point or polygon. An applicable micro or small primary operator may instead type a postal address or reference from an applicable official system for the simplified route. These details stay on your device unless you download an export or stamp the declaration (in which case only the SHA-256 of that JSON is relayed to timestamp authorities, same as any other file). Phone GNSS and eligibility for the simplified route are operator-declared fields; the stamp does not prove either claim. We do not receive a live location stream.
- Map tiles (opt-in): the chain map on try.html draws declared plots over a public-domain Natural Earth outline served from this site, so viewing it contacts nobody else. If you switch on Show OpenStreetMap tiles in the map legend, or press the map's own “show the map” button, your browser fetches map images directly from the OpenStreetMap Foundation (tile.openstreetmap.org), which then sees your IP address, which map areas you view and this site's origin (its scheme and hostname). Map-image requests send only that origin as their referrer, never the page path, buyer-link query or fragment. None of your files or plot records is uploaded to the map service. The switch is off on a new browser session and remembered only for the current session.
- Place search (you type it): the plot map's search box sends the words you type to our same-origin
/api/geocode. That function asks the OpenStreetMap Nominatim service (nominatim.openstreetmap.org) with a contactable User-Agent. Nominatim sees the query text and this server's address, not your plot, your corners or your files. Nothing is searched until you press Go. A result is a suggested map centre, not a location proof. - Screen with Whisp (you press it, after agreeing once): on the desk, Screen with Whisp sends the outline of the plots you chose — their coordinates, and a running number so the answer can be matched back, nothing else: no plot name, producer, file, account or e-mail — to our same-origin
/api/whisp. That function forwards it to Whisp, the free deforestation-risk service of the Food and Agriculture Organization of the United Nations (FAO), at whisp.openforis.org, with OpenStamps' Whisp key or, if you saved one under Account → Settings, your own. Whisp sees the outline and this server's address, never your browser. Whisp's terms say FAO does not store or retain the outlines it is sent. Its answer — a risk assessment per commodity type against global maps, not a certification — comes back to your desk, which keeps it as evidence on that product and stamps it (only its SHA-256 goes to the timestamp authorities). Nothing is sent until you have agreed to the dialog that says this, on that browser, and pressed the button. If you switch on automatic screening (under Your company on the desk, only where this deployment offers it; off unless you switch it on), the outline of each plot a farmer sends you is sent to Whisp when it arrives, without a further press; the farmer never sees Whisp's answer. Your own Whisp key stays in that browser's storage; it travels with each screening to/api/whisp, which passes it to Whisp for that request and never stores, logs or shows it. We keep a count of plots screened per account per day and per month (for the fair-use allowance), under the account's hash — never the outline, the answer or a key. Why this exists: the EUDR asks an operator to assess the risk of deforestation; the stamp lets you show what Whisp said, and when, even after its datasets change. - Satellite pictures on the desk (you press it; only where this deployment has switched it on; since 27 September 2026): under Your products, Satellite pictures, 2020 and now sends one plot's box — the west, south, east and north edges of its outline, four numbers rounded to about a metre — and which of the two pictures is wanted, to our same-origin
/api/sentinel. Nothing else goes with it: not the outline, the plot's name, the producer, the product or a file. Signed out, nothing goes further than our own function: the page holds the box back when it knows you are signed out, and the function refuses a request without a session before it does anything else. That function asks Earth Search, the free public catalogue run by Element 84, Inc. (United States), which Sentinel-2 scenes cover a square of about 5 km around the box — never the box itself — and then reads small parts of those scenes (each file's header and the one to four internal tiles, squares of about 10 km, that hold the plot) from the Copernicus Sentinel-2 archive Element 84 keeps on Amazon Web Services (United States; the AWS Registry of Open Data). Both see this server's address, never your browser. Two pictures come back to your page — the clearest day near the EUDR cut-off of 31 December 2020 and the latest clear day — each with its date and cloud cover, and the outline is drawn over them on your device. They are satellite pictures, not a finding: they do not show whether land was deforested, they are not stamped, and they are not put into the product or the desk copy under your account. A public journey includes selected snapshots only if you explicitly choose that option when publishing; that separate copy has the retention described below. When the desk holds a plot with an outline, the page asks/api/sentinel/statusonce whether the feature is switched on; that request carries nothing. We keep a count of pictures made per account per day and for the whole service (for the fair-use allowance), under the account's hash — never a box — and each picture made, filed under a keyed hash of its box (not the box, not the account) in the EU store (§9), for 30 days (pictures near 2020) or 2 days (the latest), so a second look does not fetch it again; an hourly cleanup deletes pictures due to expire before its next run, even if nobody requests another picture and even while the feature is switched off. Pictures may therefore disappear up to an hour early. Failed cleanup runs are reported as errors and retried at the next scheduled run; an outage can delay deletion. Expired pictures are never served, and the cache is not in the nightly backup. The pictures are Copernicus Sentinel data, free, full and open under EU law, and are marked "Contains modified Copernicus Sentinel data". - Species names and GeoIDs on the desk (since 26 September 2026): the species-name helper suggests names from a list that ships with the page, and a plot's GeoID is computed on your device from its outline — neither sends anything. Only if a species name is not in that list and you press Ask GBIF about this name does that one scientific name go, through our same-origin
/api/species, to GBIF (the Global Biodiversity Information Facility, an international network) for a name match; no account, plot or product goes with it, and we keep nothing. A live CITES check through Species+ (UNEP-WCMC) works the same way when this deployment switches it on; until then it is off. - Plant-photo suggestions (you press it, after agreeing once; only where this deployment has switched it on): on the farmer's plot page, once a photo is added, What is growing here? sends that one photo — redrawn on the phone first so it carries no camera data (no EXIF, no GPS position, no camera or time), at most 1280 pixels — and the plant part you picked, to our same-origin
/api/plantnet. That function refuses any photo still carrying camera data and forwards the rest to Pl@ntNet, the plant-identification service of French public research institutes (CIRAD, INRAE, Inria, IRD), with OpenStamps' key. Pl@ntNet sees the photo and this server's address, never your phone, the plot outline, a name, the request link or an account. Pl@ntNet states that it keeps the photo only in memory while identifying it and does not store it, and records the date and time of each query; it processes images temporarily transmitted, IP addresses and logs as an independent controller, on its legitimate interest, to run and secure the service, for statistics, to improve it and to contribute to scientific research, for no longer than necessary (its data protection officer: dpo@cirad.fr). Up to three suggested names come back and are shown as possible matches — a suggestion, not an identification; they are not stamped, not kept, and never change the tree you choose. The photo on your phone, and the code of it that is stamped, are unchanged. Nothing is sent until you have read the notice once on that phone and pressed the button. Once a photo is added, the page asks/api/plantnet/statusonce whether to offer the button, carrying the request link's token when there is one — nothing you made. We keep counts only (per account or request link, per hashed network address, and for the whole service, per day), never the photo or the answer. - Identity check (optional; you press it, after ticking a consent box; only where this deployment has switched it on): under Account → Settings, an account holder may have Didit, an identity-verification company, check an identity document and a short selfie video on Didit's own pages: it reads the document, checks that the selfie is a live person and compares the face with the document's photo. Those images are biometric and identity data; Didit processes them as our processor, under its verification privacy notice, and by its own documentation in the EU by default. Our function tells Didit only which check to run, an opaque tag for the account (never your e-mail or name) and where to send you back. We keep under the account: the result (approved, declined, in review, expired or abandoned), its date and time, Didit's session number, which checks ran, the issuing country and document type if Didit returns them, whether it was a test, when you ticked the consent box, a SHA-256 fingerprint of Didit's decision so it can be stamped later, and when Didit deleted its copy — never an image, face data, a document number, a date of birth, a name or an address. Didit's copy is deleted as soon as we receive the result: once Didit has decided, our function asks Didit to delete the session, its images and its decision, and asks again if Didit does not answer. The legal basis is your explicit consent (GDPR Art. 9(2)(a)), which you withdraw by pressing Remove my identity check: that deletes our record and asks Didit to delete the session and its images. Closing the account does the same. The result says only that a document was read and a live face matched it, once, at Didit; it says nothing about who made, approved or is responsible for any record.
- Phone Sync (acoustic path): the rendezvous mailbox at
/api/copresencebriefly holds, per pairing session, four sample-clock integers and two confidence numbers from each device, keyed by a one-way hash of a secret that never reaches the server. It cannot derive a location or a distance from them; entries expire within 10 minutes. The screen-to-camera path uses no server at all. - GeoLibre plugin (opt-in, inside GeoLibre): the OpenStamps plugin for the GeoLibre GIS (installed by you from
/geolibre/plugin.json) runs in GeoLibre, not on this site. Only when you paste a journey link, press "Illustrative unit", or answer "Open and check it" when a saved project or a link names a journey (it asks first and reads nothing until you do) does it read that published journey from/api/publish/<token>or the public sample chain here — the same public reads the journey page makes, seen by our host as any page view is (§9). Checking the stamps is the engine inside the plugin and reaches nothing. What you draw stays in GeoLibre; a project you save keeps the journey link and the declared positions, never a check result. - The security and buying pack: architecture, data flow, sub-processors, retention, service limits and the honest questionnaire answers (no SOC 2, no ISO, no insurance, no SLA) are on one page, kept in step with this one.
- Coverage map (opt-in, per published journey): new hosted publishing and coverage changes are temporarily unavailable. When those controls are available and you publish a product's journey from the desk you may tick also put this journey's plots on the coverage map. Then
/api/coverageand Calibration is the public record of how our own forecasts compared with what happened; it names nobody and withholds any cell small enough to identify somebody. /coverage.html list that journey as the industry, the country a plot named, the day it was published and up to eight positions rounded to 0.01° (about a kilometre), linking to the public page — no name, no account, no polygon. The page is public whether or not you tick; the map only aggregates journeys whose publisher said yes, the tick can be undone from the desk when account changes are available, and withdrawing the page removes the dot. Ask the supplier whose plot it is before ticking.
8. Enquiries and e-mail
Evidence tools and team enquiries: the free pack builder and recipient review tool process selected files in this browser. Importing a pack or receipt does not upload it. Partner-interest enquiries include your name, reply email, organisation and message, with permission to receive and reply to that enquiry. They use the CRM and enquiry mailbox described below only after you press Send. They do not include source documents and do not opt you into marketing.
Plan finder and proforma (pricing, enterprise and home pages): the plan finder works in this browser tab. Your turnover declaration, answers and the optional company, contact and message details you type for a proforma are not sent to us and are not stored on a server. They appear only on the proforma file you choose to download or print, and your contact and company details are cleared when you close the finder. If you tick “Keep my planning answers”, your planning answers (never your contact details) are kept in this tab’s session storage until you clear them or close the tab. Emailing the proforma is not switched on.
Partner programme (in preparation; OFF): the prepared programme links assigned referral codes to a partner account and its creation date, partner kind, terms version, acceptance time and an approval receipt reference. A signed-in partner can read only its own assigned codes when that service is enabled. The enquiry form assigns no code and accepts no contract. Client source attribution requires the separate source-measurement choice in §11; a referral link alone creates no fee or payout. Written agreements, accounting records and their retention are separate from optional source measurement.
Optional API interest requests: this form is switched off in this release. When enabled, you choose one API and give separate consent. We keep your email, selected API, consent wording/version and request time in our account ledger and send a confirmation email through Resend, our email delivery provider. The link expires after 24 hours; opening it does not confirm anything until you press the button. Only confirmed interest is sent to the CRM described below. No newsletter subscription is created and no copy goes to the operational alert mailbox. The email includes a withdrawal link; you can also write to pilot@openstamps.com. Withdrawal immediately stops contact permission in the ledger and clears its live email field. The page separately reports whether CRM cleanup is complete or needs attention. Pending requests expire after 24 hours; confirmed requests expire after 730 days without a fresh reviewed arrangement. Maintenance removes expired live contact details. Minimal suppression records and backup retention are separate; withdrawal is not a claim that every backup copy has already been erased. A request does not reserve a service or promise a launch date.
Enquiry / e-mail: whatever you choose to write to us — typically your name, your work e-mail address and the question you are asking. The Ask panel and the enterprise quiz last step are the same door: a same-origin POST to /api/crm, which creates a Lead in a CRM we operate ourselves, hosted for us in Germany. Plots, stamps, desk bundles and Information System credentials are never sent that way. An e-mail link uses your own mail client. Purpose: answering you (legitimate interests, and steps prior to a contract where you are asking about buying: GDPR Art. 6(1)(f) and 6(1)(b)). Protosonic is the controller. The first-party Ask panel answers locally on your device and sets no cookie. Nothing on this site asks you for a turnover figure as an input to a price. Retention: up to 24 months after last contact, unless a contract or tax law requires longer.
9. Hosting logs and abuse limits
Our static host may process IP address and user-agent transiently to deliver pages. To enforce the per-network anti-abuse limits we store a hashed daily counter (not the IP itself) for timestamp-relay, sign-in, hand-off, Phone Sync and Ask-panel messages. These per-network counters are not the meter: the meter (section 6) counts stamps against an account, this counts requests against a hashed network, and neither holds anything you stamped. Purpose: prevent infrastructure abuse (GDPR Art. 6(1)(f)). Counters expire with the UTC day. Protosonic is the controller.
The security log (since 25 September 2026). To notice account takeover, abuse and billing faults, the site records security events: sign-in succeeded or failed, too many code attempts, an API key created or revoked, a billing notice that did not match, an account closed, a team change, a refused desk key, and a paid timestamp refunded. Each row holds the event, the time, a short tag for the account (the first 16 characters of the SHA-256 of its e-mail address, not the address) and the same salted network hash the abuse counters use, never an IP address, e-mail address, code, key or token. It is kept one record per UTC day, at most 200 rows a day, and deleted after 90 days. Only the site's owner can read it. Purpose: security of the service (GDPR Art. 6(1)(f)). Protosonic is the controller.
The owner's admin log (since 26 September 2026). When the site's owner helps a customer — adds or removes qualified stamps, gives a complimentary plan, writes a note, records a stamp grant, or runs or tests a backup — the action is recorded with its time, the reason typed, and the account named only by a short tag (the first 16 characters of the SHA-256 of its address), never the address. The last 500 actions are kept; the owner alone reads them. Legal basis: our legitimate interest in accountable administration and in answering a customer's question about their own account.
Backups (since 26 September 2026). Every night at 03:30 UTC a copy of the stored data — accounts, journals, desk bundles, vault ciphertext, hand-off mailboxes and the logs above — is encrypted with a key only Protosonic holds, kept in the same EU jurisdiction, read back and compared, and kept for the configured retention period (14 days by default, at most 35) before it is deleted. A backup exists only to restore the service after a loss; it is never read for any other purpose. A closure request does not erase an existing archive immediately; its older copy expires under that configured retention period. The vault's files are already encrypted on your device, so the backup holds ciphertext it cannot open. Legal basis: our legitimate interest, and the duty to secure the data (GDPR Art. 32).
Where the material is held, by class. Two classes of data live on the store, and /api/residency prints — for this deployment, at any moment — where each is: the evidence (the journal's envelopes, the vault's ciphertext, the nightly anchors, published journeys, the desk bundles and their versions, the hand-off mailbox and the ten-minute co-presence mailbox) and the ledger (the account record with its balance, e-mail address and key hashes, and the abuse counters). Since 16 September 2026 both classes are held in an object store with European Union jurisdiction — Cloudflare R2, bucket restricted to the EU at creation, which Cloudflare documents as storing the data only in EU locations. Cloudflare, Inc. is our sub-processor for those bytes; Netlify runs the functions that read and write them and holds no copy — the Netlify Blobs stores used before that date were emptied on the same day. /api/residency names the class of place (provider, jurisdiction), never an endpoint or a bucket; the account page prints the same sentence under the vault. Netlify's functions, CDN and request logs remain where Netlify runs them (section 9, first paragraph); residency here is about where the stored material rests. Nothing moves by itself: a change of store is a deliberate, logged act by the operator, printed on /api/residency the moment it is made.
10. Blockchain hygiene
Procurement and privacy officers ask "is this a blockchain, and what goes on it". The answer, once: no blockchain is needed to check a stamp — a stamp is checked offline from its own bytes, a public randomness round and timestamp-authority tokens. Where a public append-only log is used, now or later, what is registered is a 32-byte identifier, never a record, as one more independent clock beside the others. There is no token, no per-stamp transaction, no data on any chain, and no chain per company. A chain is one witness among several and is never load-bearing on its own. OpenStamps has run its Bitcoin anchor since 26 September 2026; it commits one batch fingerprint, never a record.
The hourly Bitcoin anchor. Every hour, at half past, a server job sends one fingerprint — a single SHA-256 hash computed over the stamps of that hour, with no customer data, no file, no name and no account in it — to the OpenTimestamps public calendars (the aggregators a.pool.opentimestamps.org, b.pool.opentimestamps.org, a.pool.eternitywall.com and ots.btc.catallaxy.com, which pass it to the calendars alice.btc.calendar.opentimestamps.org, bob.btc.calendar.opentimestamps.org, finney.calendar.eternitywall.com and btc.calendar.catallaxy.com). Every two hours for two weeks it asks those calendars whether that fingerprint has reached a Bitcoin block, and when one has, it fetches that block's 80-byte header from two public block explorers, blockstream.info (Blockstream) and api.bitaps.com (Bitaps), and keeps it only if the two agree. A backup, when it is switched on: if the calendars refused every hourly fingerprint for twelve hours, or one fingerprint has waited more than a day for a Bitcoin block, then at most once a day (at 23:50 Estonian time) the job writes the newest fingerprint into one Bitcoin transaction of our own, paid from a small wallet only this job uses; it reads the fee and that wallet's coins from mempool.space and blockstream.info and sends them the transaction. What it carries is the same 32-byte fingerprint, nothing else. Such an anchor shows that the fingerprint existed before the block and nothing more, and it is our own statement, not a third party's. None of these services receives anything about you or your files from this job, and checking a stamp's Bitcoin proof happens on your device. One exception you control: the OpenTimestamps helper page (ots.html) contacts the four calendars only when you press "Ask the calendars now" (each receives the pending commitment your own .ots already names, derived from your file's hash, never the file), and the two block explorers only when you press "Fetch the block header" (each receives a block height). Your file is hashed on your device and never leaves it. The Bitcoin anchor is switched on for the public OpenStamps service. A separate deployment can disable it. Stamps that never reach an account's journal (the field page, a plot drawn on the tools page, and any stamp made there while signed out) join that batch only this way: after the seal, the page sends our own server the stamp's content id — one SHA-256 hash of the stamp's 152-byte core, and nothing else: never the file, its name, the record, the photo, or the core itself (which can hold the plot's coordinates) — to /api/chain/submit, and later asks /api/chain/proof/ with the same id for the Bitcoin proof, which your device completes from the stamp it holds. We keep that id beside the hourly batch it joined, as we keep every leaf of a batch; your network is counted only in the hashed daily counter described above, as for the relay. On a deployment where the anchor is disabled, both answer "off" and nothing is kept.
Lifecycle emails (in preparation; OFF). No lifecycle messages are enabled in this release. The prepared policy sends new accounts a welcome email and, if no record is found in the account, an account-help email from four hours after sign-up. Neither requires a marketing tick. These two service messages contain no price, plan or commercial offer. Product news and offers are separate: their sign-up box starts unticked, and you can change that choice in Account settings. Earlier accounts and email choices are not automatically enrolled under this new policy. Replies to these prepared messages go to our confirmed pilot@openstamps.com mailbox. The sign-up screen states the planned welcome and one sample-file reminder; it does not promise delivery while these controls are off. Every lifecycle email has a stop link; stopping the list stops later account-help and offer messages together. It does not cancel sign-in codes, security messages, billing notices or evidence receipts you separately request.
The prepared list uses your account email, account-creation reference, offers choice wording/version and time, opaque stop capability, due-time work records, fixed message reservations and provider acknowledgements. There are no tracking pixels or personal click links. Separate stop and work records hold account references rather than the email or message body; these references are still personal data. A stop link works without signing in, but opening or previewing it changes nothing. Account settings can stop retained lifecycle email while new collection is switched off or an account write is interrupted. A confirmed stop cannot be reopened through these controls. Necessary hosting logs may contain the opaque mail-client capability URL; manual browser links put it in a fragment which the control removes from browser history. A provider acknowledgement is not evidence of delivery or opening.
The prepared retention rule removes stored message bodies, recipients, headers and provider IDs 30 days after reservation or issuance (whichever is later), retaining a minimal occupied slot to prevent resending. The schedules remain bounded, OFF pilots; this is not yet an active deletion policy or proof of capacity for large account populations. A separate account button can remove current lifecycle choices and attempt data and block new lifecycle email without closing your account. Already submitted email may still arrive. This does not erase account email, financial records, minimal creation, work, suppression or denial records, backups or copies held by the mail provider. Restore omits archived lifecycle permission and work records and enforces recovery denials before restoring accounts. Scheduled retention, whole-account erasure, backup/provider retention, native storage and queue throughput, and the delivered email's unsubscribe headers must be qualified before activation.
11. Cookies and analytics
Plot-file intake and repair (in preparation; OFF). Files are read on your device. Repair keeps the original unchanged and creates a separate corrected file and a list of changes, with separate stamps if you request them. Optional saved mappings keep column names, their matching choices and a header fingerprint in this browser, never the cell values or file bytes. Column names themselves may identify people; review them before choosing to remember a mapping, especially on a shared device. Both intake panels offer a button to forget these saved mappings. Clearing a selected file does not remove a saved mapping, and signing out does not clear this browser storage. If removal cannot be confirmed, use your browser’s site-data controls. Downloaded copies and any evidence you separately submit have their own retention rules.
Account feedback (in preparation; OFF). The planned sign-up question asks what you need first, with an optional plain-text answer of at most 200 characters. An optional smallholder-supplier checkbox and broad region help us understand demand; they do not promise a service. Separately, you can request one email when TRACES filing becomes available, without a promised date. A demo-interest button explains that we do not run calls or demos and links to the self-serve trial. Optional checkout-return feedback records one answer for an unpaid checkout session whose current status we can read. These answers are separate from permission to measure your visits or send product offers. They are not collected in the current release.
Planned feedback storage and removal. Account feedback would be held with your account and counted in private weekly reports. Free text, email addresses and checkout identifiers are excluded from those reports. The draft policy keeps detailed sign-up, demo and checkout feedback for 90 days; after that, only a minimal sign-up-completion marker remains. A requested TRACES email is retained separately until sent, withdrawn or erased; it is not a marketing subscription. Signed-out email requests are not yet available. A separate necessary abuse counter holds a UTC date and the number of feedback changes, capped at twenty per account per day; removing optional feedback does not reset it. It expires two days after that date starts. Hourly expiry and signed-in withdrawal and erasure controls are prepared locally and remain off with collection. Account-write coordination and the complete registration flow must be qualified before activation. Existing encrypted backups have their separate retention period (default fourteen days, maximum thirty-five), so removing live feedback does not immediately erase an older archive. Restore omits archived feedback, notification requests and counters, and blocks new collection until recovery is reconciled.
Required account setup question (in preparation; OFF). When this registration flow is enabled, new accounts created from the release cutoff answer one fixed first-need question. The optional extra text, smallholder checkbox and region remain optional. We retain a minimal account-bound completion marker while the account exists so removing feedback does not force another answer at the next sign-in. That marker contains no answer or demographic detail and grants no email or measurement permission. The feedback detail keeps its separate 90-day policy and removal controls. Existing accounts are not asked retrospectively. Unknown or restored state remains subject to recovery denial; archived feedback is not restored as a choice. The complete flow, lawful basis, proportionality and native-app continuation must be qualified before activation.
One-time TRACES-ready email request (in preparation; OFF). The separate signed-out form asks for an unticked choice to keep your email, send a confirmation and email you once when filing is ready. It promises no date and is not a newsletter. Only your explicit confirmation activates that request; previews do not confirm anything. Unconfirmed requests expire after 24 hours. Removal clears the live email and retains a minimal suppression record to prevent the same request being contacted again; the full suppression and confirmed-contact retention policy still needs acceptance before launch. Necessary abuse limits use native request network information to derive daily keyed fingerprints, with ten requests per network and a thousand per service per UTC day. Fingerprints are pseudonymous, not anonymous, and no raw network address is stored in those counter records. Prepared cleanup replaces known day records with a date-only barrier after two UTC days from that day’s start, even with collection off. Unknown and legacy rows are retained for reconciliation. Encrypted backup retention is separate; restore omits both old and new optional notification counters and blocks collection pending recovery. No public backend or cleanup schedule is selected yet; these preparations do not establish live delivery or full erasure.
Checkout-return question (in preparation; OFF). After you start a checkout, the prepared path can keep up to eight recent provider session references under your account for 24 hours, subject to the selected cleanup running successfully. Before redirecting, this tab can hold an encrypted return capability in sessionStorage; it carries no permission to change your checkout and is never placed in a URL. On return to pricing or the cart, the control removes that tab value and uses a read-only Stripe request to check the session is still open and unpaid. The capability stops opening after two hours. An optional answer uses the separate 90-day feedback policy above. This does not prove you cancelled or that payment cannot complete later. The selected cleanup retires expired or closed-account receipt payloads independently of new collection; unknown rows and failed cleanup need reconciliation. Restore omits these receipts. Nothing in this question cancels a subscription, refunds a payment or adds email consent.
Signed-out demo interest (in preparation; OFF). This separate flow is not publicly selected. Its proposed notice asks you to keep a declared email and the pricing or plan page for fourteen days to count interest; no email ownership is established and it grants no permission to contact you. It says plainly: we do not run calls or demos, and the product is free to try. The prepared storage limits are ten new requests per native network and one thousand per UTC day. The prepared form saves a random removal key and local status in this tab before submitting; it saves no email or page in that tab record. The key is sent in a request body, never in a URL. A saved local status does not establish a fresh server acknowledgement. There is no automatic retry. The tab key can remain after the fourteen-day request period until the tab closes or its storage is cleared, so you can still try withdrawal. Closing the tab or losing storage may lose that removal control; the privacy contact remains available. Removal clears the live email and page without sign-in and with collection off. A separately selected hourly expiry job is prepared locally and remains OFF. It minimises expired requests and later replaces a whole day with a date-only barrier, preventing delayed creation from restoring its contents. Each invocation has a bounded inventory and mutation batch; incomplete work is reported for reconciliation. The prepared private owner view counts retained states by the original request week, separately from account feedback; it does not establish unique people, email ownership, demand before records were retained or complete event history. Network digests and removal bindings are pseudonymous while retained. Unknown rows or failed sweeps remain pending reconciliation; this is not a guarantee of physical deletion at an exact time. Existing encrypted backups have their separate retention period. Restore omits demo payloads and their purpose-key pin and blocks new collection pending recovery. No public form, backend provisioning or scheduled cleanup is enabled by this draft policy.
Optional source measurement (in preparation; OFF). We are preparing a separate, initially unticked choice to measure how people find OpenStamps and reach their first sealed record, due-diligence file and payment. No source collector or account attribution is active in this release. The intended fields are registered source, campaign and referral codes and a public landing route, never a whole URL, arbitrary query text, a browser referrer or a screen recording. When separately enabled and accepted, the first-file counter checks the structure of your saved desk copy for a product record and its server save time. It copies no product name, supplier detail, plot, document or product identifier into analytics. A saved file is not a submitted DDS or a finding of compliance; offline-only files are outside this count. This choice is separate from the usage-sharing pilot below and from product news and offers; accepting one does not accept another. Declining leaves the tools, sign-in and checkout available. Anonymous counting uses a random tab-only session and erasure capability, sent without account cookies to our same-origin endpoint; Protosonic is the controller and the configured hosting/storage providers process it. It counts separately chosen sessions, not unique people or all visitors, with a current bound of 100 identities per UTC day. Source and milestone fields are excluded from reports within 90 days. Stop source measurement on the landing or in account settings stops collection locally immediately; server removal is confirmed separately and may need a retry if offline. Withdrawal retains only a minimal denial until expiry, preventing delayed submissions from reopening the same session. The tab holds its recovery capability; losing the tab loses that anonymous handle. At expiry, the day barrier holds only its date, with no session, erasure hash or source. Existing encrypted backups are retained separately (default fourteen days, maximum thirty-five); withdrawal does not immediately erase those archives. Our restore tools omit optional source rows and reset account choices under a collection denial. Expiry cleanup runs hourly when retention is enabled, independently of new collection. Paid-conversion integration and the complete release must be qualified before this feature is enabled. Necessary hosting request metadata is subject to the hosting policy; this is not an assertion of anonymous network transport. An optional fixed answer at sign-up is labeled self-reported and stays separate from registered landing groups. It creates no anonymous visit or partner commission. The chosen tab can attach it after sign-in; another device or tab may leave it unattached. Declining the answer does not affect sign-in. The necessary sign-in cookie is not measurement consent.
Optional source-control abuse counters (in preparation; OFF). Source choices and touches are limited to 20 changes per account per UTC day; withdrawal is not subject to that cap. A bounded date-only server record holds daily keyed account fingerprints and counts, with at most 1,000 accounts per day. It does not hold source text, email addresses or account identifiers. These fingerprints are pseudonymous, not anonymous. Hourly cleanup replaces known records with a date-only barrier once two UTC days have elapsed from that day's start, independently of new collection. Encrypted backup retention is separate; restore omits these optional counters. Unknown or older records are retained and reported for reconciliation rather than erased blindly. The current cap is infrastructure protection, not a financial or stamp meter.
Optional payment observations (in preparation; OFF). If you separately allow account source measurement, a limited report can connect the selected source with checked payment receipts. It retains hashed invoice/payment/receipt identities, euro amounts, payment time, checked fixed price adjustments and cumulative successful refund observations. It does not copy card details, customer email, invoice URLs, arbitrary provider metadata or message/document contents into this report. Received-funds entries made by the owner are identified as owner-declared; they are not independent bank attestations. Read-only Stripe catch-up checks only the currently bound customer and subscription and rechecks your current choice; unsupported or unfinished receipts remain unconfirmed. The report is partial, not an accounting balance or a complete revenue history. Account withdrawal, expiry and restore reset remove these optional receipt details under the same source-choice rules; necessary financial records have their separate retention duties. Scheduled catch-up keeps one conditional progress row with a numeric scan position and no account or provider identifier, separate from payment receipts. Hourly retention cleanup clears that cursor after 90 days without new progress, even when new collection is off. Our restore tools omit optional progress rows. Clearing live details does not erase existing encrypted backups immediately.
Optional usage sharing (currently OFF): when enabled, the report page and desk offer a separate choice to share named actions such as opening Collect, requesting an export or submitting a report, and the report route’s success/error result. We use these steps to find usability problems. We do not record screens, clicks across the whole page, typed content, documents, plot geometry, passwords or message bodies. The collector sends a random page-session identifier, an erasure secret, the consent version and fixed event names to our same-origin service; the secret is hashed in storage. The browser keeps the identity and choice in this tab’s session storage after opting in. No account identifier is included in the journey; hosting and abuse protection still process the network connection. These are pseudonymous records, not a promise of anonymity. The owner can see session counts and selected step sequences, not a video. Other pages and native mobile apps are outside this pilot.
You can stop and remove the current page’s shared journey using its visible control. Collection stops immediately; removal from live storage is confirmed separately and may need a retry if offline. A minimal withdrawal marker prevents late events from restoring that journey. Live data is excluded from reports after seven UTC calendar days and an hourly cleanup removes expired day records. The configured encrypted backup retention applies separately (default fourteen days, maximum thirty-five); withdrawing does not erase an existing backup immediately. Our updated restore tools omit optional usage journeys from recovered data, including journeys captured before a withdrawal. Closing the tab loses its recovery handle; unidentifiable past journeys expire under the retention rule. Protosonic is the controller for this optional, consent-based improvement work. Collection is capped at 100 page sessions per day and 48 steps per session; results do not represent every visitor.
This site has no advertising trackers. Optional usage sharing is prepared but switched off in this release. It requires your separate opt-in before collecting selected steps; declining does not affect the tools. The account session cookie is strictly necessary, carries no tracking, and is set only after you sign in. The Ask panel sets no cookie. Stripe sets its own cookies on Stripe’s hosted checkout and billing portal, on Stripe’s pages and under Stripe’s policy; none of them is set on this site. If you choose Revolut Pay, Stripe may send you on to Revolut’s pages, where Revolut sets its own cookies under Revolut’s policy; none of them is set on this site either.
12. Recipients and transfers
Enquiry submissions become a Lead in the CRM we operate, hosted for us by an EU provider in Germany, and a problem or security report sent from report.html becomes a support case there (what you typed, the page, your browser type if you ticked the box, and your e-mail only if you gave one); the same-origin door that creates that Lead runs on Netlify. An e-mail link uses your own mail client. Hosting and e-mail providers act as processors or sub-processors. Stripe Payments Europe, Ltd. (Ireland) is our payment processor and holds the customer record; Stripe, Inc. (United States) is its sub-processor and Stripe's own transfer safeguards apply. The timestamp authorities — two free ones, and a qualified third where this deployment relays to one: Microsec zrt. (Hungary, EEA) — receive digests only; the drand operators receive nothing. FAO's Whisp service receives the outline of the plots you choose when you press Screen with Whisp on the desk; Whisp's terms say FAO does not store or retain the outlines it is sent (§7); it is a recipient in its own right, not our processor, and it is run by the Food and Agriculture Organization of the United Nations, an international organisation. Didit Identity Spain, S.L. (Spain), only where this deployment has switched the optional identity check on, is our processor for the account holders who start one (§7, Identity check). The operator's own alert mailbox receives operational mail about that leg (counts, an HTTP code, a slot name) carrying no personal data. We do not sell personal data. Transfers outside the EEA — Netlify, Inc. and DigiCert are in the United States — use appropriate safeguards (EU Standard Contractual Clauses); the digest sent to DigiCert is not personal data. The CRM is hosted in Germany. Nobody receives anything when a stamp is checked, because nothing leaves the device that checks it.
Element 84, Inc. (United States), which runs the Earth Search catalogue, receives a square of about 5 km around a plot's box, and Amazon Web Services (United States), which hosts the Sentinel-2 archive, receives requests for parts of the scenes that cover it, when a signed-in operator presses Satellite pictures on the desk where that feature is switched on (§7). Both receive them from our server, not the operator's browser, as recipients in their own right, not our processors, and nothing else about the plot, the product or the account reaches either.
Pl@ntNet (CIRAD, France, for the Pl@ntNet consortium) receives one photo, without camera data, when a farmer presses What is growing here? after agreeing to its notice; it is a recipient in its own right (an independent controller), not our processor, and is in the EEA.
13. Retention, in one place
- Farmer's phone: 90 days for sealed entries; an unsent entry is never pruned.
- Hand-off mailbox: 14 days by default (1–30 at the buyer's choice), applied on the next touch; no sweep job; closed at once by the buyer.
- Desk: on the device until exported or cleared by the operator; the signed-in copy under the account (the bundle and its five previous versions) until the operator deletes it or closes the account.
- Saved companies: under the account until the operator removes one from the desk or closes the account.
- Vault: the existing storage term and displayed retention date are five years from storage, including files funded by a prepaid vault term. This is a service period, not a universal statutory retention rule or an automatic expiry-deletion promise. Your applicable record policy may require a different period. The hold flag blocks ordinary file deletion; account closure or deletion may remain pending, and a request alone does not confirm erasure of stored or backup copies.
- Account: until closed.
- API keys: the hash, until you revoke it or close the account.
- Meter counts: on the account record while it is open; the previous period's counts are overwritten when the period rolls.
- Payments: Stripe's own retention for the customer record; ours is what accounting and tax law requires (seven years in Estonia for the underlying documents).
- Enquiries: up to 24 months after last contact.
- Abuse counters: the UTC day.
- Satellite pictures on the desk: the page view; the cached copy 30 days (pictures near 2020) or 2 days (the latest), filed by a keyed hash, never the box; the daily counts, the UTC day.
- Identity check (where switched on): our record until you remove it or close the account; Didit's copy until we receive the result, when we ask Didit to delete it (an unfinished check: until you remove it, close the account, or Didit's own retention ends it first).
- Security log: 90 days.
- Owner's admin log: the last 500 actions.
- Backups: configured retention, 14 days by default and at most 35. A closure request does not delete an existing archive immediately.
14. Your rights
Under the GDPR you may request access, rectification, erasure, restriction, portability, and objection. For surfaces where we are controller, contact pilot@openstamps.com. For a farmer's record or a mailbox deposit, the buyer is the controller and we will refer your request to it and assist it. You may complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) or to your own national authority.
15. Children
The Service is for business users. It is not directed at children.
16. Changes
We may update this policy; the date above will change.
Optional AI cards (not enabled yet)
When enabled, AI export prepares CSTP cards locally. The default omits original documents and separately held personal openings; a stamp may itself already carry place or identity-related values, so inspect the preview before sharing. Optional clear layers require a fresh disclosure acknowledgement for each export. Nothing is sent to an AI service automatically. Opening ChatGPT (OpenAI) or Claude (Anthropic) sends no card text; those services receive the material you choose to paste or upload under their own terms. Copying uses your device clipboard, which your operating system may synchronise. Closing the export clears its preview and choices, but cannot remove copies you have shared.
Optional photo-time declaration
The Sun comparison is switched off in this release. When enabled and explicitly selected, the plot record includes your declared photo time and place, its fingerprint, a predicted sky and any shadow measurements you enter. These declarations travel with the record when you send it to your buyer or share it. The observation stamp contains a salted commitment; its opening stays in this phone’s local queue with the photo and is removed under the queue’s existing retention and erasure controls. This feature does not upload photo pixels or infer a reliable capture time from camera metadata. Other photo-sharing buttons retain their existing, separate notices.
Optional satellite snapshots on a public journey
This feature is switched off. When enabled, publishing satellite snapshots requires a separate checkbox. It copies only the pictures and their dates into the public journey you choose to publish; consumers do not make satellite-service requests. Withdrawing the page removes the copy we serve. The satellite server cache still expires at 30 days, but a snapshot deliberately published in a journey stays until that page is withdrawn. Copies taken by others cannot be recalled.
Local rehearsal receipts
The optional every-step-sealed rehearsal runs entirely in your browser. It records check IDs and readings, but excludes names, documents and coordinates. It uses this browser’s signing key, makes no AI or timestamp-service request and submits nothing to TRACES. Receipts, salted openings and sample outputs remain in page memory until you download them or leave the page. Downloading shares nothing automatically; anyone you give the file can read its contents and check its chain. The collection progress ring also works locally and is not a calculated risk score.
Forecast board erasure
When the board is enabled, account links and salted openings are encrypted separately from the statistical rows, in Netlify Blobs (United States), with a separate key store. Closing an account destroys their per-row keys and deletes the linked forecast and outcome envelopes. Keys are excluded from the application backup set. The retained rows carry no original content ID, issuer, account, opening, event location or source link; they contribute only to aggregate statistics. This removes the links we hold. It cannot undo somebody else's previously downloaded copies or guarantee that outside information cannot identify a forecast. Account invoices and the anti-repeat-trial marker follow the separate account retention rules above.
Forecast source and VAT lookup
For an enabled board, the USGS FDSN event service receives the declared public-event region, magnitude threshold and time window. It receives no account name. When a business registers, the European Commission's VIES service receives its VAT number; returned names and addresses are discarded. VIES does not check company registry numbers. Public rows withhold account identity and salted openings; those openings remain private until erased or shared by their holder.
Optional text updates (prepared; currently disabled). The field-page pilot shows English wording and asks you to choose SMS or WhatsApp for one evidence request. A separately disabled renewal screen also asks for your international phone number and explicit agreement for that number and channel. Preparing its draft sends the number to OpenStamps transiently to bind an agreement code lasting at most ten minutes; preparation does not send a message or confirm consent. Opening a WhatsApp draft reaches WhatsApp's wa.me service with the request code and, in the renewal flow, the agreement code; SMS opens your device's messaging app. You must send the command and our signed inbound handler must receive it. Renewal requires a matching message sent from the number you entered. The messaging provider handles your number and message. OpenStamps' prepared consent, replay and STOP controls keep keyed references rather than the raw number or message body; those references are still personal data. No marketing permission is inferred. STOP blocks future messages through the prepared paid-request path. The initial pilot cannot restart updates after STOP; the separate renewal flow requires fresh agreement, and your messaging service may require its own restart step. The screens keep no persistent phone number or consent choices, and evidence submission remains available without text updates. Translations, actual phone/provider acceptance and retention/recovery acceptance are still required before enabling these paths.
The separately disabled message-cleanup path removes expired agreement codes and drops detailed data from expired consent records and phone-chat bindings. It keeps minimal keyed records needed to prevent old agreements or replies from being reused. STOP records and recovery locks remain in place. These retained references are still personal data; this cleanup is not full account erasure or removal of previously downloaded backups. Retention and recovery acceptance remain required before activation.
Optional world context
The world-context card is off by default. When enabled and you agree for that request, rounded coordinates (three decimals) and UTC dates are sent through this site to Open-Meteo for model weather/elevation, NASA FIRMS for satellite fire data, and USGS for earthquake listings. No selected file, stamp core or account identity goes to those sources. They receive our server request; our hosting and their services may retain request metadata. Open-Meteo reports service logs including requests and IP addresses retained for90 days; do not assume EU-only processing. Source credentials remain on the server. A bounded cache holds at most eight replies in function memory; entries can remain until eviction or the process ends, and are served only within their stated cache age. Account quota counters use the existing hashed account identifier. Exact replies are held in the tab; if you seal and save them, the selected product, hosted workspace copy and authority pack can disclose query coordinates and dates. The stamp does not establish source truth or a photograph’s capture circumstances. Whisp annual burned-area fields and the bundled Natural Earth outline are read locally from held data. Independent reading of a stamp stays offline.
Evidence Agent preparation
The Evidence Agent is being prepared and is switched off. Prepared samples run on the device. When AI reading is later enabled, each selected document needs a separate choice to send that file set to Anthropic in the United States. Plot files stay on the device. OpenStamps keeps no server-side copy of the uploaded document or extraction; this does not promise immediate deletion by the processor. Processor terms, retention, the data-processing agreement and the international-transfer basis must be reviewed before this option is enabled.
The demonstration keeps device-signed step records with salted input/output commitments. Its sample seals have no independent time anchor. An AI extraction or draft does not establish that source claims are true, certify a supplier or file a due-diligence statement. Optional button counts accept no document, email or free text; they do not request a call or promise contact.
Sharing a record with another buyer
This feature is being prepared and is switched off. When enabled, you choose each buyer and each record. A newly made record keeps the buyer and product as a salted commitment; its opening goes only to the original buyer’s request. Other buyers receive the existing record and seal, without that opening, your photo or the list of other buyers. A private plot name needs a separate choice for each buyer.
Your phone keeps the share list and withdrawal keys. The panel is hidden when the phone is marked shared. Withdrawal stops future collection through OpenStamps; it cannot recall a copy already downloaded. Server payloads expire with the request; an early closed request is retired on its next touch or at its original expiry. A payload-free marker remains for 30 days after the later of expiry and retirement, then is removed by the bounded hourly cleanup. Backups retain encrypted earlier bytes until normal archive expiry, but a restore does not reopen shares or restore their payloads. The farmer panel remains English-only pending native review.