Privacy Policy

Last updated 31 October 2026

Naratifs (naratifs.com) is a board for creative work: notes, lists, pictures and links pinned like paper. It is run by PT Aplikasi Naratifs Indonesia, a company in Indonesia ("we", "us"). This page says what we keep about you, why, who else sees it, and what you can do about it.

The short version

• What you write on your boards is encrypted in your browser before it is sent. Our server keeps it, but cannot read it.
• We keep only what an account needs: your email address, how you sign in, and the settings that make the app work.
• We do not sell your data, show ads, or use tracking or analytics tools.
• You can delete your account and everything in it at any time, in the app or by asking us.

What we keep

• Your account. Your email address, and either a password (stored only as a one-way hash) or the Google, Apple or Facebook account you sign in with. When you sign in with Google or Facebook, they send us your name, email address and profile picture; Apple sends us only your email address (or, if you choose to hide it, an address of Apple's that forwards to it). We use your email address to identify your account. When you sign in with your organisation's own account (single sign-on, for a school or company that set it up with us), its sign-in system sends us your email address and, if it shares them, your name; your password stays with your organisation. Signing in this way never gives your organisation a way into your boards: they stay encrypted with your own passphrase.
• Your boards, encrypted. Notes, cards, boards, files, chats and Kitt's memory are sealed in your browser with keys only you (and the people you share a board with) hold. We store the sealed data so it syncs between your devices. Without your passphrase or recovery key, neither we nor anyone else can open it, and we cannot recover it for you. While you write a card that others on the board write too, each keystroke, where your caret is and your email address go to them through our server, sealed the same way and not kept. Each card also keeps who added, changed, ticked off or removed it and when (your email address and the time), sealed with it, so everyone on a shared board sees the same Board Activity.
• What sharing needs. The email addresses of people you invite or chat with, who is a member of which board and with what role, and when things changed, so that sharing and syncing work.
• Keys you choose to store with us. An AI service key or a sender email password you save "on the server" is kept in an encrypted vault and used only to make the calls you asked for. Keys you keep "private" stay inside your encrypted workspace.
• Usage of AI you pay for. For each call a Kitt makes to an AI service on your key: when, which Kitt, what kind of step, the model, the number of tokens and the price. Never the words of your boards.
• Payments for Plus. For each order: the email it is for, which plan and period, the amount, its status and the payment provider's invoice number. You pay on Xendit's page, so your card, bank or e-wallet details go to Xendit and its payment partners, never to us.
• Organisations. If you make or join an organisation or a campus on Naratifs: its name, the details it puts on its invoices (legal name, address, tax number, the email invoices go to), the email of each person invited and their role, seat and whether and when they joined, the seats it paid for and its orders, and the email domains it proves it owns (to check one, we ask Cloudflare's or Google's public DNS for its record, sending only the domain's name) with the rule for how people at them sign in. If its own system (such as Okta or Microsoft Entra ID) adds its people through SCIM, that system sends us each person's email, name, an id of its own and whether they are active, and nothing more. Its owners and admins also see how much each person in it uses Kitt from the day they joined (how many calls, tokens and Kitt credits, on which models, by day), never what anyone asked or what Kitt answered, and may turn some of Kitt's features off for its people or cap the credits a person spends a month. It may also set data rules, which your own browser reads before a board leaves it (published, shared outside, copied out, or sent to an outside AI service); when one finds something, its admins see which rule, at which step, on which board, when, and the reason you gave, never the words. It keeps an audit log of what happens in it (your signing in and out with the address you came from, joining and leaving, boards shared and published, settings changed), for 30 to 365 days as it chooses, and may have it sent to its own security monitoring service. Its owners and admins see who is in it, their seats, and how much storage its members use together; never anyone's boards, chats, files or what they do, which stay end-to-end encrypted. Leaving, or being removed, ends your access to the boards its other members shared with you.
• Kitt credits. If you use Kitt’s own models (Kitt 1 Mini, Kitt 1, Kitt Auto): your balance and each entry in it (credits bought, a monthly gift with Plus, what each answer took), with its date and amount. Never the words of your boards.
• Kitt Platform keys. If you make API keys at platform.mykitt.id: each key's name, a short start of it and a one-way fingerprint (hash) of it, never the key itself; when it was made, last used and revoked; and for each call made with it, its model, number of tokens and price. Never what the call sent or what Kitt answered.
• Technical logs. Our hosting providers keep short-lived logs (such as IP address and time of a request) to run and protect the service.

When something leaves the encryption

• AI answers. When you ask a Kitt something, the part of your boards it needs is sent to the AI service you chose (such as Anthropic, OpenAI, Google, xAI or DeepSeek), either straight from your browser or through our server when you use a key stored on the server. Files you attach to a message in a Kitt's chat go too: pictures (made smaller in your browser), PDFs, and the words your browser reads from documents, workbooks and presentations. That service handles it under its own terms. Our server passes it on and does not keep it.
• Kitt's own models. If you choose one of Naratifs' own models, Kitt 1 Mini, Kitt 1 or Kitt Auto (now in a closed trial), what your Kitt sends for that answer, with the pictures you attach to your message (made smaller in your browser), goes from our server to Fireworks AI (United States), which runs the model for us. Fireworks does not store it or use it for training; only the number of words (tokens) of each call is kept, by us and by them, to count use and cost. The same goes for what your own app sends with a Kitt Platform key. When its usual model is down or busy, a second model at Fireworks AI answers instead, the same way. On a board you share, the people you let ask such a Kitt send what they ask the same way, paid from your credits; for that, the name, model and daily limit you set, the nicknames you gave people and your instructions for members (from cards you hid from them) are kept on our server, as for a Kitt on a key stored there.
• Calling a Kitt. If you call one of your Kitts (Plus), your voice and the Kitt's go between your browser and OpenAI (United States), which carries the call, hears you, writes your words down and speaks for the Kitt, on Naratifs' account. To start it, your browser sends our server what the Kitt goes by (its instructions, what it remembers of you, the boards it reads and the chat open now) and its tools, which our server passes on to OpenAI without keeping them. OpenAI does not use what is sent through its API for training. Our server keeps only when each call started and ended, its tokens and its price; what was said is kept in your chat with the Kitt, like the rest of your workspace. A call a Kitt plans for you rings as a notification sealed for your devices; on the Android app it rings as a phone call does, carried by Google's Firebase Cloud Messaging, which gets the app's device token and the call sealed for that phone, never its words.
• Kitt's web searches. If you turn on Search the Web for a Kitt on Kitt's own models, the search words that Kitt writes for a question go from our server to Brave Search (United States), which answers with pages from the web. Nothing of your boards goes with them. Neither the words nor the results are kept by us; each search is counted, with its price, like an answer.
• Sources from a DOI. When you fill a source card from a DOI (Fill From DOI, Cite This PDF, or a Kitt adding a source), your browser sends that DOI, and nothing else, to Crossref (United States), which answers with the work's details. A DOI looked for on a PDF's first pages is found in your browser; the PDF itself never leaves it.
• Reports on Kitt's answers. If you use Report Answer under an answer of a Kitt, we keep what you write there, the model's name and, only if you tick the box for it, that question and answer (nothing else from your boards). The Naratifs team reads them to keep Kitt's answers safe and to test and improve Kitt's models; they are never used to train a model unless you agree to that separately.
• Chats you donate to improve Kitt. If you choose Donate This Chat… in a chat with a Kitt on Kitt's own model and agree to it, we keep your messages and that model's answers in that chat, as words, with the sentence you agreed to. Nothing else is sent: not your boards, files or other chats, nor answers written by another AI service. Once given, that copy is not end-to-end encrypted: the Naratifs team reads it and uses it to train and test Kitt's own models. You can take it back at any time in Account → Donated Chats, which deletes it; a model already trained with it keeps what it learnt, but it is not used again.
• Reports on people and what they share. If you report a message, a person or a shared board, we keep your account, the account you reported, where it was (as ids), the reason and what you write, and, only if you tick the box for it, the words you reported, as your own browser opened them. The report is emailed to the Naratifs team, who use it to act on abuse. The person you report is not told who reported them.
• Notifications. If you turn on notifications on a device (Account → Notifications), we keep the address its browser's push service gave it and the keys that seal notifications to it. A task's reminder is sealed in your browser to your devices before it reaches us, so we send it at its time without being able to read it. Messages in People and group chats, chat requests, boards shared with you and your Kitts' news are notified by our server saying who wrote or what kind of thing it is, never the words. Turn them off there and the device is forgotten; signing out forgets it too.
• On your device. Your browser keeps a copy of your workspace so it opens quickly and works offline. When you sign out, or when another account signs in on the same browser, that copy, its files and what it remembered for you there are deleted from the browser, so the next person never sees them.
• Automations. The rules you set on a board (Automations) are kept with the board, end-to-end encrypted, and run in the browser of whoever does what starts them. When a rule sends a notification or an email, the words you wrote for it, filled in from the board (a card's name, a task, a row), go through our server to the person it is for; a rule's notifications to you and its emails at a time of the week wait on our server until then. When a rule sends to a webhook, what happened (the card, its task or row, who and when) goes through our server to the address you gave, and that service keeps it under its own terms. We count how many each account sends a day, to stop abuse, and keep nothing else of them. A rule that writes in a board's group chat seals its message in the browser like any other there, and a rule that asks a Kitt has it work in the board owner's browser as when you ask it yourself, on the Kitt's own key or Kitt credits. A condition a Kitt judges sends that Kitt what happened and the card it is about, as a short question to its AI service, as when you ask it, and so do words a Kitt writes for a rule and a rule you describe for a Kitt to draw up. When you give a rule its own address, whatever someone sends to it waits on our server, not end-to-end encrypted, until your browser takes it while Naratifs is open, then it is deleted there; anything not taken is deleted after 7 days. We keep the address, its board and rule as ids (and, when you ask for a secret, only its SHA-256 hash), and count how much is sent to it, to stop abuse. A rule that starts before a calendar event reads your calendars in your browser, as the Agenda does; the event is sent nowhere unless the rule itself sends it (in a notification, an email or a call).
• Blocks. If you block someone, we keep that you blocked them, so the server can stop them from chatting with you or sharing boards with you.
• Kitt Cloud. Only if a board owner turns it on, after a warning: the server is given the keys of the shared boards they choose, so a Kitt can work on them while every browser is closed. Those boards are then no longer end-to-end encrypted. Turning it off deletes those keys from the server. For a Kitt on Kitt's own models, the card it checks goes from our server to Fireworks AI the same way as its answers, paid from the owner's credits.
• Emails. Invitations, reminders and news a Kitt sends, and a note to you when your Kitt credits drop below $1 or run out (once each time), are emailed through our email provider. They contain the recipient's address, the sender's name and a short message, and are kept by that provider as email is.
• Link previews. When you paste a link, our server fetches that page to show its title and picture.
• Google and Microsoft cards. When you connect a Google or Microsoft app to a card, your browser talks to them directly. Their sign-in and what the card shows of your files or mail stay in your browser and are not sent to us. Each Google card asks Google only for what that app needs, the first time you use it: a Classroom card never asks for your Drive or your mail. Where you choose a file in Google’s own picker, Naratifs can open only the files you chose. Google Classroom is only read, never changed: your classes, your own work in them and whether you handed it in, their announcements and materials. The next work due that a Classroom card shows, and the to-dos you make from it, are kept with your board, encrypted like the rest. When you ask your Kitt about a Google card, what it reads there goes to the AI service you chose, only to answer you. Naratifs’ use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: it is never sold, never used for advertising, and never used to train AI models.
• GitHub cards. When you connect GitHub to a card, with Sign In with GitHub or a token you made, your browser talks to GitHub directly; the sign-in is kept in that browser only and never sent to us. Kitt reads the code of the repositories you connected there, keeps its changes in your browser until you allow it to push them to a branch of its own, and opens pull requests and issues only after asking you. What it reads of the code goes to the AI service its Kitt runs on, only to answer you. It never reads files that hold secrets, such as .env files and keys. Sign In with GitHub passes through our server once, to turn GitHub's sign-in code into a token for your browser; nothing is kept there. When Kitt runs the code (its tests, its build), after asking you, the repository is copied to a temporary computer in the cloud run for us by Vercel (a Vercel Sandbox): your GitHub sign-in goes through our server to Vercel once, to copy it, and is then taken out of the copy; Kitt's changes are sent there before each command. It reaches only package registries and GitHub, to fetch, and is deleted within 30 minutes or when stopped; we keep nothing of the code, the commands or what they print.
• Calendars you subscribe to. When you subscribe to a calendar by its address (such as your campus e-learning's), the address is kept encrypted with your workspace. Our server fetches that calendar for your browser, because a browser cannot read another site's calendar itself, and keeps nothing of it. Its events stay in your browser unless you make one a to-do on a board.
• Forms you publish. When you publish a data table's form, what it asks (its title, words and questions, with their choices) is kept on our server so anyone with its address can read it, and is not end-to-end encrypted. The answers are: each is sealed in the visitor's browser so only your account can open it, and our server keeps it only until your browser takes it into your table. To stop a form being flooded, the server notes the internet address an answer came from for ten minutes, and how many answers a form took each month.
• Boards you publish to the web. Only if you choose Publish to Web… for a board, after a warning: a copy of what that board shows (its cards, lines and pictures; never cards hidden from members, encrypted notes, Kitts, app cards, comments or version history) is kept on our server, readable by anyone with its address, and is not end-to-end encrypted. While Naratifs is open on your device, changes to the board go to it. Take Down Page deletes the copy and its pictures and files.
• Forms you fill in. If you answer someone's form, your answer is sealed in your browser to the form's owner, so we cannot read it; they can. What they do with it is theirs to answer for, so ask them, not us. We note the internet address you sent it from for ten minutes, to stop floods, then delete it.
• What you share from your phone. Pictures, files and links you share to Naratifs from your phone's Share menu are kept in that browser until you save them to a board, then encrypted like the rest of it.

Why we use it

To provide the service you signed up for: to sign you in, sync and share your boards, send the emails you ask for, make the AI calls you ask for, show you what they cost, take payments for Plus and Kitt credits and keep your plan and balance, keep the service secure, and answer you when you contact us. We rely on your agreement to these terms and on what is needed to provide the service.

Who processes it for us

• Supabase (database, sign-in and file storage; servers in Singapore).
• Vercel (hosting the website and its small server functions).
• Our email provider (sending emails).
• Xendit (taking payments for Plus and Kitt credits, in Indonesia), only if you buy them.
• Google, Apple and Facebook (Meta), only if you sign in with them.
• Your organisation's sign-in system (such as Microsoft Entra ID, Google Workspace or Okta), only if you sign in with your organisation's account.
• The AI services you choose, only for the requests you make.
• Fireworks AI (United States), which runs Kitt's own models, only for the requests you make to them.
• OpenAI (United States), which carries your calls with your Kitts, only if you call one.
• Your browser's push service (Google for Chrome and the Android app, Apple for Safari, Mozilla for Firefox), which carries notifications to your devices, sealed so only your device opens them, only if you turn them on.

These providers may handle data outside Indonesia. We use them only to run Naratifs and choose providers that protect data with industry-standard security.

Cookies and storage in your browser

Naratifs keeps your sign-in session, your settings and a copy of your workspace in your browser's storage so it works offline and opens fast. We do not use advertising or tracking cookies.

How long we keep it

For as long as you have an account. Reports are kept while we look into them and for up to two years after, so we can act on repeated abuse. Deleted cards stay in your Trash until you empty it. When you delete your account, we delete your account and the data stored with it within 30 days, apart from what our providers' backups hold for a short time longer.

Your rights

You can ask to see, correct, export or delete your personal data, or withdraw your agreement, as the Personal Data Protection Law of Indonesia (UU No. 27 Tahun 2022) and similar laws allow. Write to us at the address below from the email address of your account.

Deleting your account and data

In the app, open Account and choose Delete Account…: your account and the data stored with it are deleted at once. If you cannot sign in, email corporate@naratifs.com from the address you signed up with (or the one your Google, Apple or Facebook account uses) and ask us to delete your account; we confirm and delete it within 30 days. What is deleted and what the law has us keep is on Delete Your Account. If you signed in with Facebook, you can also remove Naratifs under Facebook Settings → Apps and Websites; if with Apple, under Settings → your name → Sign in with Apple on your iPhone. Deleting an account that signs in with Apple asks you to confirm with Apple once more, and we then end its Sign in with Apple too.

Children

Naratifs is not meant for children under 13, and we do not knowingly keep their data.

Changes

When this policy changes, we update the date at the top. If a change matters to how your data is used, we tell you in the app or by email first.

Contact

PT Aplikasi Naratifs Indonesia
JL. DR. Soetomo, No. 32-31, RT 000, RW 000, Kel. Gurabesi, Kec. Jayapura Utara, Kota Jayapura, Papua 99222
Phone +62 821-5005-425
Email corporate@naratifs.com
NIB 1910260091254