Privacy Policy
This policy explains what personal data Tunnel processes across tunnelpowered.com, the Tunnel dashboard and our products, why, on what legal basis, who receives it, where it goes, how long we keep it, and the rights you have. Its lists of purposes and providers are generated from the record of processing our systems are checked against, so they cannot fall behind what we actually do.
Last updated: November 13, 2026
1.Who we are
Tunnel ("Tunnel", "we", "us") operates the website tunnelpowered.com, the Tunnel dashboard at app.tunnelpowered.com, and our products: AI GEO, Landline, Tunnel t0, Flamecloak, Tunnel ADR and Limit (together, the "Services").
Tunnel is a product of "STILL BETA TECH" SRL, a company registered in the Republic of Moldova, at MD-2093, str. Mihai Viteazul 28, s. Hulboaca, mun. Chișinău, Republic of Moldova. That company is the controller of the personal data described in this policy. Where we host a Flamecloak gateway for a customer, the customer is the controller of what the gateway sees of its own users, and we process it for them under our data processing agreement.
Our data protection officer is the company's chief executive. You can reach them, and us, about anything in this policy at contact@tunnelpowered.com.
2.Which laws we comply with
We are a Moldovan company, so Law No. 195/2024 on the protection of personal data of the Republic of Moldova governs what we do, and the National Centre for Personal Data Protection (datepersonale.md) supervises us. The articles cited in this policy are those of Law No. 195/2024 unless another law is named.
We also sell to customers in the European Union, so the GDPR (Regulation (EU) 2016/679) applies to what we do for people there, and the US state privacy laws apply to their residents. The rights in this policy are the same for everyone, wherever you live; the section on other laws says what those laws add.
Two commitments up front: we do not sell personal data, and we do not use advertising cookies. Analytics cookies are set only if you allow them.
3.What we do with personal data: your account
This section and the next four list every purpose for which we use personal data. They are generated from the same record of processing that our systems are checked against, so they change when the processing changes. Each purpose says what data it uses, where the data comes from, the legal basis (and whether you have to give the data), who receives it, and how long we keep it. The articles cited are those of Law No. 195/2024.
Running your account and your team.
- Data: Your email address, your name, a password (stored only as a hash), your plan and the products you use; the people you invite to your team, by email.
- Where it comes from: You, and the person who invited you to a team.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to.
- How long: While your account exists, then deleted with it. An account whose email address is never confirmed is deleted after 7 days. A team invitation nobody accepted is deleted 30 days after it expires.
Signing you in and keeping the account safe.
- Data: Sign-in sessions and the codes we email you; if you sign in with Google, the name and email address Google gives us.
- Where it comes from: You, and Google when you sign in with Google.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to; Google, when you sign in with Google.
- How long: A sign-in session is deleted 30 days after it expires.
Billing your plan and keeping the accounting records.
- Data: Your plan, its changes, your payments and invoicing details. Card payments are handled by the payment processor; we never store card numbers.
- Where it comes from: You, and our records of your plan.
- Legal basis: A legal obligation (art. 6(1)(c)). Required by law.
- Who receives it: Our hosting provider in Moldova.
- How long: 5 years, as the accounting law requires (Law No. 287/2017), also after the account is deleted.
Telling you what you asked to be told, where you asked.
- Data: The channels you add: another email address, a Telegram chat, a WhatsApp number or a Viber id, your browser's push subscription; the notifications we sent you.
- Where it comes from: You: the channels you added and switched on.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to; Telegram, if you linked it; WhatsApp, if you gave a WhatsApp number; Viber, if you gave a Viber id; the push service your browser uses (Apple, Google or Mozilla), which cannot read the message.
- How long: Your channels while your account exists; each notification 12 months.
4.What we do with personal data: our products
Making your business findable by AI assistants (AI GEO).
- Data: Your business profile and websites, their public content, and the questions we ask AI assistants about your business. A website can name a person, for example a founder; where the business is a person, the profile is personal data.
- Where it comes from: You, your website, and the AI models we ask about it.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; OpenRouter and the AI model providers listed below; anyone: this part is published.
- How long: While your account exists. An industry scan you asked for drops your details 12 months after it finishes; its industry figures stay.
Letting AI agents ask your business, and keeping what was said (Landline).
- Data: The messages agents send your business and its answers, which can carry a name, a phone number or a place; escalations to the people at your business; the commitments your business made; disputes about them.
- Where it comes from: You, and the AI agents that write to your business.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; OpenRouter and the AI model providers listed below; the AI agents in the conversation; our own mail server, and the mail provider of the address we write to; Telegram, if you linked it; WhatsApp, if you gave a WhatsApp number; Viber, if you gave a Viber id.
- How long: Conversations, messages and escalations 24 months after their last activity; a resolved dispute 3 years. A commitment your business signed is kept as proof.
Knowing which AI agents read our customers' profiles.
- Data: For each read of our public knowledge base, over HTTP, MCP or A2A: the time, the interface, the kind of read, whether the caller identified itself, and a salted, truncated HMAC of its IP address. We do not record the IP address itself, nor the text of a query. For agents that register: the registration and its grants.
- Where it comes from: The AI agents that read your profile.
- Legal basis: Our legitimate interest (art. 6(1)(f)). We do not ask you for this data, and you can object.
- Our interest: Stopping abuse of our customers' profiles, and showing each customer who read theirs.
- If you object: A customer can switch the record off for their own profile. For an anonymous read we hold nothing that links it back to you.
- Who receives it: Our hosting provider in Moldova.
- How long: Reads of the knowledge base 180 days, then deleted automatically. An agent's registration until it is revoked, then 12 months before it is anonymised.
Verifying a business and publishing the verification (Tunnel t0).
- Data: The verification case, the claims and checks, the evidence you send, and the person verified; an identity document only if you send one.
- Where it comes from: You, our verification staff, and the checks we run.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; anyone: this part is published.
- How long: The case while your account exists. The evidence and the verification record are kept as proof. The log of who opened the evidence 3 years.
Running the Flamecloak gateways you set up, and their approvers.
- Data: Your gateways and their settings; the approvers you invite, their names, email addresses and the channels they are reached on; their approvals. What a gateway sees of your own users' requests is yours, and we process it for you under the data processing agreement.
- Where it comes from: You, and the approvers you invited.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to; Telegram, if you linked it; the push service your browser uses (Apple, Google or Mozilla), which cannot read the message; Slack, if your organisation connects it.
- How long: While your account exists. An evidence export 12 months; an invitation nobody accepted 30 days after it expires.
Resolving disputes between agents under an agreement both parties signed (Tunnel ADR).
- Data: The agreement, the claims, the evidence, the judgments of the AI panel, the award, a reviewer's decision, a party's request for a person to review the award with our staff's conclusion, and the parties' passkeys (public keys only).
- Where it comes from: You, the other party, and the AI models that judge a case.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; OpenRouter and the AI model providers listed below; the other party to the agreement.
- How long: Agreements, cases, judgments, awards and reviews of awards are kept as proof. The content of the evidence is destroyed when the agreement's own retention period ends. A pending agent claim 30 days, and a sign-in challenge 1 day, after they expire.
Letting you set and sign the limits that agents ask you about (Limit).
- Data: Your limits, the questions organisations' agents asked and your signed answers, the spends reported, the organisations that asked, your passkeys (public keys only) and push subscriptions.
- Where it comes from: You, and the organisations whose agents ask you.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; the push service your browser uses (Apple, Google or Mozilla), which cannot read the message; the organisation whose agent asked, for its own question.
- How long: Your limits, the questions, your answers, the spends and your passkeys are kept as proof, also after you delete your account, which is then paused so nobody can ask it again. A signing request or a grant 30 days after it expires; a sign-in ticket 1 day; a passkey recovery 12 months.
5.What we do with personal data: forms, newsletters and reviews
Running the free visibility scan you asked for.
- Data: The email address, name, company and website you gave in the form, and the result.
- Where it comes from: You.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; OpenRouter and the AI model providers listed below; our own mail server, and the mail provider of the address we write to.
- How long: 12 months after your last contact with us.
Answering a request for a paid plan.
- Data: Your request, your account and how to reach you.
- Where it comes from: You.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to.
- How long: 24 months.
Sending the newsletter you subscribed to.
- Data: Your email address, and when you subscribed, confirmed and unsubscribed.
- Where it comes from: You.
- Legal basis: Your consent (art. 6(1)(a)). Optional: saying no, or withdrawing later, changes nothing else.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to.
- How long: Until you unsubscribe, then 30 days. A subscription you never confirmed is deleted 30 days after we asked you to confirm it.
Emailing you news about our products, when you asked for it.
- Data: Your account's email address and your choice.
- Where it comes from: You.
- Legal basis: Your consent (art. 6(1)(a)). Optional: saying no, or withdrawing later, changes nothing else.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to.
- How long: Until you withdraw your consent.
Showing your review on our website.
- Data: Your review, your name and your company, as you gave them.
- Where it comes from: You.
- Legal basis: Your consent (art. 6(1)(a)). Optional: saying no, or withdrawing later, changes nothing else.
- Who receives it: Our hosting provider in Moldova; anyone: this part is published.
- How long: Until you withdraw it.
6.What we do with personal data: records we must keep
Proving what you consented to, under which text, and when you withdrew.
- Data: Each consent and acceptance: what it was for, the version of the text, when it was given and when it was withdrawn.
- Where it comes from: You: what you agreed to, and when.
- Legal basis: A legal obligation (art. 6(1)(c)). Required by law.
- Who receives it: Our hosting provider in Moldova.
- How long: While the consent stands, then 3 years after you withdraw it.
Keeping a record of the email we sent.
- Data: The address, the subject, the kind of message, when it was sent and whether it was delivered.
- Where it comes from: Our own mail server.
- Legal basis: Our legitimate interest (art. 6(1)(f)). We do not ask you for this data, and you can object.
- Our interest: Proving what we sent, to whom and when, and finding failed deliveries.
- If you object: This record is how we prove that a notice about your account reached you, which can decide a dispute. It is kept only 90 days, so we keep it despite an objection (art. 21(1)).
- Who receives it: Our hosting provider in Moldova.
- How long: 90 days, then deleted automatically.
Answering your requests about your data, and keeping the record that we did.
- Data: Your request, how we confirmed it was you, our answer and its dates.
- Where it comes from: You.
- Legal basis: A legal obligation (art. 6(1)(c)). Required by law.
- Who receives it: Our hosting provider in Moldova; our own mail server, and the mail provider of the address we write to.
- How long: A request and our answer 3 years after we receive it, kept as proof that we answered. A confirmation code 1 day.
Keeping the files attached to a record.
- Data: A file you upload, such as a logo or a document.
- Where it comes from: You, when you uploaded the file.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova; anyone: this part is published.
- How long: As long as the record that holds the file.
Giving our own staff access to the administration.
- Data: Our staff members' names, email addresses and access.
- Where it comes from: Our own staff records.
- Legal basis: Our contract with you (art. 6(1)(b)). Needed for the service: without it we cannot provide it.
- Who receives it: Our hosting provider in Moldova.
- How long: While the staff member works for us.
Recording which of our staff opened personal data, so that access can be checked.
- Data: Who opened which record, and when.
- Where it comes from: Our own systems, when a staff member opens a record.
- Legal basis: A legal obligation (art. 6(1)(c)). Required by law.
- Who receives it: Our hosting provider in Moldova.
- How long: 3 years, the period in which a complaint can be made.
Recording every personal data breach, what it touched and how we answered it.
- Data: What happened, whose data it touched, what we did, and whom we told.
- Where it comes from: Our own staff, from what they found.
- Legal basis: A legal obligation (art. 6(1)(c)). Required by law.
- Who receives it: Our hosting provider in Moldova.
- How long: Kept, as the law requires, for the Centre to check (art. 33(5)).
7.What we do with personal data: keeping our servers safe
Keeping our servers and the people using them safe: seeing the traffic, noticing attacks and break-ins, and blocking the addresses that attack us.
- Data: For each request to our websites, dashboard, API and the gateways we host: the time, your IP address, the address requested without anything after "?", the status, size and duration of the answer, the website you came from (its domain only), and your browser's name. For logins to our servers: the address, the account and how it signed in. The addresses our firewall blocked. When a sign-in to your account fails, a sign-in token is used a second time, a request is refused for coming too fast, or an AI agent's signature does not check out, and for each sign-in to our admin panel: the time, the address, the account if there is one, and what happened, never what was typed.
- Where it comes from: Our own servers, from the requests and logins that reach them.
- Legal basis: Our legitimate interest (art. 6(1)(f)). We do not ask you for this data, and you can object.
- Our interest: Seeing attacks and break-ins, and stopping them, which is part of keeping your data safe (art. 32).
- If you object: A record that left out whoever objected would leave out exactly the addresses an attacker controls. Each record holding your address is deleted after 30 days, so we keep it despite an objection (art. 21(1)).
- Who receives it: Our hosting provider in Moldova.
- How long: Records and server logs that hold an IP address: at most 30 days, then deleted automatically. Counts per minute, which hold no address and no page: 13 months.
8.AI models and your data
Several products send text to AI models. We send a model only what its task needs, and the lists above say which purposes do. Each kind of call is recorded with what it sends.
- Questions about a business (AI GEO, the free scan): a business's name, its website's public content, and generated questions. These describe a business, not you; where the business is a person, they are personal data.
- Reading a message to a business (Landline): a model reads what an agent wrote to tell what it asks. It gets the message only, cut at 2,000 characters, and nothing about the business; the answer comes from the business's own data, not from the model.
- Judging a case (Tunnel ADR): the agreement, the claims and the evidence, as the parties submitted them.
Every call that carries personal data, and every ADR call, goes through OpenRouter to a model that keeps nothing and trains on nothing, and never to a free model. We never send models your password, your payment details or an identity document.
9.Decisions made by AI models
In Tunnel ADR, a panel of AI models decides a dispute between two parties under an agreement both signed (art. 22(2)(a)). This is the only decision we make by automated means alone, and it can affect the parties' rights under their agreement. How it works:
- The agreement names the panel: one model from each family it lists. Each model reads the case alone, in two rounds, and gives a judgment; the agreement's own rule (unanimity or a majority) decides what counts as an outcome.
- The case is judged again under small variations, as many times as the agreement says, to measure whether the outcome is stable.
- A person decides instead of the panel when the panel reaches no outcome the agreement's rule accepts, or when the evidence is too large for the panel, if the agreement sends those cases to a reviewer: our staff, or a person both parties named.
- The award states which models judged, how each voted, and whether a person decided.
A person's review. Within 30 days of the award, either party can ask a person to review it, from the case page, saying why. Our staff read the case, the award and both parties' reasons, and record whether the decision stands or is wrong, with their reasons; both parties are told. The signed award stays as it was issued, as proof, and the review is kept beside it.
10.Signed records are kept as proof
What you sign or approve in Tunnel - limits and answers in Limit, agreements, evidence and awards in Tunnel ADR, verifications in Tunnel t0, commitments in Landline - is kept intact as proof, so that it can be verified at any time, also after you delete your account. Deleting your data does not delete it. A record that could be deleted on request could not show what was agreed, and anyone could hide a fraud by deleting their data. The law provides for this: data needed to establish, exercise or defend legal claims is kept despite a request to erase it (art. 17(3)(e)).
You are asked to confirm that you understand this before you use any of our services.
11.Content we crawl and republish
AI GEO reads a website you register and republishes a machine-readable version of it - structured data, an llms.txt file, a knowledge-base record - at stable public endpoints so AI assistants and agents can retrieve it.
We do this only for websites you register and confirm you own or are authorised to manage, under our contract with you. We honour robots directives on third-party sites, and we do not crawl a site into the knowledge base because someone else told us about it.
Website content is usually not personal data, but it can contain some - a founder's name, a staff photo, a direct email address. Where it does, you are the source of that content and remain responsible for having the right to publish it. If a person asks us to remove their personal data from a published record, we will remove it and tell you.
A listing is removed from the public knowledge base when you delete the website or your account.
12.Identity verification
Human verification is optional. It exists so that a business can prove a real, accountable person stands behind a listing.
If you request it, we may ask you for an identity document or another proof of your role in the business. We ask for it only when you request verification, we use it for nothing except confirming your identity, and we do not share it with AI platforms or any other third party.
The public record shows only that a named person was verified and when. It does not publish your document, your document number, or your date of birth.
13.When an AI agent queries our knowledge base
Our public knowledge base can be read by anyone - through plain HTTP, through our MCP server, or through our A2A endpoint - with no account and no credentials. We keep a log of those reads, because whether anyone actually uses the registry is the central question about this product and we would rather measure it than assume it.
What we record: the time, which of the three interfaces was used, which kind of read it was, whether the caller identified itself, whether we answered completely, how fresh the answer was, and how long it took. We also record a salted, truncated HMAC of the IP address, so that ten reads from one caller can be told apart from one read by ten callers.
What we do not record: the IP address itself, and the text of the query. We store the *shape* of a request - that a search term was present and roughly how long it was - never its content.
Our legal basis is legitimate interest (Article 6(1)(f)): operating and protecting a public API against abuse, and measuring whether the service is used at all. There is no profiling, no advertising, no enrichment, and no sharing of this log with anyone. We keep these records for 180 days, after which they are deleted automatically.
14.Who processes personal data for us, and where
Every company that receives personal data from us. A processor uses it only on our instructions, under a contract (art. 28); an independent one decides its own purposes, under its own policy. We do not sell personal data, and we do not share it for advertising.
| Provider | Where | What it receives | Transfer safeguard |
|---|---|---|---|
| Our hosting provider in Moldova (processes for us, under a contract) | Moldova | Everything the platform stores: the server, its disks and its backups. | In Moldova: no transfer. |
| Our own mail server, on the same host (our own system) | Moldova | Every email we send: the address and the message. | In Moldova: no transfer. |
| Google LLC (Sign in with Google) (decides its own purposes, under its own policy) | United States | Nothing from us: you sign in at Google, and Google sends us your name and email address. | We send Google nothing: you sign in at Google, under your own account. |
| Google LLC (Google Analytics) (processes for us, under a contract) | United States | On our website only, after you allowed it and never with Global Privacy Control on: the pages you view, a pseudonymous browser id, and your IP address. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| Telegram FZ-LLC (decides its own purposes, under its own policy) | United Arab Emirates | The text of a notification and the chat it goes to, if you linked Telegram. | United Arab Emirates is not on the Centre's list of countries with adequate protection. We send there only to do what you asked: to reach you on the channel you chose (art. 49(1)(b)). |
| WhatsApp (Meta Platforms Ireland Ltd) (processes for us, under a contract) | Ireland | The text of a notification and the number it goes to. Used only when switched on. | Ireland, in the European Economic Area: no transfer safeguard is needed. |
| Viber (Rakuten Viber S.à r.l.) (decides its own purposes, under its own policy) | Luxembourg | The text of a notification and the Viber id it goes to. Used only when switched on. | Luxembourg, in the European Economic Area: no transfer safeguard is needed. |
| The browser push services of Apple, Google and Mozilla (decides its own purposes, under its own policy) | United States | A message encrypted to your own browser, which the service cannot read, and the subscription address. | The United States is not on the Centre's list of countries with adequate protection. Your browser chose the service when you turned notifications on, and the message is encrypted so the service cannot read it (art. 49(1)(b)). |
| OpenRouter, Inc. (processes for us, under a contract) | United States | The text of the AI calls routed through it: every call that carries personal data, and all of ADR. For those, only a model endpoint that keeps nothing and trains on nothing, and never a free model. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| The AI model providers OpenRouter routes to (such as OpenAI, Anthropic, Google, xAI and Mistral) (processes for OpenRouter) | Various | The same text, forwarded by OpenRouter, as its sub-processors. | Wherever each provider runs. Outside Moldova and the European Economic Area, the safeguard is OpenRouter's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| Anthropic, PBC (processes for us, under a contract) | United States | Our own AI calls about a business, when we use Claude, and the visibility questions we ask Claude. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| OpenAI (API) (processes for us, under a contract) | United States | The visibility questions we ask ChatGPT about a business, and our AI calls when a website is set to OpenAI. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| Google LLC (Gemini API, paid) (processes for us, under a contract) | United States | The visibility questions we ask Gemini about a business, and our AI calls when a website is set to Gemini. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| X.AI LLC (Grok API) (processes for us, under a contract) | United States | The visibility questions we ask Grok about a business, and our AI calls when a website is set to Grok. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| Perplexity AI, Inc. (processes for us, under a contract) | United States | The visibility questions we ask Perplexity: a business's name and a question. Personal data reaches it only when the business is a person. | The United States is not on the Centre's list of countries with adequate protection (Decision No. 41/2026). The safeguard is the provider's data processing agreement, which carries the EU standard contractual clauses. Ask us for a copy. |
| DeepSeek (API) (processes for us, under a contract) | China | Our AI calls about a business, only if DeepSeek is selected for it. Nothing selects it by default, and a call that carries personal data never goes to it. | China is not on the Centre's list of countries with adequate protection, and there is no data processing agreement: we never send it personal data. |
| Slack (Salesforce) (your organisation's own provider) | United States | Approval notices, posted to your organisation's own Slack workspace, if your approvers connected it. | Your organisation's choice and its own provider; we send nothing there ourselves. |
15.Transfers outside Moldova
Some of the providers above are outside Moldova. Ireland and Luxembourg are in the European Economic Area, where no safeguard is needed. The United States, the United Arab Emirates and China are not on the Centre's list of countries with adequate protection (Decision No. 41/2026).
For the AI providers and Google Analytics in the United States, the safeguard is each provider's data processing agreement, which carries the EU standard contractual clauses. For Telegram and the browser push services, we send only to reach you on the channel you chose. We never send personal data to DeepSeek. To get a copy of a safeguard, write to contact@tunnelpowered.com.
16.Other sharing
- When required by law, or to establish, exercise or defend legal claims, or to protect the Services and their users from fraud or abuse.
- In a merger, acquisition or asset sale, in which case this policy continues to apply to your data and we will tell you of any change of controller.
- If you run a Flamecloak gateway we host, our data processing agreement governs what we do with your users' data; you accept it when you add the gateway.
17.Deletion, backups and logs
- Deleting your account - from Account, under Your data. It takes effect after 7 days, during which you can cancel; then your data is deleted, except the signed records kept as proof and what the accounting law makes us keep.
- Backups - the database is copied every night, encrypted, and each copy is deleted after 30 days. When your account is deleted, your data leaves the backups when the last copy that holds it expires, at most 30 days later. If we ever restore a backup, every deletion made since it was taken is carried out again before the service runs on it.
- Server logs - our application's logs are kept for security, with email addresses, phone numbers, IPv4 addresses, codes and secrets masked before a line is written. Our web server's record of each request, and the app's record of failed sign-ins and refused requests, keep the IP address for at most 30 days: see *Keeping our servers safe* above.
- Flamecloak evidence - when a Flamecloak gateway we host for you is deleted, its record of decisions is exported, encrypted and kept for as long as the law requires. A copy is sent only to your company's management or to a regulator, on an official request, and every copy sent is logged. If your organisation turns on Say who asked (it is off until somebody turns it on), that record also holds who asked and what changes, in your applications' own words, and the path a held request called and the names of its body's fields, never their values.
18.Security
We use appropriate technical and organisational measures to protect your data, including encryption in transit (HTTPS), hashed passwords, access controls and rate limiting on public endpoints. We watch our servers for attacks and break-ins, and block the addresses that attack them. The addresses you give us only to reach you, such as a Telegram chat or a second email for notifications, are stored encrypted, with the key kept apart from the database. When one of our staff opens personal data in our administration panel, it is logged, and staff who do not need personal data have no access to it. No method of transmission or storage is completely secure. We record every personal data breach, with what happened and what we did about it. When one is likely to put your rights at risk, we tell the National Centre for Personal Data Protection within 72 hours of becoming aware of it; when the risk to you is high, we also tell you directly, in plain language, without undue delay.
19.Your rights
You have the right to:
- Be informed about what we do with your data - this policy (arts. 13 and 14).
- Access your data and get a copy of it (art. 15).
- Correct data that is wrong or incomplete (art. 16).
- Erase your data (art. 17), except the signed records kept as proof and what the law makes us keep.
- Restrict how we use your data while a question about it is settled (art. 18).
- Portability: receive the data you gave us in a structured, machine-readable file (art. 20).
- Object to processing based on our legitimate interest (art. 21).
- Withdraw your consent at any time, as easily as you gave it, without affecting what was done before (art. 7(3)).
- Not be subject to a decision by automated means alone without a person to turn to, and to contest it (art. 22).
- Complain to the National Centre for Personal Data Protection of the Republic of Moldova (datepersonale.md), at any time, without coming to us first.
How. With an account, most of this is under Account, in Your data: download a copy, change your login email or name, restrict, object, or delete your account. Without an account, or for anything else, use the request form or write to contact@tunnelpowered.com. We confirm it is you with a code, and answer within one month; a complex request can take up to two more months, and if so we tell you why within the first month. A request about a website that runs a Flamecloak gateway goes to the website's owner, who decides about that data; we pass it on.
20.Your rights under other laws
In the European Union and the United Kingdom, the GDPR and the UK GDPR give you the same rights as the list above, and you can also complain to the data protection authority where you live or work.
In California and other US states with a comprehensive privacy law - such as Virginia, Colorado, Connecticut and Texas - you also have the right to know what personal information we collect, use and disclose, and not to be discriminated against for exercising your rights. We do not sell or share personal information for cross-context behavioural advertising, so there is nothing to opt out of. You may act yourself or through an authorised agent; we respond within 45 days, extendable once by 45 days where permitted.
21.Email we send you
We send transactional email (email confirmation, codes, service and billing notices - necessary to provide the Services), product news only if you asked for it, and the newsletter only if you subscribed and confirmed. Every newsletter and product email has a working one-click unsubscribe, which takes effect immediately. Every email we send names your rights and where to use them.
22.Cookies and local storage
The consent bar names three purposes we use cookies and data for: delivering and maintaining the service, keeping spam, fraud and abuse out, and measuring how the site is used. This section says what each of those means in practice today, which is deliberately less than the purposes allow.
Measuring audience engagement uses Google Analytics, and only if you switch it on. Until you do — and if you reject, or never answer — nothing from Google loads and no analytics cookie is set. When it is on, Google Analytics sets two cookies, _ga and _ga_BPQVFZN22V, and Google LLC receives the pages you view, an identifier for your browser, and your approximate location derived from your IP address, as our processor. Switching it off stops it and removes both cookies. The site loads no advertising tags. The other script it loads from another origin is ours, and it adds structured data to the page rather than storing anything.
The first two purposes do not depend on cookies. Your IP address and request metadata reach our servers and are kept in logs for security and rate limiting, as described under *Keeping our servers safe* above — that is technically necessary to run the service and defend it, so it rests on legitimate interest rather than on consent. Declining the third purpose therefore does not change it, and we would rather say so here than let the panel imply otherwise.
One thing is kept in your browser: tunnel.consent, in local storage, recording the answer you gave to the consent bar so that we stop asking. It holds the date and one true-or-false value per category, nothing that identifies you, and it is never sent to us. Clearing your site data removes it and you will be asked again.
Signing in to the dashboard sets one cookie, strapi_up_refresh, on our API's address. It keeps you signed in: no script can read it, it lasts at most 30 days (14 without use), and signing out ends it. It is strictly necessary for the sign-in you asked for, so it does not depend on the consent bar. The dashboard also keeps a short-lived sign-in token in your browser's storage, which stops working within minutes.
That bar offers Reject all and Accept all as equally prominent choices, plus a panel for deciding category by category. Nothing optional is pre-selected, and giving no answer is treated as a refusal rather than as permission. You can change or withdraw your answer at any time through the Cookie settings link in the footer of every page.
Two of the three categories in that panel — audience measurement and advertising — hold nothing today, and the panel says so under each rather than implying otherwise. We keep the mechanism anyway, because the ability to ask has to exist before there is anything to ask about. If either category ever gains something, the panel is where it will be named, this section is where it will be described, and you will be asked again rather than carried over on an answer you gave about something else.
The Tunnel dashboard at app.tunnelpowered.com is a separate application, and uses browser storage strictly to keep you signed in.
23.Age
You must be 18 or older to have an account: an account is a contract, and Limit commits your money. You confirm your age when you sign up. If you believe someone younger has given us personal data, tell us and we will delete it.
24.Changes to this policy
When this policy changes, we post the new version on this page with its date, and the next time you sign in we show you what changed and ask you to accept it before you continue.
25.How to contact us about privacy
For any question or request about this policy or your personal data, write to our data protection officer:
"STILL BETA TECH" SRL - Data protection officer
MD-2093, str. Mihai Viteazul 28, s. Hulboaca, mun. Chișinău, Republic of Moldova
tunnelpowered.com