Privacy Policy

Last updated November 20, 2026

This policy explains what personal data HUMANOOP collects, why, who processes it on our behalf and the choices you have. HUMANOOP is operated by AETHON Engineering Μονοπρόσωπη ΙΚΕ (“AETHON Engineering”, “we”, “us”), whose details are at the end of this page.

Our role

For your account, your billing and your use of this website, we decide how personal data is used: we are the controller.

For the content you put into HUMANOOP (your documents, the data read from them, your chats and your Knowledge Base files), you or your organisation decide how it is used, and we process it only to provide the service to you: we are your processor. If that content holds other people’s personal data and they ask about it, their request goes to you first, and we help you answer it.

What we collect

  • Account details: your name, your email address, a one-way hash of your password (never the password itself), your language and the time you accepted the Terms of Service. If you sign in with Google: the name, email address and account identifier of your Google account.
  • Content in your Hub (the workspace your account belongs to): the documents you upload and the data read from them, your corrections and approvals, exports, chat messages, the images and files you add to Chat Workspaces and Knowledge Bases (including the websites and Google Drive folders you link), Help Desk tickets and feedback.
  • People you invite: the email addresses of the team members you add and of the people you share results or a chat with. We use them to send the invitation and a one-time code.
  • Billing details: your subscriptions, your invoices and the date and amount of your payments. Card details are typed into Stripe’s payment form and stay with Stripe: we never see or store card numbers.
  • Technical data: your IP address, sign-in and usage events, the audit trail of reviews and approvals, and server logs, which we need to run and secure the service.
  • Analytics data, only if you accept analytics cookies: how the pages of the site are used, and whether a visit ends in a sign-up or a first payment (with the payment’s amount and reference), as recorded by Google Analytics.
  • Advertising data, only if you accept advertising cookies: whether your visit started from one of our ads (the ad’s click identifier) and whether it ended in a sign-up or a first payment, as recorded by LinkedIn and, once it is switched on, Google Ads.
  • Campaign labels: when you create an account, we keep with it the campaign labels (UTM tags) of the link you arrived by if you accepted analytics or advertising cookies, and the ad’s click identifier only if you accepted advertising cookies. If you accepted neither, we keep none of them. Together with the date and amount of your first payment, they let us count which campaigns bring customers.

Why we use it

  • To provide the service you signed up for: reading your documents, review, answering your chats, billing and support. This is necessary to perform our contract with you.
  • To send account emails: address verification, password resets, invitations, one-time codes and the notifications you choose in Settings → Notifications. This is part of providing the service.
  • To keep the service secure and reliable: preventing abuse, applying rate limits and investigating errors. This is our legitimate interest in a safe, working service.
  • To keep the records the law requires, such as invoices.
  • To measure how the site is used, only with your consent, which you can withdraw at any time in the cookie settings.
  • To measure which of our ads lead to sign-ups and first payments, only with your consent, which you can withdraw at any time in the cookie settings. We do not use it to show you personalised ads.

We do not sell personal data, and we do not use your documents, the data read from them or your chats to train AI models.

If you speak a message in a Chat Workspace instead of typing it, the recording is transcribed into text on our own servers and then discarded: we do not store your voice, only the text you choose to send.

Who processes it for us

We use the following providers to run HUMANOOP. Each one processes data only as far as its part of the service needs:

  • DigitalOcean: hosting of the application, of the files you upload, of our database backups and of our AI gateway (the service that passes each AI request to our AI servers), in Frankfurt, Germany. Visits reach it through the network of Cloudflare, which DigitalOcean uses in front of its hosting.
  • Neon: the managed database, in Frankfurt, Germany. It also holds our AI gateway’s request log, which records only technical details of each AI request (its time, size, duration and outcome, and the number of the Hub it came from), never your documents, the data read from them or your messages, and keeps them for 90 days.
  • Upstash: the queue that runs background jobs, in Frankfurt, Germany.
  • GitHub: runs our nightly database backup. The backup is created on a GitHub server, which may be outside the European Economic Area, written to our storage in Frankfurt and not kept at GitHub.
  • Our own AI servers, not a provider: the AI models that read your documents, answer your chats, read the images in your Knowledge Bases, transcribe voice input and index your Knowledge Bases run on computers we own, in our office in Athens, Greece, reached through our AI gateway. Your documents, the data read from them and your chats are not sent to third-party AI services, except to Google’s Gemini API as a backup, described next.
  • Google (Gemini API, Google LLC), as a backup only: when our own AI servers fail or cannot be reached (for example during an outage), our AI gateway may send that one request to Google’s Gemini API instead, so that your document is still read or your chat still answered. Google then receives what that request contains: the document page image and the fields to read, or the chat message with its conversation, any attached images and Knowledge Base excerpts, or the Knowledge Base image being read. Voice input and Knowledge Base indexing never use it. A Chat Workspace with “Keep my files private” switched on never uses it either: its chats and its Knowledge Base stay on our own servers. Document reading in Data Entry has no such switch. We use Google’s paid service, under which Google does not use the content to train or improve its models and keeps it only for a limited time to detect abuse. Google may process it outside the European Economic Area (see below). Our AI gateway’s request log records which requests were answered this way.
  • Stripe (Stripe Payments Europe, Limited, Ireland): payments, subscriptions, invoices and the card form, with its fraud checks.
  • Google: Sign in with Google (its button loads on the sign-up and sign-in pages; Google receives your account details only if you use it), reCAPTCHA bot protection on the sign-up and sign-in pages, Google Drive (if you link a shared Drive folder to an operation or a Knowledge Base, we read its files from Google), Google Fonts (the site’s typefaces, loaded from Google when a page opens, which shows Google your IP address), Google Analytics (if you accept analytics cookies) and Google Ads (not switched on yet). The last two are described below.
  • LinkedIn (LinkedIn Ireland Unlimited Company): the LinkedIn Insight Tag, only if you accept advertising cookies (described below).
  • Namecheap (Namecheap, Inc., United States): delivery of the emails we send, and the mailbox that receives what you write to [email protected].
  • Tavily (AlphaAI Technologies Inc., United States), only in a Chat Workspace where “Search the web” is offered and switched on: when a question needs current information from the internet, our AI writes one short search phrase from your question and sends it to Tavily’s web search, which returns public web pages for the answer to cite. Tavily receives only that phrase: nothing that identifies you, your account or your Hub, and none of your files, Knowledge Base excerpts or the rest of the conversation. Because the phrase is written from your question, it can contain words you typed, so leave out personal details you do not want searched. Tavily is not one of our processors: it handles the phrase in the United States under its own terms and privacy policy (tavily.com/privacy), which let it keep the phrase and use it to improve its services, including to train AI models. A Chat Workspace set to keep its files private never searches the web, shared chats never do, and search stays off until someone turns it on in the workspace’s settings.
  • Sentry (Functional Software, Inc.): error monitoring, in its EU region in Frankfurt, Germany. When the application or the website hits an error, Sentry receives a technical report (what failed and where, the page or route, and an internal number for your account, not your name or email address), never the contents of your requests, email addresses, document text or chat messages.
  • Have I Been Pwned: when you choose a password, we check it against this public list of passwords found in data breaches. Only the first five characters of a scrambled (hashed) form of the password are sent, never the password itself, your name or your email address.

