Privacy notice

This notice describes what Rekvira does with personal data. Rekvira is an MCP service that retrieves official EU regulation text for AI assistants. It is written from what the system actually stores, not from intention.

Who we are

Kiznis Studio, the operator of rekvira.com, is the controller of the personal data described here. You can reach us at privacy@rekvira.com or hello@rekvira.com.

What Rekvira is, in data-protection terms

Rekvira searches and reads official EU regulation texts published on EUR-Lex. Those texts are public records; we do not treat them as your personal data.

What we hold about you is the small amount needed to run the service. That is the assessments and private workflows you deliberately save, usage counts, and, if you choose to sign in, a free account with its keys. We do not build advertising profiles, we do not sell data, and we do not search for or index people.

MCP queries and server logs

Procurement and security reviewers usually ask three things. This section answers them from what the system does today, not from intention.

Query text

Search queries and ordinary retrieval arguments are not written to a Rekvira database. Each retrieval call is handled in memory and discarded when the response is sent.

Deliberate state tools

Deliberate state tools are different: record_assessment stores the regulation, pinpoint, verdict, optional structured reason and timestamp; save_workflow stores the workflow ID, title, summary, body, published state and timestamps. Those records are keyed by the opaque trial_id returned by connect, or by your account once you sign in. A different trial_id cannot retrieve, update or delete them, and published does not share a workflow publicly. The other narrow exception is feedback sent with submit_feedback; that deliberate feedback is described below, and nothing from the preceding query or calls is attached to it automatically.

Network addresses

Our own web server keeps an access log for 14 days. It records the time, the page or endpoint requested and the client or browser name. Your network address is shortened before it is written: the last two parts of an IPv4 address are removed. We use it to count visits and assistant connections, not to build profiles. Cloudflare, which sits in front of our sites, may also record your network address in its own logs; see the sub-processors list for who runs infrastructure and where. Rekvira does not build a user profile from these logs.

After you create an account

A free account adds your email address, the items you chose to keep, your plan choice and the dates you signed in. For each call we count only which account made it, never the text of a search. Account data is kept while the account exists; see How long we keep it below.

What we collect when you call a tool

Every Rekvira tool needs an account with a verified email address; registration is free on the beta plan, with no daily search limit enforced during the beta (whoami returns searches_left_today: null).

Usage counts

Each tool call adds one line to a private event ledger. The line holds the time, whether it answered, whether it was a setup step such as connect, and whether the call came from our own testing or monitoring. It also holds a salted one-way hash of the network address, never the address itself or what you asked. From these lines we count, in aggregate, how many distinct people used the service in the last 7 and 30 days; only those totals leave the service. Lawful basis: legitimate interest, Art 6(1)(f).

Search and ordinary retrieval calls

Search queries and ordinary retrieval arguments are not written to a Rekvira database. Each retrieval call is handled in memory and discarded when the response is sent.

Assessments and private workflows you deliberately save

record_assessment stores the regulation, pinpoint, structured verdict or reason and the timestamp you submit. save_workflow stores the workflow ID, title, summary, body, published state and timestamps you submit. Records made before 14 October 2026 without an account remain under the opaque trial_id returned by connect; a different trial_id cannot retrieve, update or delete them. The published state marks a workflow ready only for you; it does not share it publicly. Do not put personal data in a private workflow.

Feedback you explicitly send

If you use submit_feedback after approving the exact message, Rekvira stores only what is sent. That is the message, its category and severity, and whether it was your own words or an agent draft you approved. It also holds any context you chose to include (what you expected, what came back, the tool, a query) and a reply address if you gave one. We store it with your account, and the time.

What happens to feedback

It is emailed to our team. Rekvira does not attach a search query, tool arguments or prior-call history to feedback automatically. We keep it 24 months, delete it with your account, and delete it sooner on request to hello@rekvira.com. It is never shown on a public page. Lawful basis: legitimate interest in knowing whether the product works, Art 6(1)(f).

Infrastructure logs

