Skip to content
KIFF kiff.dev
proof tafs download pricing docs Blog see how a card works →
EnglishDeutschFrançaisEspañolItalianoPortuguêsNederlandsPolski

tafs · privacy policy

tafs Privacy Policy

Last updated: 18 November 2026.

This policy explains how tafs, KIFF's app for iPhone, iPad, Android and computers, handles personal data. tafs is part of KIFF Cloud, so KIFF's Privacy Policy applies to it too, and to anything this page doesn't cover. Questions: privacy@kiff.dev.

1. Who we are

tafs is provided by Kiff Agents OÜ, a private limited company incorporated in Estonia (registry code 17372313, VAT number EE102924327), at Tööstuse tn 75-71, Põhja-Tallinna linnaosa, Tallinn 10416, Estonia. The EU General Data Protection Regulation (GDPR) applies to our processing.

2. What this policy covers

The tafs app for iPhone, iPad, Android and computers (Mac, Windows and Linux), and the service behind it, including Setup, which connects a company's tools, and planque, which keeps those connections. In tafs, a company hands a job to an AI agent, a taf, that works inside KIFF Cards.

3. Our roles

We are the controller of your account and sign-in data, and of the operational data of our own service. We act as processor, on your company's behalf, of what tafs keeps for it: each taf's runs, chats, reports, memory notes and the files they deliver. Your company is the controller of that data, and the DPA governs that relationship.

4. What tafs collects

  • Your account: you sign in to tafs with your KIFF account. On a phone or tablet the app keeps your session in the device's Keychain (on Android, its encrypted storage). On a computer it keeps it sealed for your user account: on a Windows PC with Windows' own data protection, on Linux in your keyring, on a Mac in its Keychain. A computer's session lasts up to 90 days.
  • Your device: the app makes a signing key that never leaves the device: in the Secure Enclave of an iPhone, iPad or Mac, the Keystore of an Android device, or the TPM of a Windows PC. On Linux, and on a Mac without a Secure Enclave, the key is a software key kept in your keyring or Keychain, and that computer can show what waits for you but not approve it; you approve on your phone. A Windows PC without a TPM can't sign in to tafs. KIFF keeps the key's public half, the device's name and platform, and when it was added and last used, so it can check your answers to held calls and your approvals of connections.
  • Your watch: a watch holds no password or key, talks only to your paired phone, and never approves. It sends what you say to Coach only as text, through the phone, once you've allowed the AI. The watch's own speech service, Apple's or Google's, turns your words into that text. It can refuse, halt or send to Coach only while it has a screen lock or passcode and is unlocked.
  • Apple Watch: it shows your tafs and their pages without keeping them. It keeps only your Inbox, in a file it can't read while it's locked: each held call as its taf's name and what it asks, never an amount, and Coach's replies to what you sent from the watch, as text. It keeps nothing unless the watch has a passcode. The Inbox goes when your iPhone signs out, or the next time the app opens or closes without a passcode. It makes no recording, and the only notifications it shows are your iPhone's.
  • Wear OS: it shows your account's email, today's calendar and your tafs' pages without keeping them. It keeps your Inbox, where each line is a taf's name and what it says, never an amount, and one message kept for later, as text. Signing out, on the watch or on the phone, clears all of it. For its tile, it also keeps the count of what waits for you, shown only while the watch is unlocked, and cleared when you sign out, or the next time the tile shows while the watch is locked or has no screen lock. After you sign out on the watch, it keeps a note that you did, until you sign in again. The Inbox also goes the next time the app opens or closes while the watch is locked or has no screen lock. A message kept for later stays until you send or delete it, since you asked for it to be sent. The watch keeps no recording. A taf's result can stay in the watch's notifications until you dismiss it or sign out on the watch.
  • Passkeys: when you approve with a passkey on your computer, such as Windows Hello or a security key, your face, fingerprint or PIN stays with the computer's own system. KIFF keeps the passkey's public key, its id, a counter and a name, never anything secret, and refuses a passkey that syncs to other devices.
  • Alerts: on a phone, a tablet or a Mac running the iPad app, when you turn them on, we keep the device's push token with your KIFF person id, and the language the app showed. An alert goes through Apple or Google with only which taf and what it wants, and in a door's alert the name or email address of who wrote in: never an amount or a request's details. The app adds those on the device itself, from KIFF, so an unlocked phone's alert can show an amount, a merchant or a person. On a locked Android phone it shows only "A taf needs you", and on a locked iPhone too, unless you've set its previews to show always. On a Windows PC, a Linux computer or a Mac with the macOS 12 app, alerts are made by the app itself while it runs, with no push token and through no other company. On Windows and Linux they show which taf, what it wants to do, the amount, why and by when; on the macOS 12 app they show KIFF's words for the call, once you turn them on, and a locked screen shows what the Mac's preview setting allows. On Windows they're off until you turn them on, and show only "A taf needs you" while the screen is locked. One shown before the screen locked keeps its details in Windows' notification list. On Linux they're on until you turn them off, and what a locked screen shows depends on your desktop.
  • Language: the tafs service keeps the account's language, from whoever last chatted with Coach, for up to three months, so a taf's reports come in it.
  • Your tools: when you connect a tool, you sign in at the tool's own provider. For an app planque signs in to itself, such as Stripe, or a key you give, planque keeps that token or key for your company, encrypted. For a managed connection, Composio, the connection service planque works with, holds the sign-in, and planque keeps only the connection's record and the tools you approved (see Google user data). KIFF uses managed connections only for the apps named on /subprocessors.
  • Your tafs' work: each taf's runs, chats, reports, memory notes and the files they deliver, held as processor.
  • Purchases: Solo and packs of credits are sold by Apple through the App Store, or by Google through Google Play's billing. They tell us what was bought, for which KIFF account (a random id), when, and their transaction or order references. They don't give us your Apple ID or Google account, name, email address or card.