Google Analytics, only if you accept analytics cookies: Google (Google Ireland Limited) records the pages you visit on our site and, when a visit ends in a sign-up or a first payment, the fact that it happened and, for a payment, its amount and reference; never your name, email address or anything you put into HUMANOOP.

LinkedIn, only if you accept advertising cookies: the LinkedIn Insight Tag (LinkedIn Ireland Unlimited Company) records the pages you visit on our site, and when a visit that started from one of our LinkedIn ads ends in a sign-up or a first payment, the fact that it happened and, for a payment, its amount and reference; never your name, email address or anything you put into HUMANOOP. LinkedIn uses this data under its own privacy policy (linkedin.com/legal/privacy-policy).

Google Ads is not switched on yet. Once it is, and only if you accept advertising cookies: when a visit that started from one of our ads ends in a sign-up, Google Ads (Google Ireland Limited) receives the ad’s click identifier and the fact that a sign-up happened, never your name, email address or anything you put into HUMANOOP. Google uses this data under its own privacy policy (policies.google.com/privacy) and may combine it with what it knows from its own services. We ask Google not to use it for personalised advertising.

If we have agreed with your organisation to connect your Hub to an AI model that it runs itself, your documents and chats are read by that model instead of ours.

Several of these providers are United States companies or use servers outside the European Economic Area (EEA): DigitalOcean, Cloudflare, Neon, Upstash, GitHub, Google, Stripe, LinkedIn, Namecheap and Sentry. Where personal data leaves the EEA, the transfer relies on the safeguards in their data processing terms: the EU–US Data Privacy Framework for providers certified under it, or the European Commission’s standard contractual clauses. Tavily is the exception: we have no data processing agreement or standard contractual clauses with it. A search phrase goes to Tavily in the United States only because a web search was asked for, in a Chat Workspace where someone switched “Search the web” on. If you do not want that, leave it off.

How long we keep it

Your account and the content of your Hub stay until you delete them or delete your account. Deleting your account (Settings → General → Delete account) permanently removes every Hub you own with its documents, results, chats and files, cancels your subscriptions, removes your payment profile at Stripe and deletes your account, with the campaign labels kept with it. In Hubs you joined but do not own, your private chats are deleted and your name is removed from the review history.

An archived Data Entry operation or Chat Workspace is kept, and can be restored, until the end of its current billing cycle (30 days if it has no subscription). It is then permanently deleted with everything in it (for an operation its documents, results, review history, exports and shared links; for a Chat Workspace its sessions, shared links and Knowledge Base), and cannot be recovered. Its shared links stop working when it is archived. A chat you delete is removed at once.

A link you share to results or to a chat expires after 14 days.

Deleted data leaves our backups later: the database’s recovery copies after 7 days, and our nightly backups after at most 8 weeks.

Invoices and payment records are kept by our payment provider for as long as tax law requires.

Your rights

Under the GDPR you can ask to access, correct, export or delete your personal data, object to its processing or ask us to restrict it, and withdraw a consent at any time. You can do most of this yourself: edit your profile in Settings, export the results of each operation and delete your account. For anything else, write to [email protected]; we answer within one month.

If you believe we handle your data unlawfully, you can complain to a data protection authority; in Greece, the Hellenic Data Protection Authority (www.dpa.gr).

Security

Traffic to HUMANOOP is encrypted (HTTPS). Passwords are stored only as one-way hashes, and changing your password signs you out everywhere. Our AI servers accept only encrypted, mutually authenticated connections from our AI gateway. Every Hub’s data is isolated from every other Hub’s.

Changes

We update this policy when our practices change. The date at the top shows the current version.