Draft — to be reviewed by a lawyer before launch. Details still to fill in: company code, VAT code, address, email, privacy email, data protection officer, Resend region.
Privacy policy
Last updated 10 October 2026
This policy explains what personal data Flair Digital, UAB handles when you use Flair Clients or visit this website, why, and what you can do about it. We follow the EU General Data Protection Regulation (GDPR) and Lithuanian data protection law.
1. Two roles: yours and ours
Inside a workspace, the agency is in charge. The agency that subscribes decides what goes into its workspace: its team, hours, clients, leads, projects, costs, bank transactions and so on. For that data the agency is the controller and we are its processor: we handle it only on the agency’s instructions, under our data processing terms. If you are a team member or a client of an agency and have a question about your data there, please contact that agency first. We will help them answer.
For accounts, billing and this website, we are in charge. For the data described in section 2, Flair Digital, UAB ([address], Vilnius, Lithuania, company code [company code]) is the controller.
2. What we collect as controller
- Account details: name, email address, and, if you sign in with Google, the basic profile Google shares (name, email, picture).
- Billing details: company name, billing email, address, VAT code, and subscription history. Card details go straight to Stripe; we never see or store full card numbers.
- Technical and security data: IP address, browser, device and time of requests, sign-in events and errors, so we can keep the Service secure and working.
- Messages: what you write when you contact us for support or feedback.
- Product usage: which features a workspace uses and how many active people it has, to bill correctly and improve the Service. We don’t use third-party analytics or advertising trackers.
3. Why we use it
| Purpose | Legal basis |
|---|---|
| Creating and running your account, signing you in | Contract (Art. 6(1)(b) GDPR) |
| Billing, invoices, tax and accounting records | Contract and legal obligation (Art. 6(1)(b) and (c)) |
| Security, preventing abuse, fixing errors | Legitimate interests (Art. 6(1)(f)) |
| Service emails: trial ending, payment problems, changes to terms | Contract and legitimate interests |
| Product news by email | Consent, which you can withdraw at any time |
4. Data inside workspaces
As a processor we use workspace data only to provide the Service to that agency: to store it, show it to the right people, run the features they use and connect the services they choose. We don’t sell it, we don’t use it for advertising, and we don’t use it to train AI models. Our staff access it only when needed to support the agency or keep the Service secure, and that access is limited and logged.
Each workspace is separated from all others in the database itself. Within a workspace, roles (member, manager, admin) decide who can see what, for example rates, costs and profit.
5. AI features
When someone uses Ask, or when bank transactions are sorted automatically, we send the question and the records needed for the answer to an AI model through OpenRouter. We only allow model providers that don’t store prompts or use them for training. Ask can only use data the person asking is allowed to see, and it never changes data without someone confirming.
Shared company list: when a workspace sorts a company in a bank statement import (for example “Figma → Software”), the company’s name and the chosen category count towards a list all workspaces use, once at least three workspaces agree. Only names of companies and their categories are used: never names of people, amounts, dates, or which workspace paid whom. Admins can turn this off in Settings → Money; their choices then stay in their workspace.
6. Who we share it with
We share personal data only with the providers that help us run the Service, listed with their purpose and location on the subprocessors page, with services a workspace chooses to connect, and with authorities when the law requires it. We never sell personal data.
7. Transfers outside the EU
Our database is in the EU. Some providers are based in, or process data in, other countries such as the USA. Where that happens, the transfer is protected by the EU–US Data Privacy Framework where the provider is certified, or by the European Commission’s Standard Contractual Clauses with extra safeguards where needed.
8. How long we keep it
- Workspace data: while the workspace exists. When it ends, it stays read-only for 90 days so the agency can export, then we delete it. Deleted data leaves our backups within a further 30 days.
- Account details: while you have an account, and up to 90 days after it is closed.
- Billing records: for as long as Lithuanian accounting and tax law requires (currently up to 10 years).
- Technical logs: up to 30 days, longer only when needed to investigate a security incident.
- Support messages: up to 2 years after the conversation ends.
9. Security
- All connections are encrypted (HTTPS/TLS) and data is encrypted at rest.
- Workspaces are separated by row-level security rules in the database, so one agency’s data can’t be read from another workspace.
- No passwords: people sign in with Google or a one-time email link.
- Secrets for connected services are stored server-side only and never sent to the browser.
- Access by our staff is limited to what is needed and protected with two-factor authentication.
10. If something goes wrong
If we become aware of a personal data breach affecting a workspace, we will tell the agency’s admins without undue delay, and in any case within 48 hours, with what we know and what we are doing about it, so they can meet their own duty to report within 72 hours. Where we are the controller, we will notify the State Data Protection Inspectorate and the people affected as the GDPR requires.
11. Your rights
You can ask us to access, correct, delete, restrict or transfer your personal data, and you can object to processing based on legitimate interests. Where you gave consent, you can withdraw it at any time. Write to [privacy email]; we answer within one month. For data inside an agency’s workspace, we will pass your request to the agency and help them respond.
You can also complain to the Lithuanian supervisory authority, the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija, vdai.lrv.lt), or to the authority where you live or work.
12. Cookies
We use only the cookies needed to keep you signed in and secure. We don’t use advertising or analytics cookies, so there is nothing to accept. If we ever add optional cookies, we will ask first.
13. Changes and contact
We will post changes here and, for important ones, email workspace admins in advance. Questions about privacy: [privacy email], or by post to Flair Digital, UAB, [address], Vilnius, Lithuania. Data protection officer: [data protection officer].