Privacy Policy
Last updated: 12 November 2026
In short
- Amana is a place to keep your family's important documents: passports, policies, certificates, records. You decide what to save, who else can see it, and you can take it all back at any time.
- We do not sell your data. We do not show you adverts. We do not share anything with anyone for marketing.
- Amana keeps your documents and details encrypted when they are stored and when they travel. Amana's systems open them to show them to you and the people you choose, and to help you organise them. Your most sensitive details are kept under a separate key, and every use of that key is recorded. Our team does not look through your documents or details. The detail, and the limits, are in section 8.
- You can delete everything, at any time, and we will actually delete it.
- If you share your vault with a Helper, a family member or friend you trust, only you decide who, and you can stop it instantly.
The rest of this policy is the detail. If you only read one section, read section 8.
1. Who we are
Amana is provided by Tessera42 Ltd, a company registered in England and Wales, company number 17405769, registered office Suite RA01, 195-197 Wood Street, London, E17 3NU, United Kingdom.
We are the data controller for the information described in this policy. That means we decide how and why it is used, and we are responsible for it.
We are registered with the UK Information Commissioner's Office (ICO), registration reference ZC234594.
Privacy questions and rights requests: privacy@myamana.app
Everything else: support@myamana.app
We are a very small company. There is no legal requirement for us to appoint a Data Protection Officer, and we have not appointed one. Privacy questions go to the address above.
2. Who this applies to
This policy applies to everyone who uses Amana, wherever you live. It also applies to anyone who opens a link to a document that an Amana user has shared with them, even without an account. Section 9.7 is written for you.
Amana is currently in closed beta with testers in several countries. Rather than vary your protection depending on where you happen to be, we apply one standard to everybody, based on UK and EU data protection law. This is the strictest of the standards our current testers are subject to, and the most defensible. If your local law gives you rights beyond the ones described here, those rights still apply, and you can contact us to use them.
You must be 18 or over to hold an Amana account. Amana is not designed for children and we do not knowingly collect information about anyone under 18. If you believe a child has created an account, tell us and we will remove it.
3. What we collect
We collect three kinds of information. Nothing else.
3.1 Your account
What / Why we need it
- Your first name
- So the app can address you, and so a Helper or emergency contact you invite knows who invited them
- Your email address
- To sign you in, to send you the emails described in section 7, and to be able to reach you
- Your password
- Stored only as a one-way cryptographic hash. We never store the password itself and cannot recover it or see it.
- Your second step at sign-in: a passkey, an authenticator app, or both
- For a passkey we keep its public key, a name for it and when it was last used. Your face, fingerprint or device passcode stays on your device. For an authenticator app we keep the shared secret it uses to make codes, encrypted with keys we hold
- Devices you ask us to remember
- When you tick "Remember this device", or finish the second step in the iPhone app, we keep a random reference for that device, the type of browser or device, and when it was last used. We do not ask for your second step there again for 90 days from its last use
- A backup email address, if you add one
- Once you confirm it, we send some security alerts there too, including the alert, with its stop link, when a support case about your account starts. It cannot be used to sign in and does not receive password resets
If you pay for a plan. Payments on our website are taken by Stripe (section 9.2). You type your card details into Stripe's own payment form, and they go straight to Stripe. We never see or store your full card number or security code. From Stripe we receive and keep: your name and email address, the plan you chose, the amounts and dates of your payments, whether a payment succeeded or failed, the last four digits, brand and expiry month of your card, and the country of your billing address, which we need to charge the right VAT.
If you pay in the App Store or Google Play, Apple or Google take the payment (section 9.3). We receive only what we need to run your plan: which plan you bought, when it started and renews, and a purchase reference. We never receive your card or store account details.
3.2 What you put in your vault
This is the part that matters most to you, so here it is in full.
What / Notes
- The files you upload
- Photos, scans and PDFs. Whatever you choose to save.
- The title you give each document
- Any notes you write
- The category you file it under
- Family, Finance, Property, Insurance, Legal, Contacts or Medical
- Details you type in about the document, such as an issue or expiry date, who issued it, and a note about where the paper original is kept
- We can read these, and we need to, so we can remind you before something expires. See section 8.2.
- Your protected details: details you type in such as a reference number, policy number, sort code, the last digits of an account number, a holder's name, a date of birth or an address
- These are kept under a separate key for each person, and every use of that key is recorded. On Medical pages and other sensitive pages, the title, notes, type, issuer and category are protected details too. Which details you are asked for depends on the kind of document. See section 8.1.
- A searchable copy of text from some documents, when you have turned document search on
- Your device reads the document, removes fixed-format numbers it can recognise (for example card numbers, IBANs and UK National Insurance numbers in the published shape), and sends only that masked copy. We store it encrypted with keys we hold, only for open pages of document types that allow search, and only while search is on. Turning search off clears it. Dates of birth and unformatted reference numbers can remain in that copy. Medical pages never store it. See section 8.4.
- The name of who issued a document, when we do not already know it
- We copy that name, with nothing else from the page, to a list our team reads, so we can add the issuer's logo and spelling. The list does not say whose document it came from. If you type a person's name as the issuer, it can be copied too. Pages you file as Medical, and pages not yet filed, are not copied.
Dates and reference numbers are still ones you type or confirm. Unless suggestions are on (see section 3.7), we do not pull expiry dates, issue dates or protected details out of the file into those fields. Separately, when document search is on, your device can read the text of an allowlisted document, mask fixed-format numbers, and send that masked copy so you can search. That reading happens on the device, and search sends no file to a cloud OCR provider. Section 8.4 describes how that works and what the masker misses. Section 8.3 explains who can open your files.
We do not store the original filename of the file on your device. It is replaced with an opaque internal reference the moment you upload, so a filename that might reveal something sensitive never reaches our systems in the first place.
3.3 Helpers and emergency contacts
If you invite a Helper, someone you trust to have read-only access to your vault, we store who they are, what they can see, and when that access was granted or changed.
If you name someone as an emergency contact, we store that you did, when, and when they accepted. They can be one of your Helpers or someone without an Amana account. If they ask for access, we store when they asked, their statement that you cannot use Amana yourself, and whether the request was stopped, ended because you signed in, withdrawn or went ahead. After they are let in, we store whether you kept or removed their access. If a change of plan turns an emergency contact off, or back on, we store that too. Section 9.9 explains how this works.
3.4 Technical and security information
What / Why
- Your IP address and browser or device type, each time you sign in
- To keep the account secure and to spot someone signing in who should not be
- An activity log of actions taken in your vault
- So you can see what happened in your own vault, especially if you have given a Helper access
- Basic error logs
- So we can fix things when they break
Our activity log records what happened, when, and who did it. It does not record the contents of your documents. Each time someone other than you opens one of your pages, and each step of a support case about your account, appears in it. A Helper's own account activity outside your vault, such as resetting their own password, is not included, because this log exists for your oversight of your vault, not surveillance of the person helping you.
3.5 Waitlist
If you join the coming-soon waitlist before you have an Amana account, we collect only the information in the table below.
What / Why
- Your email address
- So we can confirm you asked to join, and so we can email you when a beta invite is ready
- Your language preference
- So waitlist emails arrive in a language you can read
- The kind of phone you use
- If the form asks: iPhone, Android or something else. We use it to plan the beta and to email you about it
- Who Amana would be for
- If the form asks: you, someone you help, or both. We use it to plan the beta and to email you about it
- A feature you ask to hear about
- If you ask us to tell you when a feature is ready. We email you about that feature when it is
The lawful basis is consent. You tick a box on the waitlist form before we store anything. We send a confirmation email; your address stays unconfirmed until you open that link.
Unconfirmed waitlist records are deleted after 30 days. Confirmed records stay until you unsubscribe, or until we no longer need them to run the beta waitlist.
Every waitlist email includes an unsubscribe link. You can also open the unsubscribe link from the confirmation or invite email at any time. After you unsubscribe we will not send you further waitlist or beta-invite mail, and we delete the features you asked to hear about. We keep your address on a list of people who asked not to be emailed, so that we do not write to you again.
We do not sell waitlist addresses, and we do not use them for advertising.
3.6 Chat
Chat lets you ask a question about what you have saved. You choose to open it. A Helper looking at your vault does not get Chat.
Chat sends the names, types and dates of your pages to Mistral, a company that answers the question for us. It also sends anything you type, including your question and the earlier turns of that same conversation. It does not send Medical pages, or other pages whose title is a protected detail (section 8.1), at all: not the name, not the type, not the dates. It does not send your files. There is one exception, and it is yours to choose. You can pick one protected detail from one of your own pages, such as a policy number or an address, check it, and say yes. That one detail is then sent with that one question. If a person page names someone else, including someone who does not have an Amana account, that name is included.
Please don't type account numbers, policy numbers or passwords. Chat cannot stop you, and anything you type is sent. If you want Chat to use one of your protected details, choose it with "Use a protected detail" instead, so you can check it before it goes.
Amana does not keep the conversation after you close it. There is no saved chat history on our side. Mistral does not keep what you send, or the answer, after it has replied.
Mistral processes this in the European Union. Its terms allow temporary transfers outside the EU to companies it lists as subprocessors. We have switched off the setting that would let Mistral use these calls to train its models.
The lawful basis is the service you asked for: an answer to your question. When you choose a protected detail, you ask for it to be used for that one question, and you check it before it goes. The notice shown before your first Chat message says the same thing, in short.
Amana does not keep a protected detail you send. It passes through our server in that one request and is not stored. We record that you sent one, which kind it was (for example "policy number") and from which page, so you can see it in your Activity. We never record the detail itself, your question or the answer.
3.7 Suggestions when you add a document
When suggestions are on, Amana sends the document you add, or the photo you just took, to Mistral. Mistral is the company that also answers Chat, and it works for us through its service in the European Union. It reads the document and suggests what kind of document it is, its name, who issued it, its dates and some of its details, such as a date of birth or an ID or account number.
A document you add from Medical is not sent. A document you add without choosing Medical first is sent, even if it is about your health. When Amana asks whether to turn suggestions on, saying Yes also means you agree to that, and we record that you did and when.
If the document itself cannot be used, Amana sends the words read from it instead, after taking out card numbers, IBANs, UK National Insurance numbers, UK sort codes next to an account number, and passport code lines.
Every suggestion is a proposal. Nothing is saved until you check it, and you can change or remove any suggestion. A number, date of birth or address you accept is kept as a protected detail (section 8.1). You can turn suggestions off at any time in Settings.
Mistral does not keep the document or the words after it answers. Amana keeps no second copy of the document for this. The document you save is kept as described in section 3.2. Mistral's terms allow temporary transfers outside the EU to companies it lists as subprocessors.
Amana records in your Activity that suggestions were sent. To measure how well they work, it also records which kinds of detail were suggested and whether you accepted, changed or dismissed each one. It never records the document, the words read from it or a suggested value.
The lawful basis is the service you asked for by adding a document with suggestions on.
3.8 Documents you send by email
If your plan includes it, you can email a file to a personal Amana address, and it appears in your vault for you to file. Resend, the company that sends our email, receives the message. Amana fetches each attachment that is allowed, removes its hidden details, and saves it as a page named "Email" with the date.
We keep the file and a receipt that links the message to your account. We do not keep the sender, the subject, the text of the message or the original file name. We do not check who sent the message, so anyone who has your Amana address can add a file to your vault.
Resend's own terms say it keeps a received message for 30 days, in the United States. While we file the message, its reference and the address it was sent to wait in our job queue until the job finishes. The sender's address and the subject can appear in our server logs.
The lawful basis is the service you asked for: adding a document to your vault.
3.9 If you say yes to research emails
In Settings you can choose to be asked to help with research. It is off until you turn it on. If you turn it on, we keep the date you said yes, and our team can see your email address and that date on a list. Now and then we may email you a few short questions, or ask whether you would like a call. The lawful basis is your consent. If you turn it off, you leave the list at once.
3.10 If you ask us to help you get back in
Most people get back in on their own. "Forgot password" sends a link to your email, and then you use your second step. If you set up more than one second step, "Try another method" lets you use the other one.
If that does not work, you, or one of your Helpers, can email support@myamana.app. We do not say whether an account exists until we have checked it is you. Depending on what you have lost, we ask for a reply from the email address on your account, or for a live video call on Zoom where you show photo identification and answer two questions only you would know. If you have a Helper, we ask them to confirm it is you from their own Amana account. If you have no Helper and a paid account, we also ask for billing details.
Before we change anything there is a wait: 24 hours, or 5 days if you have no Helper to confirm it is you. When it starts, we email the address on your account, your backup email if you have confirmed one, and your Helpers, and we send an alert to your phone. Each email has a "This wasn't me" link. One tap stops the case, and stopping it changes nothing on your account. You can also stop it from Amana if you are still signed in.
When the wait is over, we sign you out everywhere, remove your old passkeys, authenticator app and remembered devices, and tell your Helpers. Then we email you a link to get back in and set up a new second step. If your email address changed, the link goes to the new address and you choose a new password too. Our team never sets your password and never sees your protected details.
We keep a record of the case: which checks we did, never the documents or answers you showed us, who confirmed it was you, the new email address if there is one, and when each step happened. We do not record the video call, and we do not keep a copy or a picture of your identification. The record is deleted 12 months after the case ends. Each step also appears in your activity log.
The lawful basis is the service you asked for: getting back into your account. When we refuse or stop a recovery, and when we keep the case record, we rely on our legitimate interest in keeping your account out of the wrong hands (Article 6(1)(f)).
4. What we do not collect
We think this list is as important as the one above.
- No tracking cookies beyond the two described in section 5, no advertising pixels, no session recording, and nothing that follows you to other websites. Our web pages load no third-party code at all. We do use one analytics tool, PostHog, to count a small number of things about how the app is used, described in section 5. It never sees your documents, your name or your email address, and you can switch it off at any time.
- No location data.
- No contacts, photo library, calendar or other data from your phone, beyond the specific file you choose to upload.
- No full card numbers or security codes. Stripe, Apple or Google hold those. We keep only what section 3.1 lists.
- No data bought from, or shared with, data brokers, advertisers or marketing companies. Ever. This is a commitment, not a current-policy statement that might change quietly. If it ever changed, we would tell you and give you the chance to leave first.
5. Cookies and similar technology
Amana puts up to three small pieces of information on your phone or computer. Each is needed for signing in or for security, which is why there is no cookie banner.
What / Why / How long it stays
- A sign-in cookie
- Keeps you signed in, so you are not typing your password on every screen
- Until you sign out, or 90 days after you last used Amana
- A security cookie
- Stops another website making requests to Amana while pretending to be you
- Until you close the app or browser
- A remembered-device cookie
- Lets Amana skip your second step on this device after you type your password. Only set if you tick "Remember this device", or finish the second step in the iPhone app
- 90 days after you last signed in with it. Signing out does not remove it; removing the device in Settings does
None of them contains your documents, your name or your email address. The sign-in and remembered-device cookies are random references that mean nothing to anyone except our server.
If you use the iPhone app and turn on Face ID or Touch ID to unlock Amana, the app remembers that choice on your phone, and we keep a note that you turned it on. It is off unless you switch it on, and it unlocks your existing session on that device. Separately, you can sign in with a passkey, which uses Face ID, Touch ID or your device's passcode. A passkey sign-in is complete on its own. Your face and fingerprint never leave your device.
In a web browser, Amana also keeps a few notes in the browser's own storage, and they stay on that device: timings that let the page lock after 30 minutes without use or 12 hours after you last unlocked it, your recent searches, the last category you opened, an edit you have not saved yet (never your protected details), and whether you said "Not now" to an offer. That is the complete list of what Amana itself puts on your device. Nothing for advertising, and nothing that follows you to other websites.
Usage insights, and how to turn them off.
We would like to know whether Amana actually works: how many people finish signing up, how long it takes to save a first document, whether a Helper can find something when it matters. To measure that we use PostHog, an analytics service whose European servers are in Germany.
What PostHog receives is a random reference number that identifies your account to us and to nobody else, the name of the thing that happened (for example "saved a first item"), and a small number of measurements such as how many seconds something took, or whether you accepted or dismissed a suggestion card on Home. It never receives your name, your email address, your documents, or anything you type, including the comment box on our feedback form, which comes to us by email instead. It does not receive your IP address or your location.
This is on unless you turn it off, and you can turn it off at any time in Settings, under "Privacy and consent". It stops immediately, we do not ask why, and nothing else in the app changes. We rely on our legitimate interest in knowing whether the product works, and we have weighed that against your privacy: the data is small, it is not linked to your name or your email, it is never used to advertise to you and never used to make any decision about you.
No analytics code runs in these pages, and PostHog puts nothing on your phone or computer. That is why there is still no cookie banner: the cookies and browser notes above remain the only things Amana stores on your device.
(An earlier version of this policy said we used no analytics tool, and promised to update this section before introducing one. We started using PostHog on 4 September 2026 and did not update this section at the time. That was our mistake, and this paragraph is the correction rather than a quiet rewrite.)
6. Sensitive documents
Amana has a Medical category. People use products like this for hospital letters, prescriptions, insurance claims, passports and immigration papers. Some of that is what the law calls "special category data": information about your health, your ethnic origin, your religion, or similar. The law gives it extra protection, and rightly so.
Two things follow from that.
First, we ask for your explicit consent, separately from anything else, before you can store this kind of document with us. That consent is the legal basis on which we hold it (UK GDPR Article 9(2)(a)). It is a real choice, it is not bundled with anything else, and you can withdraw it at any time in Settings. If you withdraw it, every document in your Medical category is deleted immediately, including anything in your Trash. This cannot be undone, and we tell you this before you consent, not after.
Second, you choose document by document whether something goes in your Medical category. Nothing is filed there automatically.
A note about other people's documents. Many people use Amana to keep documents belonging to a parent, a partner or a child: someone else's medical letter, someone else's passport. That is a normal and expected use of the product. If you are doing this purely for your own family and household, data protection law generally treats it as a personal or household activity and does not put legal duties on you. Please think about it anyway: save what you genuinely need, tell the person if you reasonably can, and delete it when it is no longer needed. If you are doing this in a professional capacity, for example as a carer, an adviser, or an attorney acting under a power of attorney, you may have your own legal responsibilities and should take your own advice.
7. Why we are allowed to use your information
Data protection law requires a specific legal reason, a lawful basis, for everything we do with your information. Here is ours, in full.
What we do / Why / Legal basis
- Create and run your account
- You asked us to
- Contract, Article 6(1)(b)
- Store your documents, titles, notes, categories and reminders
- That is the service
- Contract, Article 6(1)(b)
- Store sensitive documents within that
- Same, plus the extra permission the law requires
- Contract, Article 6(1)(b), and explicit consent, Article 9(2)(a)
- Run the Helper feature, and let you revoke access at any time
- You asked us to share with a specific person
- Contract, Article 6(1)(b)
- Send you account and security emails
- Necessary to operate the account
- Contract, Article 6(1)(b)
- Record IP address, device type and sign-in records
- To keep your account secure and detect misuse
- Legitimate interests, Article 6(1)(f)
- Keep an activity log of your vault
- You are entitled to see who did what in your own vault, and we need it to investigate problems
- Contract, Article 6(1)(b), and legitimate interests, Article 6(1)(f)
- Respond to you when you contact us
- Contract or legitimate interests, depending on what you're contacting us about
- Ask for and act on your beta feedback
- To make the product work better
- Legitimate interests, Article 6(1)(f)
- Count a small number of things about how the app is used, unless you switch usage insights off
- To find out whether the product actually works
- Legitimate interests, Article 6(1)(f)
- Meet our legal obligations
- Where the law requires it of us
- Legal obligation, Article 6(1)(c)
- Send you a push alert for a small number of security events, on devices where you've allowed it
- In your own interest, as a second channel alongside email
- Legitimate interests, Article 6(1)(f)
- Record each time a document shared by link is opened
- So there is a reliable record of when a shared document was opened
- Legitimate interests, Article 6(1)(f)
- Count that a shared file was opened, and how long it took
- To find out whether sharing works
- Legitimate interests, Article 6(1)(f)
- Run a shared folder, so the people in it can see the documents there and, where you allow it, change them
- You, or the person looking after the folder, asked to share those documents with specific people
- Contract, Article 6(1)(b)
- Check it is you and help you back into your account, with a wait and alerts first
- You asked us to; and to keep your account out of the wrong hands when someone else asks
- Contract, Article 6(1)(b), and legitimate interests, Article 6(1)(f)
- Let an emergency contact you named see and download your documents, after a wait in which you did not stop it
- You asked us to set this up
- Contract, Article 6(1)(b)
- Keep the name and email address of an emergency contact you named who has no Amana account, so they can ask for access later
- You named them
- Legitimate interests, Article 6(1)(f)
- Take payments for your plan, renew it, and tell you before it renews or if a payment fails
- You asked us to
- Contract, Article 6(1)(b)
- Keep records of your payments and the country used for VAT
- The law requires us to keep accounting and tax records
- Legal obligation, Article 6(1)(c)
- Handle a refund you ask for
- You asked us to, and consumer law gives you the right
- Contract, Article 6(1)(b), and legal obligation, Article 6(1)(c)
Where we rely on legitimate interests, we have weighed our interest against your rights and concluded it is proportionate. In each case the purpose is security, integrity or basic product improvement, none of it involves profiling you, and none of it is used to make automated decisions about you. You can object to any of it: see section 12.
We do not use your information for advertising, and we do not sell it. This will never change.
8. What our encryption does and does not do
Everything travelling between your device and us goes over an encrypted connection (TLS), on every page.
Here is how we protect what you keep, in three sentences:
- Amana keeps your documents and details encrypted when they are stored and when they travel. Amana's systems open them to show them to you and the people you choose, and to help you organise them.
- Your most sensitive details, such as passport numbers, dates of birth and home addresses, are kept under a separate key. Every use of that key is recorded.
- Our team does not look through your documents or details. If you ask us to help you get back into your account, we may open one identity document to check it is you, and you will see that in your activity log.
The rest of this section explains each part, what is true in the app today, and where the limits are.
8.1 Your protected details
Which details. Your protected details are the reference numbers, policy numbers, sort codes, last digits of account numbers, holders' names, dates of birth and home addresses you type in, the details on a person's page and in your contacts, and the photo on a person's page. On Medical pages, other sensitive pages and pages you have not filed yet, the title, notes, document type, issuer and category are protected details too. Dates such as an expiry date are not, because we use them to remind you.
How they are kept. Each person has their own key for these details, used with AES-256-GCM, the standard cryptography built into our servers' software. Your key is stored only in a locked form. The key that unlocks it is held by Amazon Web Services' key service in Frankfurt (section 9.2) and never leaves it. When Amana needs to show you a protected detail, it asks the key service to unlock your key, uses it for that one request, and then lets it go. It is never written to disk, to a log or to a job queue. A copy of our database on its own shows no protected detail.
Every use is recorded. Amazon's key service records each time a person's key is unlocked, outside Amana's own systems, and we are alerted if an unusual number are unlocked in a short time.
Who can see them. You. A Helper, on the pages they can see. People in a shared folder, on the pages in that folder. An emergency contact, once their access is released (section 9.9). They are not shown to someone who opens a link you shared. Each time someone other than you opens one of your pages, it appears in your activity log.
Our team does not look through them. Amana's staff screens are built so they cannot show a protected detail. Protected details are kept out of our logs, error reports, usage insights, push alerts and activity log entries.
The limit, said plainly. This protection rests on rules and records, not on it being impossible. Someone who controlled both the running Amana service and the key service could read protected details. Only the running Amana service is allowed to unlock keys for real accounts. The people who run Amana can manage that key but are not allowed to use it to unlock anything, and Amazon records any change to that rule outside Amana. We would rather you hold us to a promise you can understand than trust a claim you cannot check. If the key service cannot be reached, protected details show as "Temporarily unavailable" until it is back, and the rest of Amana keeps working.
8.2 The information around your documents
This is how Amana works today.
Except on the pages in section 8.1 whose title is a protected detail, the title of each page, your notes, the document type, the issuer or provider, the category, the name on your account, and, when document search is on, the masked searchable copy described in section 8.4, are encrypted inside our database, and Amana holds those keys. Dates such as an expiry date or an issue date, and your note about where the paper original is kept, are stored as ordinary fields in that same database, which is encrypted at rest and is not reachable from the public internet.
We can read all of this, and we need to. It is what lets us remind you before your passport expires, sort your vault by category, and let a Helper find the right paperwork.
8.3 The document files themselves
This is how Amana works today. Your document files are kept apart from your details. Before a file is stored, Amana encrypts it with a key Amana holds, and our storage provider encrypts it again.
Amana's servers can open your document files, to show them to you and to help you organize them. They are encrypted in storage and in transit, and every time one is opened it is written to your vault's activity log. Your files are stored in Cloudflare's EU storage and are not publicly reachable. A Helper or someone holding a share link can also open a file.
We do not open your files to look through them. If you ask us to help you get back into your account, we may open one identity document to check it is you, and you will see that in your activity log. Otherwise we would only access the contents of your vault if you asked us to in order to fix a problem, or if we were required to by law. If that ever happens for any reason other than your own request, we will tell you.
8.4 Text read on your device so you can search
This is how Amana works today, when you turn document search on.
On the iPhone app, Apple's Vision framework reads the capture on the device. In the browser (including the Desktop Vault), the text layer of a PDF is read in the page, and for a photo or a scan a local reader in the page (Tesseract.js) does the same. Nothing is sent to a cloud OCR service for this. Android reading with ML Kit is decided and not built yet.
Before anything leaves the device, a masker removes fixed-format numbers it can prove: payment card numbers that pass a check digit, IBANs that pass their checksum, UK National Insurance numbers in the published shape, a UK sort code written next to an account-number run, and a passport machine-readable zone. It does not understand the page. It leaves in dates (including dates of birth), policy and membership numbers with no fixed shape, names, addresses and ordinary sentences. We may say which formats are removed. We do not say the copy is safe or that we cannot see personal data in it.
Only that masked string is stored, encrypted with keys Amana holds (the same tier as titles and notes), and only when all of these are true: you have turned document search on; the page is not Medical or another page whose title is a protected detail (section 8.1); and the document type is on the searchable list. A page saved before you turned search on, closed before you confirmed, or filed as Medical, does not gain text later. Turning search off stops new capture and clears stored text. Cleared text is not restored.
Anyone who can already open the page can search that text: you, a Helper on your vault (except a page you have withheld from Helpers), and a shared-folder member who can open the page. Search does not show the text in the result list. Opening a result so the stored text is read is recorded in your Activity. Matching alone is not.
You choose this. The first time a capture would store text, we explain and ask. You can say not now, turn it on later in Settings, or turn it off later. Turning it off clears what was stored. The lawful basis is the search service you asked for by turning it on, not a separate consent tick.
9. How we share your information
We do not sell your information, ever. We share it only in these situations.
9.1 With your Helpers
Inviting someone as a Helper gives them read-only access to your full vault, every category. A Helper sees the whole vault, except any page you choose to withhold from your Helpers. Sharing particular documents with other people is a shared folder, described in section 9.8. Sharing every document in a category, without choosing the documents, is not built. You can revoke a Helper's access instantly, at any time, from within the app. Revoking access is immediate and unilateral; it does not require the Helper's agreement.
9.2 With service providers who help us run Amana
We work with a small number of providers under contract, each restricted to using your information only to provide their specific service to us.
Provider / What they do / Where
- Supabase
- Database hosting
- Frankfurt, Germany (EU)
- Cloudflare (R2)
- File storage, with a jurisdictional restriction locking data to the EU
- EU
- Cloudflare
- Also sits on the network path as our content delivery and TLS termination layer for all traffic, wherever the nearest edge happens to be
- Global edge network, observed for Amana traffic in London
- Render
- Application hosting
- Frankfurt, Germany (EU)
- Resend
- Our account and security emails, and documents you email to your Amana address if your plan includes it
- United States. Resend relies on the Standard Contractual Clauses and the EU-US Data Privacy Framework
- PostHog
- Usage insights, unless you have switched them off. Counts of things that happened, tied to a random reference number, never to your name or email
- EU servers in Germany
- Mistral
- Answers Chat questions and suggests details for documents you add. Receives the names, types and dates of pages whose title is not a protected detail, names on person pages, and anything you type. If you choose a protected detail for a Chat question and say yes, it receives that detail too. When suggestions are on, it receives the document you add, or the words read from it. Does not receive documents you add from Medical. Does not keep what you send, or the answer, after it has replied. See sections 3.6 and 3.7
- European Union, with temporary transfers outside the EU to Mistral's listed subprocessors
- Amazon Web Services
- Holds the key that unlocks each person's key for protected details, and records every use of it (section 8.1). It receives your locked key and the random reference number of your account, never a protected detail, a document or your name
- Frankfurt, Germany (EU). Amazon is headquartered in the United States and relies on the Standard Contractual Clauses
- Proton Mail
- Hosts our support and privacy email addresses, so it holds the emails you send us and our replies
- Switzerland
- Zoom
- Video calls, only when we need to see you to help you get back into your account (section 3.10). Calls are set never to be recorded
- United States. Zoom relies on the EU-US Data Privacy Framework and the Standard Contractual Clauses
- Stripe
- Takes payments on our website, stores your card details, and sends us the payment information in section 3.1. Stripe also uses some of this information for its own purposes, such as preventing fraud and meeting its legal duties as a payment company. For those purposes Stripe is responsible for it under its own privacy policy: https://stripe.com/privacy
- United Kingdom and Ireland for our account. Stripe may also handle your information in the United States, relying on the EU-US Data Privacy Framework, its UK Extension and the Standard Contractual Clauses
Data processing agreements with Supabase, Cloudflare, Render, Resend, PostHog, Mistral, Amazon Web Services, Proton Mail, Zoom and Stripe are in place. For all of them except PostHog these form part of the standard terms we accept when using the service; with PostHog we have a separate signed agreement. Mistral's agreement cannot be signed as a separate paper: accepting the terms is the agreement.
9.3 With Apple and Google
If you join our closed beta through TestFlight, Apple receives your email address to send you the invitation, and collects its own installation and crash information from the TestFlight app. Apple acts as an independent controller for this, under its own privacy policy and terms, which you agree to separately when you join TestFlight. This is outside our control and outside the data processing agreements described above.
If you buy a plan in the App Store or Google Play, Apple or Google sell it to you and take the payment. They act as independent controllers for that, under their own privacy policies and terms. They tell us which plan you bought, when it starts and renews, and a purchase reference, so that we can switch your plan on.
9.4 If required by law
We may disclose information if legally required to, such as in response to a valid court order, or where necessary to protect someone's life or safety. We will tell you if that ever happens, unless we are legally prohibited from doing so.
9.5 If Amana is acquired or merged
If this happens, your information may transfer as part of that transaction. We will tell you before this affects you.
9.6 With Apple, for security notifications
If you've turned on notifications, we register your device with Apple's push notification service (APNs) so we can alert you about a small number of security events: a change to your email address, your password or your second step, a support case about your account starting or finishing, and an emergency contact asking for access, the reminders on day 3 and day 6, and their being let in. Apple delivers the alert; the alert itself carries no content by design, only a device token and the timing. This is separate from the account and crash information Apple collects if you join our TestFlight beta, described in 9.3. You can turn push alerts off at any time in Settings, or by disabling notifications for Amana in your phone's settings.
9.7 Sharing a document by link, and if someone sent you one
You can send one document to someone who does not have Amana by creating a link. The link works for anyone who has it until it runs out, which is one month at most, or until you cancel it under "What You've Shared". Treat it like a key: if it is forwarded, whoever receives it can open that document too. We cannot tell who opened it, only that it was opened.
If someone sent you a link. You do not need an account, and this section is the part of this policy that applies to you. Tessera42 Ltd, named in section 1, is responsible for the information described here.
Each time the link is opened, we record the time, the type of browser or device you used, and a network address. At the moment that address belongs to Cloudflare, the network provider that passes your request on to us, not to you. We keep this record for 24 months, or less if the person who shared the link deletes their account, and it cannot be changed in the meantime. It exists so there is a reliable record of when a shared document was opened, and we rely on our legitimate interest in keeping one (Article 6(1)(f)).
The document is delivered to your browser by our own servers, which fetch it from our storage and pass it on to you. Cloudflare, the network provider that passes your request on to us, handles it on the way and sees your IP address. The storage itself does not receive your IP address. We also count that the file was opened and how long it took to load, using PostHog (see section 5). That count is tied to the link, not to you, and PostHog does not receive your IP address. The usage insights setting of the person who shared the link does not currently switch this count off.
We do not learn your name or email address from you opening the link, and we never use any of this to contact you, follow you elsewhere or advertise to you. If you are signed in to your own Amana account when you open it, the visit is recorded against your account like your other activity.
You have the rights in section 12, including the right to object. Email us at the address in section 18. Because we hold nothing that identifies you, we may need you to tell us which link it was and roughly when you opened it.
9.8 With people in a shared folder
A shared folder lets you and other people who have Amana accounts look after particular documents together. It is separate from a Helper. A Helper sees your whole vault and cannot change it. A person in a shared folder sees the documents in that folder.
Who can change things. One person looks after the folder. They can invite people, remove people, rename the folder and close it, and they can add and change documents. Someone else may be invited to add and change documents, or only to look. Everyone who has joined can read every document in the folder. Someone invited only to look cannot add, change or remove anything. That limit is a rule of the service. Who can open the folder is also a rule of the service, kept on our servers.
Who sees whom. Everyone who has joined sees the name of everyone else who has joined. An invitation that has not been accepted is visible only to the person who looks after the folder. If someone declines, the other members are not told.
When a document moves. If you leave the folder, you are asked whether your documents stay in it or come back to your vault. If they stay, they become the documents of the next person who looks after the folder. That person is whoever has been a member longest and can change documents, or, if nobody there can change documents, whoever has been a member longest. The documents move into that person's vault. Tessera42 Ltd remains responsible for them. Your account stays yours: your subscription, your Helpers and the way you sign in do not move. If you take the documents back, they stay yours and leave the folder. If someone removes you, the documents you added go back to your vault, and you are not asked. If your account is erased after the waiting period and other people are still in the folder, documents you had left there stay in the folder and move in the same way, because you are not there to be asked. The other members are told who left, by name. If you are the last member and you leave, the folder closes and your documents stay yours. If you are the last member and your account is then erased, those documents are erased with the account.
When someone's access ends, they cannot open the folder from that moment. We cannot take back what they already saved or remembered. An invitation to a folder does not expire after a set number of days. A closed folder is kept. There is no date on which we delete it. The name of the person who left is kept with the folder.
The name of the folder is stored so we can show it in a list. We can read that name, as we can read a document's title.
9.9 With an emergency contact
You can name emergency contacts, for a time when you cannot use Amana yourself. An emergency contact can be one of your Helpers or someone else. Your plan sets how many: one on the free plan, two on a paid plan. Naming them gives them nothing extra straight away.
If an emergency contact asks for access, they first confirm that you cannot use Amana and cannot give them access yourself. If they have no Amana account, they make one then. We tell you at once, by email and with an alert on your phone, and we remind you on day 3 and day 6. Only you can stop the request. Each email has a link to stop it, and you do not need to sign in to use it. If you sign in to Amana during the seven days, the request ends. We do not tell your Helpers. Stopping it changes nothing else, but that person cannot ask again for 30 days. The emergency contact can also withdraw the request.
If you do not stop it within seven days, the emergency contact is let in. They can open and download your documents and see your protected details. We tell you by email and with an alert on your phone. They cannot change or delete anything, and their access does not end on a set date. Each page they open appears in your activity log. When you next sign in, you choose whether they keep their access. Anything the let-in changed on your account is also put back: if we had set your paid plan to end, it carries on, and our usual emails start again. You can remove an emergency contact at any time.
The lawful basis is the service you asked for when you named them.
10. Where your information is stored
Your data is stored and processed within the European Economic Area: Frankfurt, Germany for our database and application hosting, and the EU for file storage. We do not currently transfer your information outside the UK or the EEA on a routine basis.
One honest exception. Cloudflare, our content delivery and security layer, terminates encrypted connections at whichever of its edge locations is nearest to you, which for our testers has been observed to be London. Traffic is decrypted briefly at that edge before being re-encrypted and forwarded to our Frankfurt servers. This is normal for how content delivery networks work, and London is within the UK, so this does not take your data outside the UK or EEA. We are disclosing it because it is a genuine step in the path your data takes, and we would rather tell you than let "EU residency" imply a single unbroken pipe that does not quite exist.
Most of our providers are headquartered in the United States. Mistral is in France and Proton Mail is in Switzerland. Your data itself rests in Europe as described above. Resend, Zoom and Stripe are the exceptions named in section 9.2: an email we send, a video call if we ever need one to help you back in, and your payment information can pass through the United States. Their support and engineering staff may occasionally need access from outside Europe to fix a problem. Where that counts in law as an international transfer, we protect it using the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as appropriate, with each provider.
If you are using Amana from outside the UK or EEA, for example from the UAE, Algeria, Venezuela or Chile, your information still travels to and is stored in Europe as described above, and this policy still applies to you in full.
11. How long we keep your information
What / How long
- Your account and everything in your vault
- Until you delete your account
- Records of your payments: plan, amounts, dates, refunds, the last four digits of the card, the country used for VAT, the billing emails we sent you (renewal reminders, receipts and payment problems) and which version of our terms you agreed to
- 6 years from the end of our financial year in which the payment was made, because UK law requires it. For payments from the European Union, 10 years, because EU VAT rules require it. We keep these even if you delete your account, and use them for nothing else.
- A deleted account
- 30 days, then permanently erased. This gives you a window to change your mind. Payment records are kept as the row above says.
- Your customer record at Stripe
- Deleted when your account is permanently erased, except what Stripe must keep under its own legal duties
- A document you put in the Trash
- 30 days on paid plans, 7 days on the Free plan, then permanently erased. You can permanently delete it yourself at any time before that.
- Medical category documents, if you withdraw consent
- Deleted immediately, including anything in Trash. This overrides the row above.
- An unaccepted Helper or emergency contact invitation
- 14 days, then it expires
- Your sign-in records
- Until you sign out or delete your account
- Activity log entries
- 24 months, then permanently deleted. This covers your own activity, your Helper's activity in your vault, activity in a shared folder, and each time a link you shared was opened. If your account is permanently erased, the network address and device type are removed from these entries at that point.
- A link you shared
- Stops working when it runs out or you cancel it. The record that it existed is kept until the document is permanently deleted.
- A device you asked us to remember
- 90 days after it was last used, then deleted. Sooner if you remove it, reset your password, change your second step, or are helped back in by our support team.
- The link that places a document in a shared folder
- Deleted when the document leaves the folder, or when the folder closes.
- A shared folder that has no members left
- Kept. There is no date on which we delete it.
- An invitation to a shared folder that has not been accepted
- Kept until the person accepts, declines, or the invitation is withdrawn. It does not expire after a set number of days. A Helper invitation expires after 14 days.
- The record of a support case
- 12 months after the case ends, then deleted. The activity log entries for it are kept like any other activity log entry.
- An emergency contact's request for access
- Kept until your account is deleted.
- A copy of your data you asked to download
- Deleted as soon as it is downloaded, and after about an hour if it is not.
- An account nobody has used for 24 months
- We email you at 12, 18 and 23 months. If the account is still not used at 24 months, it is deleted, and then erased 30 days later like any deleted account.
- An emergency contact who has no Amana account
- Their name, email address and the date they accepted: until you remove them or your account is deleted
Where the table gives a period, deletion is genuine and runs on a nightly automated job. It is not a flag in a database that hides your data from you while we keep it. A row that says we delete something at the moment access ends, or that we keep it, is not on that nightly job.
12. Your rights
You have the following rights over your information, from UK and EU data protection law, extended to every Amana user wherever you live.
- See it. Ask for a copy of everything we hold about you.
- Correct it. Have anything inaccurate fixed.
- Delete it. Have it erased. You can do this yourself at any time in Settings, without asking us or giving a reason.
- Take it elsewhere. Get your data in a portable format so you can move it to another service.
- Restrict it. Ask us to stop using it while a dispute or a correction is sorted out.
- Object. Object to anything we do on the basis of legitimate interests.
- Withdraw consent. Withdraw your consent to storing sensitive documents at any time, in Settings. Withdrawing it does not make anything we did beforehand unlawful.
To use any of these, email privacy@myamana.app. We will respond within one month. It is free, unless a request is genuinely excessive or repetitive, in which case we may charge a reasonable fee or decline it and explain why.
If you are unhappy with how we handle your data, please tell us first so we can put it right. You also have the right to complain to a regulator without coming to us at all. In the UK that is the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, ico.org.uk, 0303 123 1113. If you live elsewhere in the EEA you may complain to your own national supervisory authority. If you live outside the UK and EEA you may complain to your local regulator where one exists, and you may still complain to the ICO because we are established in the UK.
Separately, and more immediately: revoking a Helper's access is something you can do yourself, instantly, inside the app, without waiting on us at all.
13. Helpers: sharing your vault in full
Because inviting a Helper means someone else sees your information, here is exactly how it works.
Nothing is shared unless you invite them. There is no default sharing, no automatic sharing, and no way for anyone to request access to your vault without you starting it.
What a Helper can see: the documents in your vault, their titles, notes and categories, and the protected details on them (section 8.1), except any page you withhold from your Helpers. That is read-only. A Helper cannot edit, delete or add anything, and cannot invite anyone else.
What you can see: every action your Helper takes in your vault appears in your activity log. You will know what they looked at and when.
What your Helper knows about you: their invitation carries your first name, so they know who invited them.
What you know about your Helper: their email address, and the dates the invitation was sent, accepted or ended.
You can end it instantly. Revoking a Helper's access takes effect immediately, needs no reason, and does not require their agreement. Both of you get an email confirming it.
If you are the Helper, the vault owner sees your activity in their vault. You have your own Amana account and your own vault, entirely separate from theirs, and they cannot see anything in yours.
Sharing particular documents, rather than your whole vault, works through a shared folder. Section 9.8 describes who can see them, who can change them, and who sees whom.
If you ever need help getting back in. Any of your Helpers can confirm to our support team that it is really you (section 3.10). Your Helpers are told when a support case about your account starts and when it ends.
Emergency contacts. You can name emergency contacts: one on the free plan, two on a paid plan. They can be your Helpers or other people. If one of them asks for access, only you can stop it, and your Helpers are not told. If you do not stop it within seven days, they can see your documents. See section 9.9.
If you are an emergency contact without an Amana account. If someone names you as their emergency contact in Amana and you have no Amana account, we keep the name and email address they gave us, and the date you accept. We use them only so you can ask for access if that person cannot use Amana. We keep them until that person removes you or their account is deleted. If you don't accept, we delete them once the invitation ends after 14 days. You make an Amana account only if you ask for access.
14. Automated decisions and AI
Amana does not currently use AI to make decisions about your documents, sort them, or act on them without your review. We do not profile you, and no algorithm decides anything about your account. If this changes in future updates, any such feature will always require your review before anything is filed, extracted or shared automatically. Nothing happens silently, and we will update this section before any such feature ships, not after.
Section 9.8 describes the one rule that moves documents between vaults in a shared folder. When you are there, you choose whether your documents stay. The person they pass to follows the order in that section, and every member is told. It is not an assessment of you, and it is not AI.
15. Security measures
- Everything travels over an encrypted connection (TLS), enforced for every page.
- Passwords are stored as one-way hashes, must be at least 12 characters, and are checked on our own servers against a list of passwords known from data breaches. Signing in with a password also needs a second step, a passkey or an authenticator app, unless you are on a device you asked us to remember. A passkey sign-in is complete on its own.
- Protected details such as reference numbers, policy numbers, sort codes, dates of birth and addresses are kept under a separate key for each person, and every use of that key is recorded. See section 8.
- Document titles, notes, types, issuers and categories are encrypted in the database using keys Amana holds, as described in section 8.
- Files are stored separately from the database, in Cloudflare's storage, and are not publicly reachable.
- Access to the production system is limited to authorised administrators, who sign in to Amana's staff screens with a passkey, and two-step login is required on every service that offers it. Those staff screens are built so they cannot show a protected detail.
- In a web browser, Amana locks after 30 minutes without use, or 12 hours after you last unlocked it, and asks for your password or a passkey to carry on.
- Your password can only be changed through "Forgot password", which needs the link we email you and your second step. When your email address changes, we tell the old address and give it a link to undo the change.
No system is perfectly secure, and anyone who tells you otherwise is selling something. If there is a data breach that puts your rights or freedoms at risk, we will tell you directly and without undue delay, and we will report it to the ICO within 72 hours as the law requires.
You can help: use a long, unique password that you do not use anywhere else, and consider a password manager. Amana is not a password manager and does not store passwords.
16. This is a beta
Amana is currently in closed testing. Two things to be aware of.
It may break. Beta software has bugs. Features may change or disappear. Please keep your own copy of anything you cannot afford to lose, and do not treat Amana as your only copy of an important document during the beta.
Your data will not be deleted at the end of the beta. If Amana launches properly, your account and documents carry over. If we ever had to shut the service down, we would give you at least 30 days' notice and a way to download everything first. We would not delete your documents without warning you.
This policy itself is a beta document. It has been written by us to be accurate and complete under UK and EU GDPR, and will be reviewed by a qualified adviser before Amana leaves beta. If we identify anything in it that needs correcting in the meantime, we will fix it and update the date at the top.
17. Changes to this policy
If we change this policy in a way that materially affects you, we will email you before it takes effect and give you time to read it. Minor corrections, such as fixing a typo or clarifying wording, we will just make, and the "last updated" date above will change.
We will never quietly reduce your protections. If we ever wanted to use your data for something genuinely new, we would ask you first.
18. Contact
Privacy questions and rights requests: privacy@myamana.app
Everything else: support@myamana.app
Post: Tessera42 Ltd, Suite RA01, 195-197 Wood Street, London, E17 3NU, United Kingdom
Regulator: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF. ico.org.uk. 0303 123 1113.