Privacy notice
What this site collects
This site collects nothing by itself. It has no forms, analytics, cookies or tracking storage, and it makes no request on your behalf.
The service status page, status.retiform.ai, is a separate site. It is hosted by Better Stack, a company that provides status pages, and this notice's statement about tracking does not cover it: Better Stack may load its own analytics and advertising tags on the pages it hosts. It is linked from this website, the documentation and the console.
Access requests
The request-access link opens a message in your own mail program, addressed to access@retiform.ai. Nothing is sent until you send it.
- What a request contains: your name, the agent client you use, how many agents and people would share the store, what goes wrong for them today, whether you would need to host the service yourself, the country you are in, and your mail address, which is the reply address.
- Purpose: to decide on and send trial invitations, to answer questions about the trial, and to learn what people who run agents need, so the product is built for them.
- Recipient: Retiform's owner, who reads and answers the mailbox.
- Retention: a request that does not lead to an invitation is deleted no later than 90 days after its last message.
- Deletion on request: to have a request deleted sooner, write to access@retiform.ai from the same address and ask.
- What not to send: please answer the questions in general terms. Include no restricted, regulated or personal data beyond your name and contact details, and nothing confidential about your organisation or the people it serves.
The trial's own terms are in the terms of service.
Who is responsible
Retiform is operated by Retiform LLC, a Virginia limited liability company, in the United States. It decides why and how the personal data described in this notice is used.
Privacy questions and requests go to support@retiform.ai. To report a security problem, write to security@retiform.ai.
Your account in the trial
- What we hold: your email address, the times you signed in, the tenant you belong to and your role in it.
- How you sign in: with a one-time code sent to your email address. There is no password.
- Purpose: to let you sign in, to send you the messages listed under "Messages we send", and to show the members of your tenant who its other members are.
- Erasing your account: you can erase your own account from the console's Account page, after signing in
again. A tenant's only administrator must first make another member an administrator, or delete the tenant.
- Your account record, your membership, and any invitations and unsent messages to you are removed at once.
- The erasure request keeps your address only until the sign-in provider has deleted your sign-in. That deletion is retried until it succeeds, and you cannot sign in while it is pending.
- We then send one last email confirming the erasure. Its copy of your address is removed when it is delivered, or within an hour if it cannot be.
- We keep a keyed fingerprint of your address in the record of the erasure. It is not your address and cannot be reversed. It lets the erasure be applied again if the database is ever restored from a backup.
- The sign-in provider's own logs are not changed by an erasure. They are kept for as long as that provider keeps them.
- Records of what you did in a tenant remain, under an identifier that does not contain your address.
- The record of a sanctions check on your name is not removed. "How long we keep it" says what it holds and for how long.
Your tenant's content
Your tenant's content is the documents you upload, the passages made from them, the entities and memory entries that you and your agents record, and the questions your agents ask.
- Whose it is: yours. We process it only to provide the service to you.
- What you must not put in it: the terms of service forbid restricted, regulated and personal data in the trial. Please keep other people's personal data out of your documents and memory.
- Who can see it: the members and agents of your tenant. Each tenant's data is kept separate from every other tenant's in the database itself.
- Training: we do not use your content to train models, and our model provider's terms say it does not either (see "Other companies that process your data").
- Operator access: the operator does not read your tenant's content, except where that is needed to keep the service running or to answer a request you made. Operator actions on a tenant are recorded.
Records the platform keeps
- Audit trail. Every change in your tenant is recorded with who made it, a person or an agent, and when. You can read and verify it. It names people by an identifier, not by address. An agent's client can send a short session label with a memory entry it writes. The label is text the client chose, kept with the entry and its audit record and shown as the client's own text, so do not put personal data in it.
- Usage. Counts of documents, stored text, searches and model use for your tenant, to apply the trial's limits and show them to you.
- Context usage. For each tenant, each agent and each day (UTC), the platform counts the answers it gave to context and memory-recall requests, how many requests were refused at the plan's monthly retrieval limit, and how large the answers were, as a total and as a count per size band. The agent is recorded by its client identifier, or as "console" when a person uses the console. The platform also records the time of each agent's first such answer of the day, and marks each day on which an agent made any request, so that the usage page can show how often each agent uses the store and whether it reads before it writes. These records hold counts, sizes, days and times only, never questions, answers, memory entries or document text. The size of your tenant's stored content and the counts of memory entries each agent wrote, shown beside them, are worked out from your tenant's own data when the page is read and are not stored again. The members and agents of your tenant can read these records on the console's usage page, and no other tenant can. They are deleted after 35 days, and when the tenant's data is erased.
- How we measure the trial. For each tenant, the platform records when it first reaches five steps: the tenant is created, an agent first connects, a first document is uploaded, a first answer with citations is returned, and a first memory entry is written. It also records the first time a request is refused for each plan limit, counts request errors per tenant for seven days, and records which of the getting-started emails described under "Messages we send" a tenant was sent and when. These records hold the tenant's identifier and times only, never your documents, questions, memory or name. When a tenant is deleted, its records are turned into weekly counts that identify no tenant. We count invitations and signups per week, with no names or addresses. We use no website analytics, tracking pixels or third-party scripts.
- Totals across all tenants. Each day and each week the platform adds up figures across every tenant: for example how many tenants are new, active, at a limit or paying, how much context was served, and what the models cost us. A total holds no tenant's identifier, no person and no content, and cannot be traced back to a tenant. We keep these totals to see how the service is used over time, and they remain after the tenants they counted are deleted.
- The exit survey. When you delete a tenant, when a trial tenant is about to be deleted for inactivity, or when the trial ends, the console may ask you a few optional questions: why you are leaving, what you used the platform for, whether you are an individual or a team, and what you would pay. Your answers are kept apart from your tenant's data and are linked to you only by a one-way code derived from your email address, so that we can delete them if you ask us to erase your account. If you write a comment, it is kept as you wrote it. Answers are kept for up to 12 months, or until we set our prices, whichever comes first. Weekly reports show only counts, and any count under five is shown as "under five".
- Support messages. If you write to support@retiform.ai, your message is kept in our support mailbox, outside the platform, for as long as needed to answer it and for at most 12 months. Only its weekly count enters our reports.
Other companies that process your data
- OpenAI computes the embeddings that make search by meaning work. It receives the text of your passages and of your searches, and images of document pages if reading of PDF pages is turned on. Its terms for this use say that it does not train on this data and keeps it for up to 30 days to monitor for abuse, and longer for an image it flags.
- Auth0 provides sign-in. It holds your email address and the one-time sign-in codes.
- Microsoft sends the sign-in code emails, through Microsoft 365. It receives your email address and the message that carries the code.
- Oracle Cloud Infrastructure hosts the service, its database and its storage, including export archives, in Ashburn, Virginia, in the United States. Its email service sends the other messages listed below.
Paid plans
This section applies once paid plans are open. The trial takes no payment, so no payment company receives your data during the trial.
Paddle sells the paid plans as merchant of record: Paddle, not Retiform, is the seller of a paid plan. When you buy a plan you give your payment details to Paddle, not to us, and Paddle decides how it uses them under its own privacy notice, Paddle's privacy policy. Paddle runs the checkout, charges you, collects and pays sales tax and VAT, sends receipts and invoices, and handles refunds. Paddle tells us the buyer's name, address and email address and what was bought, so that we can match the purchase to a tenant and answer questions about it; we see these in Paddle's seller dashboard and do not copy them into the platform. We never receive card numbers. Which Paddle company sells to you depends on where you buy from: Paddle.com Inc. in the United States, Paddle.com (Canada) Ltd in Canada, and Paddle.com Market Limited, of England and Wales, everywhere else.
When a tenant administrator subscribes to a paid plan, we send Paddle only:
- the tenant's identifier;
- a reference for that checkout;
- the paying administrator's email address, which Paddle uses to send receipts;
- the plan and billing period chosen;
- the internet address the request comes from, so that Paddle can tell us its country (see Where you are buying from below).
Paddle tells us what happens to the subscription: that it started, renewed, changed plan, is overdue or ended. We keep a record linking the tenant to its account and subscription at Paddle, the plan, period and status, and, for each message from Paddle, its identifier, type and time and what we changed because of it. We keep no card or bank details and no billing address. Each message from Paddle is reduced to that record once it has been applied, and within 7 days at most.
Where you are buying from. We do not sell paid plans in every country. So that checkout can tell whether we sell in yours, we send Paddle the internet address your request comes from, and Paddle tells us the country. We do not keep the address. We keep the country of the purchase, as a two-letter code, with the record of the subscription.
Changes to a tenant's plan or subscription are written to the tenant's audit log.
Messages we send
Sign-in codes, invitations to a tenant, warnings when your tenant nears or reaches a limit, and warnings before a trial tenant is deleted for inactivity. We also email you at least 30 days before the trial ends, and before a material change to this notice or to the terms takes effect.
In a trial tenant's first two weeks we may send its administrators up to three getting-started emails, each at most once, when the tenant has not yet connected an agent, uploaded a document or received a first answer with its sources. Each says what the next step is and nothing else, and has a link that stops the rest.
We send no marketing email.
Once paid plans are open, when a tenant's paid subscription ends, its administrators are emailed that day, after 7 days and after 23 days, before the tenant is deleted (see the terms of service). Paddle sends its own payment emails, such as receipts and notices of a failed payment.
The weekly memory digest is sent only if you turn it on, on the console's Account page. Any member may, and it is off until you do.
- What it contains: for one tenant and one week, how many memory entries were recorded, corrected and accepted, how many of them await review, how many current entries cite a source that has changed, and up to five excerpts of the newest entries. Each excerpt is at most 120 characters, with its writer (an agent's identifier, or "a member") and the day. Its subject line names the tenant and the week. It does not name you or any other member, and it never contains a whole entry, a passage or a document's text.
- When it is not sent: in a week with no activity, or while the tenant is suspended, read-only or being deleted. A tenant administrator can turn it off for the whole tenant.
- Turning it off: from the Account page, or with the link in each digest, which works without signing in.
- What we keep for it: your choice, the tenant's setting with the administrator who made it, and a record that a week's digest was prepared for you, which is kept for 4 weeks and holds none of its content. They are deleted when you leave the tenant or erase your account, and when the tenant's data is erased. The counts and excerpts of a digest stay in our outgoing mail queue for 30 days after it is sent.
How long we keep it
- Your tenant's content and records: until the tenant is deleted, except context usage records, which are deleted after 35 days.
- Inactive tenants: a trial tenant with no activity for 30 days is deleted. Warnings are sent before that, with a reminder to export. A tenant on a paid plan is not deleted for inactivity.
- Deleting a tenant: deletion can be cancelled for 72 hours. Erasure then completes within 24 hours. A deletion record, kept apart from the data, reports the tenant as erased. The billing records and the records of sanctions checks described below are the exceptions.
- Backups: database backups and the records used to recover the database to an earlier point in time are kept for 7 days. Data that has been erased or deleted is gone from them within 7 days.
- Billing records, once paid plans are open: kept for 7 years after the tenant's last transaction, for tax obligations. This applies after the tenant is deleted too. They hold Paddle's identifiers for the buyer's account and for the subscription, the plan, its status and the country of each purchase. They hold no name, address or payment details: only Paddle can tell from its identifier who the buyer was.
- Access requests, the exit survey and support messages: as stated in their sections above.
- Sanctions checks: United States law forbids us to supply the service to some people and places, so we check the names of the people and organisations we invite or sell to against the United States government's published lists. We keep a record of each check (the date, the name checked and the result) for 10 years, as that law requires. The record is kept apart from the service, and erasing your account or your tenant does not remove it.
Your choices
- Export. A tenant administrator can export the tenant's data from the console. The archive lists what it holds, with a digest of each file.
- Delete. A tenant administrator can delete the tenant from the console.
- Erase your account. Any member can erase their own account from the console's Account page, as described under "Your account in the trial".
- Ask. For anything else about your data, including a copy of what we hold about you or a correction, write to support@retiform.ai.
Where the trial is offered
The trial is offered only to people located in the United States. The access request asks which country you are in, and we do not invite people located anywhere else. We do not direct the trial to people in the European Economic Area, the United Kingdom or Switzerland. Your data is processed in the United States, by us and by the companies listed above.
If you are a member and move outside the United States, tell us at support@retiform.ai.
Wherever you live, you can ask us for a copy of the personal data we hold about you, to correct it and to delete it. The console's export and erasure cover most of this. For the rest, write to support@retiform.ai.
Your privacy rights under United States state laws
- What we collect. The categories this notice describes above: what you send in an access request, your email address and an account identifier, records of your use of the service (sign-in times, the audit trail and the usage records), your answers to the exit survey, and messages you send to support.
- Who we share it with. Only the companies listed under "Other companies that process your data", which provide sign-in, hosting, email delivery and the model the service's search depends on.
- We do not sell personal information. If you want to tell us not to sell yours in future, write to support@retiform.ai.
- Reviewing and correcting your information. To see what we hold about you, or to have it corrected, write to support@retiform.ai.
- Tracking. We do not track what you do on other websites or services, so there is nothing for a browser's "Do Not Track" signal to change. No advertising or analytics company collects information about your activity over time or across websites when you use this site or the service. The status page is hosted by another company and is described under "What this site collects".
- Making a request. We will not treat you differently for making a request under this section.
Changes to this notice
We change this notice when what we do changes. The review date at the foot of this page is the date from which this version applies. We email every member at least 30 days before a material change takes effect.