The app has no analytics or advertising trackers.

5. The AI in tafs

tafs uses Anthropic's Claude AI for Coach and your tafs. The app asks you before anything goes to it.

  • What's sent to it: what you write to Coach and your tafs, the files you attach, what your connected apps return to a taf while it works, and what's on your screen while Coach helps you in the app.
  • What's never sent: the passwords and keys your connected apps use, or your fingerprint.
  • Anthropic uses it to answer and keeps it up to 30 days.
  • Nothing is sent until you allow it. You can withdraw in Account.

When you withdraw, Coach and your tafs stop answering you, and a taf whose runs rest on your consent pauses. KIFF's Privacy Policy has the details.

6. Google user data

When you ask it to, tafs connects a taf to your Google account, for example to your Gmail, or to the Google Calendar or Google Sheets its job uses, in the app's Connect apps. This section says what tafs does with the data it receives from Google.

  • What it reads and writes: what the taf's job needs. In your Gmail, it reads your messages and threads to find the ones that need an answer, and writes drafts; it sends mail only where the taf's Card allows it. In Google Calendar and Google Sheets, it reads the events on the calendars it looks after, or the spreadsheets it keeps up to date, and changes them only where the taf's Card allows it. Anything over the Card's limits waits for your approval.
  • Why: only to do the job you set up for that taf.
  • How each Google app connects:
    • Through our sign-in partner, listed on /subprocessors: Gmail, Google Calendar, Google Sheets.
    • Through tafs's own Google sign-in, with no other company in between: Google Sheets.
    An app named under both connects one way or the other, depending on your account. Google's own sign-in page shows which one you're allowing.
  • What you allow: you sign in on Google's own page and choose what to allow.
    • Through our sign-in partner: tafs asks only for the access the taf's tools need. If that narrower access isn't possible, it asks for the app's usual access, and says so before you sign in. If the usual access would include personal data the taf doesn't use, tafs doesn't connect.
    • Through tafs's own Google sign-in: the sign-in asks for all of the access listed below for that app at once, even when the taf only reads.
  • How a taf uses it: a taf uses only the tools approved on its Card. Every call is checked against a permit for that exact tool and those arguments before anything is sent, and a call outside the access you gave is refused. Which actions ask for your approval each time is set on the Card.
  • The access tafs's own Google sign-in asks for:
    • Google Sheets
      • https://www.googleapis.com/auth/spreadsheets: see, edit, create and delete all your spreadsheets in Google Sheets
    However much a sign-in allows, the taf uses only the tools on its Card.
  • Who keeps your sign-in:
    • Through our sign-in partner: your Google sign-in is kept by our sign-in partner, listed on /subprocessors, and never given to a taf or to planque. Neither the taf nor tafs sees your password or your Google tokens. Another of your tafs that needs the same access reuses the sign-in, and each taf uses only the tools you approved for it.
    • Through tafs's own Google sign-in: planque, tafs's own connection service, keeps your Google token for your company, encrypted with AWS KMS in the European Union (Ireland), and uses it only to make a call the taf's Card allows. It's never given to a taf, and neither the taf nor the AI model sees your password or your Google tokens. Another of your tafs that needs the same access reuses the sign-in, and each taf uses only the tools you approved for it.
  • Who else receives it: what a taf reads from Google goes to the AI model that runs the taf, only once you allow it (see The AI in tafs), which keeps it up to 30 days under its provider's terms.
    • Through our sign-in partner: it also passes through our sign-in partner, which makes each call.
    • Through tafs's own Google sign-in: planque calls Google itself, so no other company makes the call or holds your sign-in.
    Both are listed on /subprocessors.
  • AI training: Google user data is not used to train AI models.
  • Images: tafs doesn't create or edit images or video: its AI writes text. It never uses Google APIs or Google user data to create, edit or share intimate images of anyone (non-consensual intimate imagery, NCII), or any other image of a person.
  • How long, and where: your drafts, events and spreadsheets stay in your Google account. In tafs's own store, what a tool returns is kept only until the taf's run ends. planque, which passes each call on, keeps what Google returns for 24 hours, so a repeated call gets the same answer and is never sent twice; after that it keeps only whether the call was sent. In a chat, what was only read is kept encrypted, used until the chat has been idle an hour and at most four hours after the read, then deleted automatically, within a few days. A run's record and its chat are kept 30 days, and a taf's notes until you remove the taf (see How long we keep it).
  • Stopping it:
    • Disconnect Google in the app, in Connect apps or on the taf's Card tab. Its Google tools stop at once, and tafs asks Google to revoke the sign-in at once; that may complete a little later.
    • Remove a taf, and its connections end with it. A Google sign-in that another of your tafs still uses stays until the last one goes.
    • Remove tafs's access at any time in your Google Account, at myaccount.google.com/permissions. Your tafs stop reaching Google, and the app tells you the Google connection is signed out.
    • Delete your account: its tafs, chats, notes, files and connections are erased at once, and from their point-in-time copies within 35 days, and its Google tokens are revoked where Google allows.

