Teaflask and the GDPR: agreement, role and data location.
Teaflask is a ai services tool. Most customers use it as a processor, it explains how to get its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · free to set up · no card
In short
- Category
- AI services
- Prefilled in the Privacyboard catalog
- Usual role
- Processor
- For most customers
- Data location
- United States
- Often; check your account
- Agreement
- On request
- Obtained through the vendor
What does Teaflask do with personal data?
Support business activities or client services using the provider’s API or services. That is how Privacyboard describes a typical use of Teaflask, as a starting point you can edit.
The data usually involved: documents & attachments, prompts, outputs, any personal data included in API requests
Is Teaflask a processor or a controller?
Most customers use Teaflask as a processor: it handles personal data on their instructions, for the purposes they set. That is the common reading for ai services tools and it is what Privacyboard suggests.
As a processor, it needs a written agreement with you under Article 28, and you should know which subprocessors it uses. Confirm the role against your own agreement, because the way you use a tool can change it.
Where does Teaflask store personal data?
Teaflask is usually associated with United States, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account.
What Teaflask says (read on 19 November 2026): Privacy policy: “Teaflask processes data in the US”; EEA, UK and Swiss data rely on the Standard Contractual Clauses with subprocessors. Foundation model, cloud, payment and analytics providers are in the US. Source: teaflask.com/privacy
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
If the data is processed outside the European Economic Area, Articles 44 to 49 require a transfer mechanism, such as standard contractual clauses, an adequacy decision or the EU-US Data Privacy Framework. Your privacy policy should name it.
Which legal basis usually applies to Teaflask?
The legal basis for Teaflask depends on what goes through it. The legal basis depends on what you send to the provider and why. Use the basis of the activity the AI supports in your register.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Does Teaflask have a data processing agreement?
Checked on 19 November 2026. Vendors change their pages, so check the date.
Teaflask does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy.
What we noted when we opened the page: Teaflask Customer Agreement (updated 28 Oct 2026) by Waffer, Inc. (Delaware, San Francisco): Teaflask is processor for visitors' data, the customer is controller; a DPA is available on request at privacy@teaflask.com. Privacy policy (2 Nov 2026): data processed in the US under the Standard Contractual Clauses; subprocessors listed by category (foundation model, cloud, payment, analytics providers, all US), named list on request. No training on customer data. The embedded code sets no cookies and uses local and session storage keys starting with tf-; optional activity capture (pages, clicks, form entries with sensitive fields redacted) is off by default and skipped when the browser sends Global Privacy Control.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Open the Teaflask reference pageHow to declare Teaflask
- 1
In your privacy policy
Name Teaflask as a recipient, say what it is used for (support business activities or client services using the provider’s API or services) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Teaflask with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Teaflask to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Teaflask
- Decide what personal data may be sent in prompts, and block the rest.
- Check whether inputs are retained or used for training under your plan.
- Record the provider and the purpose in your privacy policy.
- Check for automated decisions about people, which carry extra duties under Article 22.
Free to go online. Pay as you grow.
Free puts you online. Pro adds the DPA generator, vendor monitoring and the MCP connector; Business, security questionnaire autofill and the evidence pack for audits.
Free
Policies, center and banner, online today.
$0 forever
No card, no time limit
Start for free- person
- 1
- domain
- 1
- cookie scan
- By hand
Key features:
- Privacy and cookie policies
- ROPA and vendor register
- DSAR and breach register
- DPIA and TIA screening
- EU AI Act classification
- Privacy center on privacyboard.io
- Cookie banner (CMP) on 1 domain
- And 3 more on the pricing page
No card needed
ProRecommended
Compliance that keeps itself up to date.
$20 per month
Billed $240 a year Save $48
Start with Pro- people
- 2
- domains
- 3
- cookie scan
- Weekly
Everything in Free, plus:
- DPA generator, accepted online
- Vendor monitoring
- DSAR form and replies
- Your own domain
- Weekly cookie scan
- Code monitoring (GitHub)
- Slack alerts
- Google Workspace apps
- MCP connector for your AI
- 2 people
- And 5 more on the pricing page
Cancel any time
Business
Proof for audits and customers, with a team.
$109 per month
Billed $1,308 a year Save $240
Start with Business- people
- 50
- domains
- 10
- cookie scan
- Daily
Everything in Pro, plus:
- 50 seats, role-based access
- Signed agreements, vendors and clients
- Audit log, kept 3 years
- Security questionnaire autofill
- White-label privacy center
- Evidence pack for audits
- Enforced 2FA
- And 6 more on the pricing page
Bank transfer on request
Questions, answered.
Is Teaflask GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Teaflask is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it explains how to get a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Teaflask have a DPA?
Teaflask does not publish the full text of its data processing agreement on a public page. The reference page explains how a customer gets or signs it, usually from inside the account. Article 28 of the GDPR still requires a written contract, so get it and keep a copy. The reference page is https://teaflask.com/agreement/.
Is Teaflask a data processor?
Usually, yes. Most customers use Teaflask as a processor that acts on their instructions. Check your own agreement and how you use the tool, because the role can differ.
Which legal basis applies when I use Teaflask?
The legal basis for Teaflask depends on what goes through it. The legal basis depends on what you send to the provider and why. Use the basis of the activity the AI supports in your register. This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Where does Teaflask store data?
Teaflask is usually associated with United States, but the location can depend on your plan or settings. Privacyboard prefills it as a starting point that you should check in your account. What Teaflask says (read on 19 November 2026): Privacy policy: “Teaflask processes data in the US”; EEA, UK and Swiss data rely on the Standard Contractual Clauses with subprocessors. Foundation model, cloud, payment and analytics providers are in the US. Source: https://teaflask.com/privacy/
Do I need to mention Teaflask in my privacy policy?
Yes, if Teaflask handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Teaflask to my vendor list?
In Privacyboard, pick Teaflask from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
Privacyboard is not affiliated with Teaflask. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.