Privacy
Privacy notice
What personal data this website and the hosted demo receive, why we have it, who else sees it, and how long we keep it.
Last updated 7 October 2026
Who is responsible
This website and the hosted demo at app.aktaro.ai are run under the Aktaro name from Zug, Switzerland, and we are responsible for the personal data described here. For anything about this notice or your data, write to hello@aktaro.ai.
In short
This website sets no cookies and stores nothing in your browser. It runs no analytics, tracking or advertising, its fonts, images and scripts come from aktaro.ai itself, and it loads nothing from other sites. That is why there is no cookie banner. Most of that is held in place by a test in our source tree, which fails if a page starts reaching another site, if either server sets a cookie, or if the one script this site loads gains a second.
Aktaro is sold only through partners, so nothing is sold on this site. We receive personal data in three ways only: the technical data every page request carries, the partner enquiry you send us, and your use of the demo if we give you an account.
Visiting the website
When your browser requests a page, it sends your IP address, the address of the page, the time and technical details such as the browser type. We need this to deliver the page and to protect the site against attacks. The site runs on our own server in Switzerland and is delivered through Cloudflare, Inc., which processes this data on our behalf under a data processing agreement. Our own server records which pages were requested and when, but not the address they were requested from. Legal basis: our legitimate interest in a working, secure website (Art. 6(1)(f) GDPR).
Writing to us
The form on this site is for companies that want to become Aktaro partners or distributors. When you press Send, the form posts your message to our own server in Switzerland: it does not go through your mail app, and nothing sits between your browser and us except Cloudflare, which delivers the site.
We store what you typed — your name, email address, company and message — together with a reference number and the time, the IP address the message was sent from, the country Cloudflare works out from that address, the browser identification string your browser sends, and a measurement of how long the form was open, which is one of the checks that tells a person from a bot. We then send ourselves the whole of that by email, which reaches us through Cloudflare Email Routing and our own email provider, so those two hold a copy as well.
We keep the IP address and the browser string because together they are what lets us deal with abuse of a public form. Legal basis: steps you ask for before a possible contract (Art. 6(1)(b) GDPR) and our legitimate interest in answering business enquiries and keeping the form usable (Art. 6(1)(f) GDPR).
If you write to us as a prospective customer rather than a partner, we tell you which partner serves your region. We pass your enquiry to a partner only if you explicitly agree, after we tell you who the partner is and where it is based. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.
Product news, if you ask for it
The form has one optional tick box for occasional product news. It is off unless you tick it, ticking it is the only thing that puts you on that list, and we record when you ticked it so we can show you later what you agreed to. Nothing else you send us is used to market to you. Legal basis: your consent (Art. 6(1)(a) GDPR). To come off the list, write to hello@aktaro.ai and we will remove you; withdrawing does not affect anything we sent before. Be aware that the record of your consent lives inside the enquiry you sent, so coming off the list removes you from it but does not by itself delete the enquiry — ask us to delete that too and we will.
Using the demo
Demo accounts are issued to partners and to companies applying to become one. The demo is a different thing from this website, and this section is the only part of this notice where cookies, browser storage and stored content come into it.
Your account
We store a user name, your password as a salted scrypt hash, and your sign-in sessions as hashed tokens. One cookie, pb_session, keeps you signed in. It is strictly necessary, carries no tracking data, and expires after seven days or when you sign out. Your IP address is used to limit repeated sign-in, sign-up, invite, password-recovery and assistant-registration attempts. It is held in the running process's memory only and never written to disk by the demo — but to be exact rather than flattering: an address stops counting against you after an hour, while the entry holding it is only cleared the next time that same address appears, so in practice it sits in memory until the service restarts.
What the demo keeps in your browser
Unlike this website, the demo does store things in your browser's local storage, under keys tied to your user name: your pane and graph-legend layout, a handful of dismissed prompts, and your chat history — your questions, the answers you were given, and the pages each answer cited, up to fifty turns per conversation, for every conversation you have had. Nothing expires. Clearing your browser storage deletes it; signing out does not, so on a shared computer it is the browser you have to clear.
We do not upload that archive. But it is not sealed off from us either: when you ask a follow-up, your browser sends the last dozen turns of that conversation back to us, and on to the model provider, so the answer follows from what came before.
What the demo keeps on our server
Chats you have in the demo's own chat panel are not written to our database at all — they exist on our server only for as long as it takes to answer, and the copy that persists is the one in your browser described above.
What is stored is the content you put in: documents you upload or capture, including their full extracted text and, for scans, the text recognised from each page; and the notes, memos, projects, remembered facts and filed transcripts that you or an assistant you connect create.
We also keep a usage record, so we can see what the demo costs and diagnose faults. It covers the calls an assistant you connect makes to us over MCP, and it holds each call's arguments as they were sent — which can include the text you searched for, a note or memo you filed, or a transcript you uploaded. Working in the demo's own interface does not write to it. It is readable only by the account that administers the deployment, and it is capped by size rather than by age, so rows are dropped when the log grows rather than when they get old.
Who at Aktaro, and at your partner, can see it
This is the part most worth reading. Demo accounts sit in a tree: whoever issued your account sits above it, and we sit above them. Anything you do not mark Private can be read by the account that issued yours — typically the partner you are talking to — and by every account above that, including ours. That is how a shared demo collection is meant to work, but it is not what most people assume, so mark anything you would not show them as Private before you put it in.
Private means the owner alone: not the partner who issued your account, not us. The one exception is a deliberate, recorded override that an operator with full access can switch on to read private material, which writes an audit row naming who looked and at what. An administrator above you can also reset your password and disable your account, which starts the 30 day deletion described under How long we keep it. Being above you does not by itself let them delete what you wrote; that is ours to do, and we can also delete a disabled account and everything it holds at once rather than waiting out the 30 days.
Where your questions go
Answering a question sends it to our model provider twice. The first call decides which of your pages are relevant, and to do that it sends your question together with a one-line index of every page your account can read — each page's title and the opening of its text. The second call sends your question, the pages chosen to answer it, and up to the last twelve turns of the conversation, and the provider writes the answer.
The provider does more than answer questions. Everything you upload or capture is sent to it to be summarised into the demo's wiki; scans are sent to it page by page to be read; filing a transcript can send its text to be turned into remembered facts; looking for papers sends it your library to build search queries from; and if you switch on a periodic briefing, a scheduled job sends it your newly added pages without you asking for anything at that moment. In short, assume everything you put into the demo reaches our model provider. Please do not enter confidential information.
That provider is OpenAI today. Which endpoint is used is an operational setting an administrator can change from the admin console without a release, and a change moves this traffic to whoever is configured; we update this notice when it changes.
If you connect your own assistant, such as ChatGPT or Claude, that conversation happens in the assistant, and its provider handles it under its own terms — we receive only the calls the assistant makes to us.
One thing worth saying plainly, because a demo account is easy to fill quickly: the documents, emails and transcripts people upload usually contain other people's personal data. We process whatever you put in on your instruction, as part of running the demo, and we have no way to tell whose it is or to answer those people directly. If you are putting in real material rather than samples, that is your decision to make as the one responsible for it — and it is a good reason to use samples.
Legal basis for all of the above: providing the demo you asked for (Art. 6(1)(b) GDPR) and our legitimate interest in keeping it secure and affordable (Art. 6(1)(f) GDPR).
Who else receives your data
Service providers who work on our instructions under data processing agreements: Cloudflare, Inc., which delivers both sites and receives our email; our email provider, which keeps our mailbox; and OpenAI, which writes the answers in the demo. A partner receives your data only with your consent. We do not sell personal data and we do not use it for advertising, and there is no analytics, telemetry or error-reporting service anywhere in either site.
Two things in the demo reach other sites. Looking for a paper sends search terms to arXiv, Crossref or Springer — terms you typed, or terms built from the papers already in the library — and uploading or capturing a document that carries a DOI makes us ask Crossref about it; asking the demo to capture a web page makes our server fetch that page, which tells the site in question that our server asked for it. None of them is told who you are, and the request carries our server's address, not yours.
Transfers abroad
Cloudflare and OpenAI also process data in the United States. Cloudflare is certified under the Data Privacy Framework between the United States and the EU, and under its Swiss counterpart. OpenAI's data processing addendum relies on the EU standard contractual clauses. Where our email provider processes data outside Switzerland and the EU, the transfer rests on the Data Privacy Framework or on the standard contractual clauses. A partner outside Switzerland and the EU receives your enquiry only with your explicit consent, given after we tell you where it is based. The bibliographic services above — arXiv and Crossref in the United States, Springer in Germany — receive only a search term or a DOI, at your request, which is the basis for that. If an administrator points the demo at a different model provider, that traffic goes wherever the new provider processes it.
Backups
The demo's database is copied to a dated snapshot every night, and the files uploaded to it are mirrored alongside. A snapshot is written as a fresh copy of the database rather than an image of the file as it sits on disk, so it holds what the database contains at the moment it is taken and not the space that earlier deletions released. We keep the last fourteen snapshots, and the mirror keeps a file only while one of those snapshots or the live database still refers to it. Something deleted from the live demo, an account included, therefore leaves the backups within fourteen nightly runs, without anyone having to go and find it.
If we restore a snapshot, the deletions made after it was taken are applied again before the demo reopens, from a list kept beside the database and a second copy kept in the backup directory. The demo refuses to start rather than come back with a deleted account in it.
Both the snapshots and the mirror are on the same machine as the demo, and that machine is itself backed up by macOS Time Machine, which copies the database, the uploaded files and those snapshots into a history of its own. Deleting something removes it from the live demo at once, and from our snapshots on the cycle above. It does not remove it from that system history, which macOS writes and prunes on its own schedule rather than on ours, so a copy can persist there after it has left everything described above. We would rather say so here than describe a cycle that only covers the backups we control.
How long we keep it
Partner enquiries, including the IP address and browser string they carry: up to 12 months after our last exchange, unless a partnership follows; then for as long as that partnership and statutory retention periods require. There is no automatic deletion behind that — it is a review we carry out, so if you want your enquiry gone sooner, ask and it goes.
Demo accounts and their content: when your access ends we disable your account, and 30 days later it is deleted automatically, with everything it holds. That is your documents and the text extracted or recognised from them, your notes, memos, projects, remembered facts and filed transcripts, your sign-in sessions, the assistants you connected, the access you gave or were given, the invitation codes issued to you or by you, and the usage records of your calls. A job checks every hour, so the deletion happens on the day it falls due rather than at a particular minute. Enabling an account again stops the clock, and a fresh 30 days only begins if it is disabled again. Ask us and we delete the account at once instead, without waiting. The 30 days is a setting of this deployment rather than something built into the software, and it is the setting app.aktaro.ai runs with; an Aktaro installation a customer runs for themselves deletes nothing automatically unless its operator chose to.
Four things deliberately survive that deletion, and they are better read here than discovered later. Where the same file is still held by another document in the demo, because somebody else uploaded an identical copy, that file and the text recognised from it stay with the document that still refers to them. What other accounts wrote themselves stays theirs, even where it cites or quotes a page of yours, so a note another person filed keeps its quotation after your page is gone. Access you arranged between two other accounts stays as it was, recorded against the deletion rather than against you, because withdrawing it would change what those two can read and that is not yours to decide on the way out. And we keep a short record that the account was deleted, holding its user name, when it happened, who or what did it and how much was removed, for as long as the demo runs; it holds none of the content. Records of administrative actions taken on the account, or by it, are kept as the record of how the demo was administered, with the identifiers of the account, and the names attached to them, replaced by a reference to that deletion record.
What deleting means on the disk, since the word carries more weight than it can always bear. The rows and the uploaded files go at once, and from then on the database overwrites the space a deleted row occupied instead of merely releasing it for reuse. The overwriting is not always finished the moment you press the button: changes are written first to a journal file beside the database and folded back into it at a checkpoint, and a checkpoint can be refused while something else is reading, in which case the next hourly run attends to it. Space released before this mechanism existed was cleared by rewriting the database once, when the mechanism was introduced. So the account and its content leave the demo immediately, and the last bytes leave the disk shortly afterwards rather than instantly.
Two limits on all of that. What was sent to our model provider to answer your questions is covered under Where your questions go, and deleting your account here does not reach the copies that provider holds under its own terms. And the chat history the demo keeps in your browser is on your device, not ours: it stays until you clear it.
Consent to product news: until you withdraw it. Our web server's page records: they carry no address, so they identify nobody, and we keep them as long as they are useful for diagnosing faults.
Your rights
You can ask for access to your personal data and a copy of it, for its correction, deletion or restriction, and for a portable copy. You can object at any time to processing based on our legitimate interest, and withdraw consent at any time without affecting what was done before. Write to hello@aktaro.ai. You can also complain to a data protection authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU the authority where you live or work.
Other points
You do not have to give us personal data, but without it we cannot answer you or open a demo account. We make no automated decisions that have any legal or similarly significant effect on you, and nothing here is used to score, rank or profile you as a person.
One qualification, because a blanket "we build no profiles" would not be honest about what the product does: the demo has a memory. It draws short statements out of the material you give it — transcripts especially — and keeps them as remembered facts, which can be statements about you or about the people in that material, and which the demo then uses to answer later questions. That is the feature working as intended, it is confined to your account and to those who can read it under the rules above, and you can see and delete those facts. It is still worth knowing before you file a real conversation.
This notice follows the Swiss Federal Act on Data Protection and, where it applies, the EU General Data Protection Regulation. We update it when the website or the demo changes; the date at the top shows the current version.