Privacy policy

What gate4.ai keeps, where it goes, and what you can do about it. Revision of 6 September 2026.

What the service does

gate4.ai receives a copy of your notes over WebDAV (the Remotely Save plugin in Obsidian), stores the files, builds a search index over them, and serves that index to an AI assistant over MCP. The point is that your notes are reachable from your phone and from a browser while your computer is off.

What we hold

• The account. Email address, a password hash (argon2id — we do not have the password itself), the dates the account was created and last signed in to, and the timezone you chose.
• The note files, whole — in Cloudflare R2 object storage. Everything the sync plugin uploaded: markdown, and attachments such as images and PDFs.
• Note metadata in Postgres: path and file name, title, frontmatter fields, tags, size, content hash, modification dates.
• The text of your notes — in the database, in the clear. Markdown files are cut into chunks, and the text of every chunk is stored in Postgres as it is, with a full-text index over it. Together the chunks cover the whole note. None of it is encrypted.
• Vector representations of those chunks — 1024 numbers each — and a cache of vectors keyed by content hash.
• Access keys, as hashes only. The sync password and the tokens of AI clients are stored hashed; the secret itself is shown once, when it is issued.
• An activity journal. What the plugin uploaded, what of it reached the index, which notes an assistant touched and with which tool, when, with what outcome and how long it took. You can read it on the activity page.
• Technical logs and traces. The web server's request log — time, IP address, method, request path (and a request path is a note path), response code; the services' structured logs; execution traces. No note content is in them: authorization headers and cookies are stripped, and note text, titles and search queries are kept out of the logs by a rule an automated test enforces.
• Cookies. One: the signed cabinet session, which lives seven days. No analytics, no counters, no advertising cookies.

We can read your notes

Plainly: the text of your notes and chunks sits in the database in the clear, the files sit in a bucket, and a person with access to the server can read them. This version of the service has no end-to-end encryption.

The reason is technical, and we would rather name it than promise encryption we do not have. Half of the search is full-text: it is built on a morphological index, and such an index cannot be built over ciphertext. Encrypting the content would cost exactly the thing the service exists for.

Instead of cryptography we give you what can be checked:

• an access journal — every time an assistant reaches into your notes is visible in the cabinet;
• the list of connected clients — who has access, when they last came in, and a Revoke button that takes effect at once;
• writing only into the folders you opened yourself;
• a trash and previous versions of notes, kept 30 days.

In ordinary operation we do not read your notes: access to the database is there to run the service. We may look at a particular note if you write to support with a question that cannot be answered otherwise — and only for that question.

Who else receives data

• Voyage AI — the embedding provider. The text of the chunks of your markdown notes goes there (model voyage-4; a vector comes back), and so does the text of the search query an assistant asks. Nothing else: not your address, not any account identifier. Attachments — images, PDFs, anything that is not markdown — are never sent, because they are not indexed at all.
• Cloudflare R2 — storage for the note files (region Eastern North America, USA) and a daily database backup, in a separate bucket under a separate key.
• Hostup AB — the server the service runs on. Sweden.
• Your AI client. When you connect Claude or another assistant to gate4.ai, the fragments it finds and the notes it reads go to it — that is what the service is for. From there it handles them under its rules, not ours.

Nobody else. There are no advertising networks and no third-party analytics. Notes are not used to train models — ours or anybody's.

The files in Cloudflare R2 are encrypted by the provider. That encryption protects against a stolen disk, not against us: the keys are the provider's and the service's.

What a connected assistant can do

You grant the permissions on the consent page, and there are two:

• notes:search — search the text of your notes and read what it finds (search_notes, read_note).
• notes:write — create notes, append to them, change a section, rename and delete (create_note, append_to_note, append_daily_note, patch_note, move_note, delete_note).

Writing is limited to the folders you opened yourself, on the write rules page. Service paths — editor settings, Obsidian's own trash, the sync plugin's bookkeeping — are always closed and cannot be opened by an allow rule.

Before any overwrite the previous content of the note is kept, and deleting is soft: the note goes to a trash. Both are recoverable for 30 days. Every request an assistant makes lands in the journal, and access is revoked from the cabinet — at once, without us.

How long we keep it

• Notes, the index and the activity journal — while your account exists.
• The trash and previous versions of notes — 30 days, then deleted.
• Database backups — 30 days.
• Request logs — up to 30 days; traces 7 days; metrics 6 months.
• A deleted account — the data and the indexes go immediately, from the database and from the object store. Backups that already hold them expire on their own schedule, no later than 30 days.

Your rights

• Revoke access. The Revoke button beside a client in the cabinet: the application's next request is refused.
• See what happened. The activity page: uploads, indexing and assistant requests on one timeline.
• Delete your notes, or the whole account. Both are buttons in the cabinet, and both say what they take before you press them. Deleting the vault contents keeps the account; deleting the account takes everything.
• Get a copy of your data. Write to support@gate4.ai and we will export the files and the metadata. There is no “export everything” button in the cabinet yet; meanwhile the original of your notes is in Obsidian and our copy is the secondary one.
• Correct your data, or find out what we hold. The same address.

Who the operator is, and how to reach us

For anything in this policy: support@gate4.ai.

Honestly about what is not here: the legal entity the service operates under has not been registered yet, so we have nothing to put in place of an operator's details or a jurisdiction. gate4.ai runs as the author's private project at an early stage. When the entity exists, the details and the governing law will be written here and the revision date updated. We think leaving the space empty is better than filling it with a plausible invention.

Changes to this policy

The revision date is at the top of the page. If a change is material — a new recipient of data, say, or a different retention period — we will write to the account's address before it takes effect.