Privacy
What personal data the Hesimesi beta keeps, why, for how long, and who else receives it. We wrote this page to follow the EU's data protection law (GDPR), with the rights Türkiye's law adds. A lawyer has not reviewed it yet. That review comes before public launch, which means when sign-up opens without our approval, the first customer pays, or a company is registered, whichever comes first.
Last updated 21 November 2026
In short
- Your files and saved details are sealed on your device, and we can't open them, as long as the code our website sends to your browser is honest; our security page explains this limit and the others. The exception is a file you lock only to a date: once that date passes, anyone who holds it, us included, can open it. We can read what is around them: your email address, file names, labels, your sign-in log and the other things listed below.
- We record each sign-in with its IP address, and keep those records with no fixed end date, also after an account is deleted.
- Our providers work in Germany, the United States and several other countries. We, the operator, read the readable data from where we work, a country outside the EU and the European Economic Area with no EU adequacy decision; no safeguard covers that yet.
- We have added no analytics, tracking or advertising, and we don't sell your data.
- Write to support@hesimesi.com about anything on this page.
Who we are
Hesimesi is a service in an invite-only beta, run without a registered company yet. Anyone can sign up, but an account opens only when we approve it by hand; that is what we mean by invite-only. Hesimesi is responsible for the personal data this page describes.
Write to support@hesimesi.com about anything on this page. To report a security problem, write to security@hesimesi.com.
We have not appointed a representative in the European Union. When a company is registered, it will take over responsibility for your data, and we will email every account.
What we can't see, and what we can
Your files and saved details are sealed on your device before they reach us, and we cannot open them. This rests on the code our website sends to your browser; our security page explains that limit. The exception is a file you lock only to a date: once that date passes, anyone who holds it, us included, can open it.
Everything around your sealed contents is readable to us. That includes:
- your account email, and your sign-in log with IP addresses and emails;
- file and document names (a file keeps its original name), document types and sizes, labels, field names, field types and access levels;
- destination addresses, the domains in your rules, agent and sidecar names (a sidecar is the helper program you run to deliver values), and organisation and app names;
- share-link notes. Anyone holding a live share link also sees the file's name, size and note, and when the link expires;
- the recipient your agent names for a send;
- for each site request: which site asked, which kinds of detail it asked for, the outcome, and the contact hint the site sent (the first letter of your email and its domain);
- the activity log, contact-form messages with their IP address, and the push addresses of your approval devices;
- the readable header of each stored file, which shows the kinds of keys that can open it, whether recovery shares exist and how many are needed, and, for a time-locked file, when it opens.
What we keep, why, and for how long
Each row says what we keep, why, the legal basis we rely on, how we get it, and how long we keep it.
The legal bases mean this. Contract: we need it to give you the service you signed up for. Legitimate interest: we need it for a reason such as security, weighed against your privacy. Consent: you chose it and can withdraw it. Legal obligation: a law requires it.
Account
- What
- Your email address, your password (kept only as a one-way hash), your passkeys (only their public half, which can't sign you in), whether your account is approved, your plan, and any plan upgrade you ask for
- Why
- To run your account
- Legal basis
- Contract
- How collected
- From you, when you sign up and in Settings
- How long
- Until your account is deleted
Sign-in log
- What
- The time, the method (password, sign-in link, passkey or sign-up), the outcome (success, failed, or refused because the account is suspended), your IP address, your account's email and whether it had been confirmed
- Why
- Security, stopping abuse, and answering lawful requests
- Legal basis
- Legitimate interest in security and abuse prevention; legal obligation where a law requires it
- How collected
- Automatically, at each sign-in and at each wrong password our rate limits let through. A wrong password typed for an address that has no account keeps the time, method and IP address, but no email
- How long
- No fixed end date yet, and kept after your account is deleted, so that we can still answer a lawful request or look into abuse afterwards. We will set a fixed period before public launch
Session
- What
- A random code in a cookie, and on our side a record of which account it belongs to and when it started and ends. No IP address or browser details
- Why
- Keep you signed in
- Legal basis
- Contract (strictly necessary). If you tick “Keep me signed in”, consent
- How collected
- Automatically, when you sign in
- How long
- Without the box ticked, the session ends after at most 12 hours, and the cookie usually goes when you close the browser (a browser that restores your tabs may keep it). With it ticked, both last 30 days. The record is deleted within about 6 hours after the session ends, or about 7 days after you sign out
Known device
- What
- A random code in a cookie, and on our side a record of it. No IP address or browser details
- Why
- Limit password guessing
- Legal basis
- Legitimate interest in security
- How collected
- Automatically, after a correct password from a browser not yet known for your account
- How long
- 180 days after it was last used
Suspension record
- What
- The reason, the admin who acted, and when the suspension started and was lifted
- Why
- Stop abuse; answer lawful requests
- Legal basis
- Legitimate interest in preventing abuse; legal obligation where a law requires it
- How collected
- By an admin
- How long
- Until your account is deleted
Our record of admin actions on your account
- What
- What an admin did: approval, plan and feature changes, suspension and its lifting, and each reading of your sign-in log
- Why
- Accountability for what we do
- Legal basis
- Legitimate interest in accountability
- How collected
- Automatically, when an admin acts
- How long
- No fixed end date; kept after your account is deleted
Hosting request logs
- What
- At the web host: your IP address, the address of the page you asked for and your browser type, for every page request. At the server host: a sample of requests with your IP address, and failed requests with the address asked for but no IP address
- Why
- Deliver and secure the site
- Legal basis
- Legitimate interest in running a secure service
- How collected
- Automatically, by the web host and the server host
- How long
- As each host keeps them; see “Backups, logs and email copies”
Activity log
- What
- What you and your agents did in your vault, including names, labels, the host names of sites involved and send recipients
- Why
- Your own record of what happened; security
- Legal basis
- Legitimate interest in security and in giving you that record
- How collected
- Automatically, when you or your agents act
- How long
- No fixed end date; kept after your account is deleted, because removing an entry would break its chain
Names and settings
- What
- File and document names, labels, field names, destinations, rules, and agent and sidecar names
- Why
- Run the features you use
- Legal basis
- Contract
- How collected
- From you
- How long
- File and document names, labels, field names, destinations and rules: until you delete them or your account. Agent and sidecar names: until your account is deleted, because revoking an agent or a sidecar stops it but keeps its name
Sealed files and saved details
- What
- The sealed contents, which we cannot open, except a file locked only to a date once that date has passed
- Why
- Store them for you
- Legal basis
- Contract
- How collected
- From you
- How long
- Until you delete them or your account; see also “Backups, logs and email copies”
Agent requests
- What
- What your agent asks to do, including the recipient it names for a send
- Why
- Carry out what your agent asks
- Legal basis
- Contract
- How collected
- From your agent
- How long
- Deleted about 24 hours after they are decided or expire; the recipient also stays in the activity log
Site requests
- What
- Which site asked, which kinds of detail it asked for, the outcome, the site's receipt, the site's contact hint, and your passkey approval (which passkey approved it, with its signature). After you deny a request, or when a site's redemption doesn't match its request, a pause that stops that agent asking that site again for a while
- Why
- Carry out a site's request for your details
- Legal basis
- Contract
- How collected
- From your agent, the site and your approval
- How long
- 30 days after they end. A pause lasts 1 hour after a denial, and 24 hours after a mismatch
Deliveries
- What
- Which detail goes to which destination, with its status and times; the value itself travels sealed
- Why
- Deliver a value you approved or your rules allowed
- Legal basis
- Contract
- How collected
- From your rules and approvals
- How long
- About 30 days after they end
Share links
- What
- Your note, the expiry and the download count; we keep only a fingerprint of the link itself. A link made for your agent's send is also held in full until your agent first collects it, usually within seconds
- Why
- Let someone download a file
- Legal basis
- Contract
- How collected
- From you
- How long
- Until the file or your account is deleted. The full link made for a send goes when your agent collects it, or at the latest with the agent request
Organisations and API keys
- What
- Organisation and app names, API keys (we keep only a fingerprint), daily usage counts, and the email address an organisation's owner invite was sent to
- Why
- Run the API product
- Legal basis
- Contract
- How collected
- From us when we set up an organisation, and from you and your apps
- How long
- Until your account is deleted; an organisation goes with its owner's account. An organisation we set up whose invited owner has not accepted yet has no owner, so it stays, with the email address its invite was sent to, until we remove it. Revoking an API key stops it but keeps its fingerprint. Daily usage counts are kept while the organisation exists
Push notifications
- What
- The push address your browser gives us for your approval device
- Why
- Wake your approval device when a request is waiting
- Legal basis
- Consent: you turn notifications on
- How collected
- From your browser
- How long
- Deleted when you turn them off, or with the record of the session that turned them on (up to about 7 days after it ends)
Contact form
- What
- Your name, email, company, company size and message, and the IP address it came from (an IPv6 address is shortened to its network part)
- Why
- Answer you; stop abuse of the form (the IP address)
- Legal basis
- Legitimate interest in answering an enquiry and in preventing abuse
- How collected
- From you; the IP address automatically
- How long
- 12 months
Emails we send
- What
- Your email address and the message, including any one-time link in it. For each one-time link we email, we keep only a fingerprint of its secret, never the link itself. We also email ourselves when a new account signs up, naming its email
- Why
- Send sign-in links, confirmations, approval and security notices; review new accounts
- Legal basis
- Contract; legitimate interest in security notices and in reviewing new accounts
- How collected
- Automatically
- How long
- A sign-in or confirmation link's fingerprint is deleted after the link expires, and a passkey link's with the session record it belongs to. A new passkey's “this wasn't me” link keeps its fingerprint as long as the passkey, and an invite as long as the invitation. For the messages, see “Backups, logs and email copies”
Storage in your browser
- What
- Interface preferences, approval-app settings, the fingerprint of each delivery the approval app sealed (so it can check the site's receipt), the sealed device key, a passkey sign-in cookie, and an email-confirmation code held in one tab while you sign in. If you use our browser extension, it also holds the values you unlock and your account email in the browser's memory, and keeps its theme setting
- Why
- Make the site and the extension work as you set them
- Legal basis
- Strictly necessary, or your own setting
- How collected
- In your browser
- How long
- Until you clear it. A delivery's fingerprint is kept 2 days, the passkey cookie lasts 5 minutes, the confirmation code goes when the tab closes, and the extension forgets the values you unlocked when it locks itself (at most 12 hours after you unlock) or the browser closes
About the activity log
Activity-log entries hold names, labels, the host names of sites involved and send recipients.
Some older entries also hold a fingerprint (hash) of an email address. They were written before our change of 20 November 2026, for a failed password sign-in or a sign-in-link request. The fingerprint is of the email typed, even an address that has no account. These entries belong to no account, so no account owner sees them. The fingerprint is made without any secret. So anyone who can read our database (us, or an attacker who breaks in) and already knows an address can find its entries. We keep them because rewriting them would break the chain. Newer entries don't hold the fingerprint.
The log is chained so that casual changes show, but someone with write access to our database could forge it.
Who receives your data
We use the outside providers below. We describe them by type and country; email support@hesimesi.com and we'll tell you their names.
Server host, a US company
- What it receives
- Everything our service handles. It runs our service, our database, our log store, the demo visa site and our test tools. It receives each request to our service, with your IP address, the address you asked for and your browser type. It holds the database, with all the readable data on this page and your sealed saved details. Sealed files pass through it on their way to file storage. It also holds our server logs
- Where it is processed
- The servers that run our service, and our database, are in Frankfurt, Germany. Connections arrive at the host's network point nearest you. Database snapshots, the host's log archive and its records of a sample of requests are in the United States
- Safeguard for transfers out of Europe
- EU-US Data Privacy Framework: the host states that it is certified
File storage, a US company
- What it receives
- Your sealed files and the files attached to your documents, each with its readable header, under random identifiers. No names
- Where it is processed
- Spread across several countries, including the United States
- Safeguard for transfers out of Europe
- Not yet confirmed; our legal review is pending
Web host, a US company
- What it receives
- Requests for our web pages: your IP address, the page address and your browser type. It also answers DNS lookups for the demo visa site's domain
- Where it is processed
- Its server code runs in the United States; pages are delivered through its worldwide network
- Safeguard for transfers out of Europe
- EU-US Data Privacy Framework: the host states that it is certified
Email sender, a US company
- What it receives
- Each recipient's address and the full message, including one-time links
- Where it is processed
- Its records are kept in the United States; mail leaves through Ireland
- Safeguard for transfers out of Europe
- Standard contractual clauses in its data-processing terms, which are in force. It also states that it is certified under the EU-US Data Privacy Framework
Inbound email service, a US company
- What it receives
- Mail you send to support@hesimesi.com or security@hesimesi.com, our replies, and our alert for each new account
- Where it is processed
- Data centres in several countries, including the United States; no region is fixed. For most customers billed in Europe, the Middle East and Africa, ours included, the recipient is its Irish company
- Safeguard for transfers out of Europe
- EU-US Data Privacy Framework, under which it states that it is certified, and standard contractual clauses in the data-processing terms accepted for our mail account on 20 November 2026
DNS provider for our domain
- What it receives
- Lookups of our domain names, which come from the service your device uses to look up web addresses (usually your internet provider's). It does not carry traffic to our site or our service
- Where it is processed
- Operated from several countries; its records are kept mainly in the United States and the European Economic Area
- Safeguard for transfers out of Europe
- EU-US Data Privacy Framework, under which it states that it is certified, and standard contractual clauses in its terms
Your browser's push service, run by your browser's maker
- What it receives
- A wake-up signal with no content, sent to the push address your browser gave us, when a request is waiting for you
- Where it is processed
- The United States and other countries
- Safeguard for transfers out of Europe
- We have no contract with any push service. Two of the four push services we can send to state that they are certified under the EU-US Data Privacy Framework; whether that covers this use is part of our pending legal review. For the other two, no safeguard is in place yet
Public time relay, run by others
- What it receives
- Your IP address and which time value your browser asks for. It does not receive your files. Time-locked files open using a public time signal published by an independent network, and your browser fetches it from this relay directly: when you use time-locked files, and while the live counter on our file-tools page is on screen
- Where it is processed
- The United States
- Safeguard for transfers out of Europe
- None in place yet; our legal review is pending
Who sees your sign-in records
In Settings you can see the time, method and IP address of your 50 most recent recorded sign-ins and wrong-password attempts on your account. A wrong password recorded before your email was confirmed is listed without its IP address. Our admins with permission see all of it, including every IP address.
Some attempts are not recorded: those our rate limits refuse, failed passkey prompts, and invalid or expired sign-in links. Recording is best effort, so a database fault can drop a record.
Where your data is processed
The servers that run our service, and our database, are in Germany. Our web pages' server code runs in the United States, and the pages are delivered through the web host's worldwide network. Some copies and records are also in the United States: database snapshots, the server host's log archive and its records of a sample of requests, and the email sender's records. The public time relay is in the United States. File storage, DNS, the inbound email service and push services work across several countries. The table above gives each recipient's country.
We, the operator, also read the readable data listed on this page, such as account emails, sign-in records, our mailbox and the values sent through our device-test site, from where we work. That is a country outside the EU and the European Economic Area, for which the EU has made no adequacy decision. No safeguard covers that yet; the legal review before public launch will settle it.
Where data leaves Europe, we name a safeguard only where the provider's own terms confirm one. The EU-US Data Privacy Framework is an EU adequacy decision for US companies certified under it; standard contractual clauses are contract terms approved by the European Commission. Where no safeguard is confirmed, the table says so, and our legal review, due before public launch, will settle it. To get a copy of a safeguard named here, write to support@hesimesi.com.
None of these providers has a transfer mechanism under Türkiye's personal data protection law (KVKK) in place with us. The legal review will settle this too.
Your rights
You can ask to access, correct or delete your data, to restrict how we use it, and to receive it in a portable form. Email support@hesimesi.com; we answer within 30 days. The vault has no way to export your data yet, so we answer a portability request by email. For a deletion, we first confirm by writing to the address you sign in with.
Where we rely on legitimate interest, you can object at any time, on grounds relating to your situation. We then stop, unless we have compelling legitimate grounds that override your interests, or need the data for legal claims.
Where we rely on your consent, you can withdraw it at any time; that does not affect what we did before. To withdraw it, turn push notifications off, or sign out (or use “Sign out all other devices” in Settings) to end a remembered session.
Türkiye's data protection law adds the right to learn whether your data is processed, for what purpose, and whether it is used for that purpose; to learn who receives it, inside the country or abroad; to have recipients told of a correction or deletion; to object to an outcome against you reached only by automated analysis; and to compensation for damage caused by unlawful processing.
You can complain to the data protection authority where you live, or to Türkiye's Personal Data Protection Authority.
In your vault you can also see your activity log (under Activity) and your recent sign-ins (under Settings).
Do you have to give us this?
An email address and a password or passkey are needed to open an account. The contact form needs its fields so we can reply. Without them we can't open your account or reply to you. Your IP address is collected automatically when you use the site.
Automated decisions
Automatic security limits can pause sign-in attempts for a while, for example after too many wrong passwords. We make no other automated decision with legal or similarly significant effect. A person decides whether an account is approved during the beta, and whether it is suspended.
During the beta
- Use sample details only, and don't store other people's personal data in files or saved details.
- Have your agent send files only to your own address or to someone who has agreed to receive them: the recipient's address stays in the activity log, with no fixed end date, also after your account is deleted.
- We don't offer a data-processing agreement (a contract a business signs before a provider stores its customers' personal data).
- The beta may end, and its data may then be deleted.
- Anyone can sign up, but an account opens only when we approve it by hand.
- We run a demo visa site for testers, on our server host in Germany. It keeps your draft application (name, email, arrival date and trip purpose) in its memory for up to 6 hours, sets one cookie that usually ends when you close the browser, and sends the vault a contact hint: the first letter of your email and its domain. The vault stores the hint with the site request and shows it in the approval app; site requests are kept 30 days. When you approve a delivery to it, the demo site opens the details you approved in its memory, checks them, and keeps no value, only the receipt and which fields failed its check; its log lines hold none of them. Our legal basis for the demo site is our legitimate interest in testing the service.
- We also run two test tools. A release-demo destination, on our server host in Germany, writes each value it receives to its log, which the server host keeps for 7 days, plus an archive in the United States for 30 days. Values sent through our device-test site are opened by us, on our own computer. Our legal basis for the test tools is the same legitimate interest in testing the service.
Backups, logs and email copies
Some copies and records outlast a deletion. Deleting your data or your account does not reach them at once; each goes as it ages out:
- Database snapshots: the server host takes one every day and keeps each for 5 days, in the United States. Deleted data can remain in them for up to about 5 days.
- File storage: snapshots and a recycle bin for deleted files are both off, so it keeps no deleted copies for us. We have not yet confirmed whether the provider keeps backup copies of its own.
- A sealed file whose upload or deletion failed half-way can stay in file storage with no record pointing to it. It can't be opened without your key.
- A file someone downloaded through a share link: the copy they already downloaded stays with them.
- Usage counts: when an organisation goes with its owner's account, its usage counts stay until our next cleanup pass, within about 6 hours.
- A delivery to a site: our server holds its sealed bundle only in its memory, never in its database, for at most about 21 minutes.
- The demo visa site's draft application: held in that site's memory for up to 6 hours, as “During the beta” says.
- Email sender: keeps each message it sends, with its recipient and full content, one-time links included, for up to 30 days, plus up to 7 days in its backups.
- Our mailbox at the inbound email service: mail to and from support@hesimesi.com and security@hesimesi.com, and our new-account alerts, stay until we delete them.
- Server logs: our service and the demo visa site write log lines that, by design, hold no content, IP addresses or emails, only the kind of request and its result. Our log store, on the server host in Germany, collects only these two programs' logs and keeps them for 30 days. The server host also keeps its own copy for 7 days, and an archive in the United States for 30 days.
- Database error lines: the database's error lines can hold an email address, for example when someone signs up with an address that already has an account. These lines are not in our log store. The server host keeps them for 7 days, plus an archive in the United States for 30 days.
- Test-tool logs: the release-demo destination's log holds the test values it received. It is not in our log store. The server host keeps it for 7 days, plus an archive in the United States for 30 days.
- Server host request records: the server host keeps no log of every request. It keeps detailed records of a sample of requests, which include the IP address, in the United States for up to 60 days. It also records failed requests with the address asked for and no IP address, and does not publish how long it keeps them.
- Web host request logs: the request logs we can read are kept for 1 hour. The web host keeps its own system records for as long as it considers necessary, and publishes no fixed period.
We added no analytics or advertising, and sell nothing
We have added no analytics, tracking or advertising to our pages, and we don't sell your data. Our pages' security policy lets your browser load content only from our own site, and connect only to our site, our service and the public time relay.
The hosts' own records are described above.
Changes to this page
Before a change that affects your data or your rights, we email every account. The date at the top shows the latest edit.