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.
Data processing agreement
Last updated 10 October 2026
This data processing agreement (“DPA”) is part of the terms of service between Flair Digital, UAB and the business that uses Flair Clients. It applies automatically when you create a workspace or subscribe. It meets Article 28 of the EU General Data Protection Regulation (“GDPR”).
Need a signed copy for your records? Write to [privacy email] and we will countersign this text. If this DPA and the terms differ on personal data, this DPA applies.
1. Parties and how this applies
“Customer” means the business that holds the workspace. “We” or “processor” means Flair Digital, UAB, company code [company code], [address], Vilnius, Lithuania. “Customer data” means the personal data in the customer’s workspace that we process to provide the Service. Words such as controller, processor, processing, personal data breach and supervisory authority have the meaning given in the GDPR.
2. Roles
The customer is the controller of customer data and we are its processor. The customer is responsible for having a lawful basis for the data it puts into the Service and for telling its people about it. For account, billing and website data we are the controller ourselves; that is covered by our privacy policy, not this DPA.
3. Instructions
We process customer data only on the customer’s documented instructions, including for transfers outside the EEA, unless EU or member state law requires otherwise (in which case we tell the customer first, unless that law forbids it). The instructions are: the terms and this DPA, the settings the customer chooses in the Service, the services it connects, and any other written instruction we agree. We tell the customer straight away if we think an instruction breaks data protection law.
4. Confidentiality of our staff
Only people who need it to run, support or secure the Service can access customer data. Each of them is bound by a duty of confidentiality.
5. Security
We keep appropriate technical and organisational measures in place to protect customer data, as Article 32 GDPR requires. They are listed in Annex 2. We may improve them over time but will not lower the overall level of protection.
6. Subprocessors
- The customer gives general authorisation for the subprocessors on the subprocessors page.
- We bind each subprocessor by a written contract with data protection duties at least as protective as this DPA. We remain responsible to the customer for them.
- We tell workspace admins by email at least 30 days before we add or replace a subprocessor used for every workspace.
- The customer may object on reasonable data protection grounds within that time. If we can’t resolve it, the customer may end the subscription and get a refund of fees paid for the unused period.
- Services the customer chooses to connect (for example Slack, Xero or its bank) act on the customer’s own instruction and under their own terms with the customer.
7. Transfers outside the EEA
Customer data is stored in the EU. Where a subprocessor processes it outside the European Economic Area, we make sure the transfer is covered by an adequacy decision (such as the EU–US Data Privacy Framework for certified providers) or by the European Commission’s Standard Contractual Clauses (2021/914), with extra safeguards where needed.
8. Requests from individuals
The Service lets the customer find, correct, export and delete customer data itself. If that is not enough, we help the customer answer requests from people exercising their GDPR rights. If someone sends such a request to us directly, we pass it to the customer and do not answer it ourselves unless the customer asks us to.
9. Personal data breaches
We notify the customer without undue delay, and in any case within 48 hours after becoming aware of a personal data breach affecting customer data. The notice describes what happened, the kinds and rough number of people and records affected, the likely consequences, and what we have done or propose to do. Where we don’t have all of this at once, we send it as we learn it. We help the customer meet its own duty to notify the supervisory authority and the people affected.
10. Assessments and authorities
Taking into account what we know about the processing, we give the customer reasonable help with data protection impact assessments and with prior consultation of a supervisory authority.
11. Information and audits
We make available the information needed to show we meet Article 28 GDPR. The customer, or an independent auditor it appoints under confidentiality, may audit our compliance with 30 days’ written notice, at most once a year unless a breach or an authority requires it. Audits take place during working hours, avoid disrupting the Service, and respect other customers’ confidentiality. Each side bears its own costs.
12. Return and deletion
Admins can export the main records as CSV at any time, and we provide a complete export on request in a common machine-readable format. When a workspace ends, it stays read-only for 90 days so the customer can export. We then delete customer data, and it leaves our backups within a further 30 days, unless EU or member state law requires us to keep it. An admin can ask for earlier deletion at any time.
13. Liability and term
The limits of liability in the terms apply to this DPA, except where the GDPR does not allow them. This DPA lasts as long as we process customer data for the customer. It is governed by the same law as the terms: the law of the Republic of Lithuania.
14. Annex 1: Details of processing
| Subject matter | Providing Flair Clients to the customer. |
| Purpose | Time tracking and approvals; clients, leads and projects; profit and spend reporting; Ask, the AI assistant; reminders; and the services the customer connects. |
| Nature | Storing, organising, displaying, calculating, sending and deleting, as the customer uses the Service. |
| Duration | While the customer has a workspace, plus up to 90 days to export, then deletion. |
| People concerned | The customer’s team members and contractors; contact people at its clients, leads and suppliers. |
| Kinds of data | Names, work email addresses and roles; hours, notes and approvals; hourly rates and staff costs if entered; client and lead contact details; invoice and billing details; bank transactions (amounts, dates, counterparties, descriptions); calendar event titles and times for people who connect a calendar; Slack user IDs. |
| Special categories | None intended. The customer should not store them unless strictly needed. |
| Subprocessors | As listed on the subprocessors page. |
15. Annex 2: Security measures
Hosting and encryption
- Database and app servers in the EU (Ireland), with providers that hold recognised security certifications.
- Encryption in transit (TLS) for every connection and encryption at rest for the database and backups.
- Daily backups, kept for a limited time and encrypted.
Access
- Each workspace is walled off from all others by row-level security rules in the database, not only in the app.
- Roles inside each workspace (member, manager, admin) limit who sees rates, costs and profit.
- Passwordless sign-in with Google or one-time email links; sessions expire.
- Staff access is least-privilege, protected by two-factor authentication, used only for support or security, and logged.
Application
- Keys for connected services stay on the server and are never sent to the browser.
- Messages from Slack and other services are checked by signature before they are trusted.
- AI requests carry only what the question needs, and go only to providers that don’t store prompts or train on them.
- Company sorting from bank imports (company name and category only; no personal data, amounts or dates) is pooled across workspaces to improve automatic sorting, unless the customer turns this off in Settings.
- Changes proposed by Ask are applied only after a person confirms them.
Operations
- Dependencies kept up to date and security advisories reviewed.
- A written process for handling incidents and notifying customers.