Data Processing Agreement
When we host a Flamecloak gateway for you, we process personal data on your behalf. This agreement says what we process, on whose instructions, how we keep it safe, who helps us, and what happens at the end. You accept it when you create a hosted gateway.
Last updated: November 13, 2026
1.The parties
Between the customer named on the account that creates the gateway (the controller, "you") and "STILL BETA TECH" SRL, MD-2093, str. Mihai Viteazul 28, s. Hulboaca, mun. Chișinău, Republic of Moldova (the processor, "we").
This agreement is made under Law No. 195/2024 on the protection of personal data and, where it applies to you, Article 28 of the GDPR. It is part of the Flamecloak service terms.
2.What we process, and why
| Purpose | Running the Flamecloak gateway we host for you: holding the actions your policy names for approval, notifying your approvers, recording each decision, and exporting that record when you ask or when the gateway ends. |
| Duration | For as long as the gateway runs, then as the section on the end of the service says. |
| People concerned | Your approvers and staff; the people on whose behalf your applications request actions; anybody whose data appears in a held request. |
| Data | Approvers' names, email addresses and notification addresses; the public half of each approver's device key, never the private half; the content of requests your policy holds; decision records. Request details only as your approvers allow them, one by one. |
| Special categories | None expected. You tell us before your policy holds any. |
3.Your instructions
We process the data only on your documented instructions. Your policy, and the settings your approvers confirm in the dashboard, are those instructions, including about transfers.
If an instruction would, in our view, break the law, we tell you at once and do not carry it out until you confirm or change it. If a law requires us to process the data otherwise, we tell you first, unless that law forbids it.
4.Confidentiality
Everybody we allow to process the data is bound to keep it confidential, by contract or by law, and sees only what their task needs.
5.Security
Each gateway is kept apart from every other customer's, with its own database. Traffic is encrypted in transit. A decision is bound to the person who made it, on a device they hold, and the record of decisions cannot be changed afterwards. Request details are encrypted at rest by default, unless your approvers choose otherwise. An exported record is encrypted to a key you hold.
Our own backups are encrypted before they reach the disk, and our staff's access to personal data is limited by role and logged.
To protect the machine your gateway runs on, our web server records each request that reaches it: the time, the IP address, the path without anything after "?", the status, size and duration of the answer, the referring site's domain, and the browser's name. We use this record only for the security of our servers (seeing attacks, and blocking the addresses that attack them), as a controller under our own privacy policy, and delete it after 30 days.
6.Sub-processors
You authorise these sub-processors:
| Sub-processor | What it does | Where |
|---|---|---|
| Our hosting provider | The machine your gateway runs on | Republic of Moldova |
| Browser push services (Apple, Google, Mozilla) | Delivering push notifications to approvers who turned them on. The message is encrypted to the approver's own browser, and the push service cannot read it. | United States |
| Telegram | Delivering notifications to approvers who connect it | United Arab Emirates |
Email is sent from our own mail server. Slack webhooks are set up by your approvers and post to your own Slack workspace: Slack is your processor for that, not ours.
We bind each sub-processor to the same obligations as this agreement, and we remain responsible to you for it. We tell you at least 30 days before adding or replacing one, at the account’s login email. You may object on reasonable grounds within that time; if we cannot meet the objection, you may end the service for that gateway without a fee.
7.Transfers outside the Republic of Moldova
Your gateway runs in the Republic of Moldova. Nothing leaves it except a notification an approver turned on for themselves.
The push services and Telegram are outside the European Economic Area and are not on the adequacy list of the National Centre for Personal Data Protection. The basis for these two channels is under legal review; until it is settled, you may turn both off for your gateway and keep email only.
8.Helping you
Requests from the people concerned. You can find every request detail your gateway keeps about one person by an identifier: a user name, an email address or a network address. You can export what was found, or delete it, from the dashboard. A request we receive directly, we pass to you without answering it ourselves.
What deletion cannot reach. Three request details, when your approvers allow them, become part of what an approver confirms: who asked and what changes, the path called, and the names of the body’s fields. They are inside the decision record, which cannot be changed afterwards, so they are kept for as long as the record is kept, and the export lists them. If you do not want a person’s words in a decision record, do not allow those three details.
We help you meet your obligations on security, breaches, impact assessments and prior consultation, as far as the nature of the processing and the information we have allow.
Breaches. We tell you of a personal data breach affecting your data without undue delay, and within 48 hours of becoming aware of it, at the account’s login email and its confirmed notification channels, with what we know at the time and the rest as we learn it.
9.At the end
Before a gateway ends you can export everything it holds about people. When the gateway is deleted, its decision record is exported, checked and encrypted to a key you hold and to our escrow key, and the gateway and its database, request details included, are deleted.
That export is kept for as long as the law requires the evidence in it to be kept, and is not deleted earlier. A copy is given only to your company’s management or to a regulator, on an official written request, and every copy is logged. When that period has passed, we delete it and tell you.
We keep the gateway’s address and the record that it existed, so that its hostname is never given to anybody else.
10.Information and audits
We make available the information needed to show we meet this agreement, including our records of processing for your gateway. We allow and contribute to audits by you or an auditor you mandate, on 30 days’ notice and at most once a year, unless a breach or a supervisory authority requires otherwise.
11.Your obligations
You make sure you have a lawful basis for the data your applications send through the gateway, that your policy holds only what it needs to, and that the people concerned are told what your gateway does.
12.Liability, law and changes
Liability is as in the Flamecloak service terms. This agreement is governed by the law of the Republic of Moldova. A new version is offered in the dashboard and applies to a gateway once you accept it there; until then, the version you accepted applies.