tafs's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

7. Who else receives data

For tafs, we use these companies: Amazon Web Services (hosting, including tafs's store and planque's connections), Clerk (sign-in for KIFF accounts), Anthropic (the AI model), Composio (the sign-ins of managed connections, and the calls planque asks it to make), Apple (push alerts), Google (push alerts on Android, and Google Play's billing), and Resend (a taf's email door). The official, current list, with what each one touches and where, is on /subprocessors.

Some of them are outside the European Economic Area, mostly in the United States. KIFF's Privacy Policy says how those transfers are safeguarded.

8. How long we keep it

  • What your tools return to a taf: only until the run ends. In a chat, what it only read is kept encrypted for its next messages, used until the chat has been idle an hour and at most four hours after the read, then deleted automatically, within a few days.
  • A taf's runs and chats, with a chat's summary: 30 days. Its memory notes: until the taf is removed.
  • Coach's short notes for its next answer, such as why a connection couldn't be made in a chat, or that a Card was approved: until that answer takes them, at most 7 days; after that, as part of that chat, for as long as the chat is kept. A copy is kept 24 hours so that a resent message gets the same note. A chat's note is only used in that chat.
  • Files you attach in a chat: with the message they're attached to, 30 days, or sooner if the chat is removed, and in any case within 38 days. A file no message uses is removed about an hour after you upload it. Deleting your account deletes them.
  • Files your tafs deliver: 30 days from when the run made them, then deleted automatically within a day. Only members of your account can reach them, and the apps don't show them yet.
  • What a tool returned, in planque's record of each call: 24 hours. After that, the record keeps only whether the call was sent, so it is never sent twice.
  • A connection's token or key in planque, or a managed connection's sign-in at Composio: until you disconnect it. The record of its approvals: until the account ends.
  • A device's push token: until you sign out of the app, remove the device, or Apple or Google reports the token gone. A device's public key, name, platform and dates: while you use it; once you sign it out, it's marked removed and kept until the account is deleted, so KIFF can refuse a late answer from it and show which device signed an earlier one. A passkey's public key, id and name: as its device's. A computer's session: up to 90 days, or until you sign out.
  • Your account: until it is deleted. Service logs: 30 days. The stores of tafs and planque keep encrypted point-in-time copies for 35 days, used only to restore a store after a failure.

Everything else is in KIFF's Retention section.

9. Lawful bases

Performance of a contract, to run your account and your tafs. Legitimate interests, for security, fraud prevention and abuse detection. Consent, for the AI in tafs (section 5). Legal obligation, for tax records. KIFF's Privacy Policy has the details.

10. Your rights

Under the GDPR you can ask for access to your data, its correction, erasure, restriction or a portable copy, object to processing based on legitimate interests, and withdraw consent. Email privacy@kiff.dev; we respond within one month. In the app, Account → Export my chats downloads your own chats and notes.

To delete your tafs account, open the app, go to Account and tap Delete account, then confirm. It can't be undone. KIFF's Privacy Policy says what is deleted and when, and how to ask by email.

You can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), or to the supervisory authority where you live.

11. Security, children and changes

Our security measures are on /security. tafs is not directed at children, and we do not knowingly collect personal data from children under 16. We change this policy the way KIFF's Privacy Policy says for its own.

12. Contact

Privacy questions and requests: privacy@kiff.dev. Formal legal notices: legal@kiff.dev. The app's own terms are at /tafs/terms.

KIFF

Limits for AI agents, set by people.

Product Proof Pricing Whitepaper Blog hello@kiff.dev
Build Guard SDK ↗ Docs Framework ↗ llms.txt
Trust Support Security Privacy Terms Acceptable use DPA Subprocessors Cookies SLA Status EU AI Act