Our hosting and CDN providers may record your network address in standard server access logs. The sub-processors list names them and where they operate. A personal key placed in a connection address (?key=) is removed from our own access log before it is written.

Accounts

Every tool needs a free account (the beta plan). You create one by asking your assistant to sign you in. Rekvira emails you one message with a confirmation link and a six-digit code, and the account exists once you confirm. Lawful basis for everything in this section: performance of the contract you ask for when you sign in, Art 6(1)(b).

Your email address

Used to sign you in and, if you ask, to confirm deleting the account. We do not send marketing email.

Sign-in links and codes

Each request stores your email address and a SHA-256 hash of the six-digit code and of the link. It also stores a one-way hash of the requesting network address (used only to stop abuse), and the times it was created, confirmed and used. A link and code expire after 15 minutes and work once.

Keys and sessions

A sign-in issues a personal key (rek_…) and a session value your assistant carries in the conversation. Signing in through your assistant’s own Sign in button (OAuth) issues a key in the same way. We store only SHA-256 hashes of keys and sessions, with when each was created and last used. A session lasts 30 days. You can list and revoke keys with rekvira_account.

What the account keeps

Assessments and private workflows are kept under your account instead of a trial code, so they are there on every device. If you had worked without an account and sign in with that trial’s code, those records move into the account.

Plan choice

Nothing is charged during the beta. If you tell your assistant which plan you would choose, we record that choice and the time. It is not an order and creates no payment obligation.

Usage

For each tool call made while signed in, the ledger line above records your account’s number instead of the address hash, never your email or what you asked. We use it only for aggregate counts.

Founding Beta terms

No payment is taken during the Founding Beta. The beta terms are in the terms.

If payments start

No payment is taken during the beta. Before any payment is taken, this notice will name the billing details we would then store (for example a billing name and invoice address) and the payment provider.

Sub-processors

The providers that process personal data on our behalf are on the sub-processors list, with the date of the list. That page names hosting and edge infrastructure only: not the EUR-Lex corpus.

What we do not do

We do not sell personal data, we do not use it to train models, and we do not enrich it from third-party people-search sources. Rekvira is a regulation corpus tool for compliance professionals, and that boundary is deliberate.

How long we keep it

Search queries are never kept. Assessments and private workflows made before 14 October 2026 without an account remain in the private state ledger until they are replaced, deleted or removed after a privacy request. There is no automatic expiry. delete_workflow removes a private workflow. A lost trial_id cannot be recovered, because no email is associated with it.

Account data

Account data is kept while the account exists. Sign-in links and codes stop working after 15 minutes; the records of them are deleted after 30 days, and with the account. Sessions expire after 30 days. Revoked keys are kept as revoked (prefix and dates only) so the account’s key history stays readable, and are deleted with the account. The access log of our own web server is kept for 14 days. Explicitly submitted feedback is kept 24 months, deleted with the account, or sooner if you ask.

Backups

The state ledger is backed up, encrypted, every day: daily copies are kept for 14 days, weekly copies for 8 weeks and monthly copies for six months. A deleted account therefore disappears from the backups within six months, as older copies are replaced; we do not restore a deleted account from a backup.

Deleting your account, or getting a copy

Ask your assistant: rekvira_account exports everything the account holds, and deletes it. Deletion is confirmed from your inbox. We email a link, and the account is erased only when you open it and press Delete. An instruction typed into a chat window is not proof that the account holder wants it gone. Deleting erases the account, its keys and sessions, its sign-in records, its plan choice, and its assessments and private workflows. Aggregate counts that no longer name the account are not personal data and stay.

You can also write to privacy@rekvira.com.

Your rights

You can ask for a copy of your data, and ask us to correct it or delete it. You can ask us to restrict or object to how we use it, and to receive it in a portable form. Where we rely on consent you can withdraw it at any time without affecting what came before.

Write to privacy@rekvira.com. We will answer within one month.

If you think we have handled your data wrongly you can complain to the supervisory authority where you live.

Changes

Material changes are announced on this page with the date of the change, rather than by quietly replacing it.