Privacy Policy

1. Who processes your data

For accounts, the service and security, the data controller is Meta Solusi Digital. Data protection contact: support@tauta.id.

Creators who sell products also receive the buyer's name and email for orders in their store, so they can serve their buyers. Creators are responsible for how they use that data outside Tauta.

Forms on creator pages: the creator decides the questions and uses the answers, so for form answers the creator is the data controller. Tauta processes them on the creator's behalf: it stores them, shows them in the creator's dashboard and sends notifications to the creator's email.

The same goes for creators' surveys: the creator decides the questions and uses the answers, so for survey answers the creator is the data controller, and Tauta processes them on the creator's behalf.

2. Data we collect

• Creator account: name, email, password (stored as a hash, never the password itself), preferred language, the terms version you accepted, and when you signed up.
• Profile and content: username, display name, bio, profile photo, page content, social links, short links and their destinations, products, images and files you upload. Content you publish is public.
• Orders: the buyer's name and email, the product, price, payment status, time, language, and the number and time of the last download. We also record the buyer's approximate country and province at checkout, from their internet connection (not the IP address, not the city), so creators can see where their buyers are, and the source of the buyer's visit that day (for example Instagram, WhatsApp or a QR code), so creators know where their buyers came from.
• Payments: the reference number and status from the payment provider. You enter card, bank or e-wallet details directly on the payment provider's page; Tauta never receives or stores them.
• Creator payouts: the bank, account number and account holder name for payouts, and your balance and payout history. The account number is stored encrypted; only its last 4 digits are shown.
• Creator identity check, before the first payout: your full name as on your KTP, your NIK, a photo of your KTP, and a selfie holding it. The NIK and photos are stored encrypted and opened only by the Tauta team to check your identity.
• Content reports: the reason, the details you write, and the page, form or link reported. We don't ask who you are.
• Form answers: what you type or choose when you fill in a form on a creator's page (for example your name, WhatsApp number, email or order), when you sent it, and the page language. We don't store your IP address or browser type with the answers. To refuse duplicate sends and spam, we keep a random code (hash) of the answers and your network that is only used to recognise the same send, and sometimes ask for a bot check (Turnstile). Forms may not ask for passwords, OTP codes, PINs, or card or bank login details. How many people saw, started and sent a form is counted per day, like page statistics.
• Survey answers: what you choose or write in a creator's survey, the questions its logic skipped, the ending shown, your score if the survey is a quiz, how long you took, the campaign name and hidden fields from the link you opened (for example ref=kol1), when you sent it, and the page language. As with forms, we don't store your IP address or browser type with the answers. If a survey takes one answer per person, we keep a random daily code of your network and browser, plus a cookie in your browser, only to recognise a second answer. Anonymous surveys may not ask who you are. How many people saw a survey, started it, reached each question and finished it is counted per day, without the answers.
• Statistics for creators: page views, unique visitors, button taps, link clicks, link previews in chat apps, the name of the site visitors came from, and the campaign name on links creators share (for example in an Instagram story) with the visits, taps and paid orders it brought, plus visitors, button taps and paid orders per source (for example Instagram, WhatsApp or a QR code; paid orders per source only show from 3), approximate country, province and city, device type and app, and hour of visit, all counted per day. Places with fewer than 3 visitors are grouped together so no one can be singled out. We don't store IP addresses, browser user agents, or the full address of the referring page. To count unique visitors, we use a random code (hash) of the IP address and browser type under a key that changes every day, so the same person can't be recognised from one day to the next. The source of a person's first visit that day is kept with that code, until the next day at most, so their taps and orders count for that source. For the dashboard's "now" number, we count roughly how many people opened a creator's page in the last 30 minutes: only a count per 5 minutes is stored, that random code is only held briefly in memory and never stored, and none of it goes into the database.
• Security: to prevent abuse (such as repeated sign-in attempts), we count requests per device under a hashed key, not the IP address. Sign-in sessions store a session token and the browser type, without the IP address. Important actions, such as an order being created or content being suspended, are recorded in an audit log.
• Chat with the Tauta team: the chat is on Tauta's main pages and in the creator dashboard, not on creator pages. We keep the messages and files you send, the team's replies, and the feature suggestions you write. If you're signed in as a creator, the chat also knows your name, email and account id. To help the team answer, we record the address of the page you wrote from (without parts that could hold a secret code), the page title, the name of the site you came from, your browser and operating system, your language and time zone, and your approximate city and country from your network. We don't store your IP address. If the chat knows your email (you're signed in as a creator, or you typed it in the chat), team replies you haven't read are sent to that email.
• Email: we send the emails the service needs, such as order links for buyers and password reset links. If a creator turns it on, we also send a weekly summary of the statistics above (no buyer details); they can turn it off in Settings or with the link in each email. For forms and surveys, the creator gets an email for each answer (with the answer in it) or one digest a day, as they set it.

3. Why, and on what basis

• To provide the service you ask for (basis: performing our agreement): creating your account, showing pages, redirecting short links, processing orders and delivering files.
• To keep the service secure and prevent fraud (basis: legitimate interest): request limits, bot checks, reviewing reports, and audit logs.
• To give creators combined statistics about their pages and links (basis: legitimate interest), without tracking individuals.
• To answer your questions in the chat and record feature suggestions that improve Tauta (basis: legitimate interest; for creators, also performing our agreement).
• To measure Tauta's own ads on Facebook and Instagram (basis: your consent): only if you press Allow on the ad measurement notice. See sections 4 and 7.
• To meet legal obligations, such as keeping transaction records and responding to official requests from authorities.
• Anything else only with your consent, which you can withdraw at any time.

We don't sell personal data. Buyer data, orders and creators' page content are never used for advertising.

4. Who receives data

• Cloudflare: hosting the app, the database, file storage, bot checks (Turnstile) and sending email.
• Helpo, Meta Solusi Digital's own chat app: where the Tauta team reads and answers chats. Helpo also runs on Cloudflare, and feature suggestions go on to the team's internal work tool.
• Mayar: processing payments. To create a payment, we send the buyer's name and email, the product and seller name, the amount and the order number. For a Pro purchase, we send the creator account's name and email.
• Banks: to send a payout, we use the account holder name, bank and account number.
• The selling creator: the buyer's name and email for orders in their store.
• The creator who owns a form: everything you send through it, in their dashboard, in notification emails and in a CSV file they can download. If the form continues to WhatsApp, a message with your answers opens in the WhatsApp app and is only sent when you press send yourself.
• The creator who owns a survey: everything you send through it, its summary, notification emails and a CSV file they can download. In the summary, groups of fewer than 3 people are not shown as a number or percentage.
• Meta (Facebook and Instagram), only with your consent: when you open a Tauta marketing page, claim a page name, create an account or publish your page for the first time, our server sends that event to Meta with your email and account id hashed (SHA-256, which can't be turned back into the address), the browser id and ad click id from the _fbp and _fbc cookies, your IP address and browser type. We don't store the IP address. The purpose is measuring and optimising Tauta's own ads. No Meta script runs on any page, and nothing is sent from creator pages, stores or orders.
• Authorities, when the law requires it.

These providers process data for us under our agreements with them and their own privacy policies.

5. Where data is stored

Data is stored on Cloudflare's infrastructure. The database and files are currently in the Asia-Pacific region, and requests are served by Cloudflare's network in many countries, so data may be processed outside Indonesia. We make such transfers in line with the UU PDP rules on cross-border transfers of personal data.

6. How long data is kept

• Account and content: while your account is active, until you ask for deletion.
• Form answers: until the creator deletes them or the form, or until the auto-delete period the creator chose (for example 90 or 180 days). Answers deleted from the inbox are gone for good within about an hour. If the creator's account is deleted, all their forms and answers are deleted with it.
• Survey answers: the same as form answers. A survey the creator deletes takes all its answers and numbers with it. The one-answer-per-person cookie lasts a year; the random daily code changes every day.
• Daily statistics: 400 days, then deleted automatically.
• Unique-visitor codes: two days at most (today and yesterday).
• Request-limit counters and duplicate-order protection: about one day.
• Sign-in sessions: until you sign out, or after 7 days without use.
• Chats: messages and chat data are kept until you ask for deletion.
• Orders and payment records: 10 years, as tax record-keeping rules require.
• Identity checks: if not approved, the NIK and photos are deleted at once. If approved, they're kept while your account is active, as evidence for payouts already sent, and then as the law requires.

7. Cookies and browser storage

• Session cookie (signed-in creators): keeps you signed in. Only the server can read it.
• Order cookie (buyers): reopens your order in the same browser. Lasts 90 days and is only sent to that order's page.
• tauta_kampanye (7 days): the campaign name on a link you opened, for example a link in a creator's Instagram story. Only sent to that creator's pages, so your visit and order count for that campaign. It holds the campaign name only, nothing about you.
• tauta_survei_… (1 year): only on surveys that take one answer per person, set after you send your answers so the survey knows you've answered. It's only sent to that survey's address and holds nothing but that mark.
• Cloudflare Turnstile on the sign-up and report forms, and on creator forms and surveys when many answers arrive in a short time: checks that you're not a bot.
• Your language choice in the app is stored in your browser (localStorage).
• helpo:… (localStorage): your chat code and the last account id the chat was told, so your conversation is still there when you come back and nobody else using the same browser reads it. For creators, both are deleted when you sign out.
• tauta_ads (180 days): your choice on the ad measurement notice, Allow or Decline.
• _fbp and _fbc (90 days), only after you press Allow: a random id for this browser and the Meta ad click id that brought you to Tauta. Both are Tauta's own cookies and are deleted if you decline.

We don't put third-party ad scripts or trackers on any page. You can change your ad measurement choice at any time with the Ad settings link at the bottom of the home page.

8. Your rights

Under the UU PDP, you have the right to:

• be informed about how your data is processed;
• access your data and get a copy;
• correct data that is wrong or incomplete;
• ask for your data to be deleted or destroyed;
• withdraw consent you gave;
• pause or restrict processing;
• receive your data in a common, machine-readable format;
• object to decisions based solely on automated processing;
• sue and receive compensation for violations in the processing of your data.

For form or survey answers, contact the creator who owns it first; they can delete your answer in their dashboard. If they don't respond, you can contact support@tauta.id.

You can do some of this yourself in the app, such as editing your profile, content and language. For anything else, including deleting your account, email support@tauta.id from your account email or the email you used when buying. We may ask for proof that the data is yours, and we respond within the time the UU PDP sets. We may keep data the law requires us to keep.

9. Security

We use encrypted connections (HTTPS), store passwords and access tokens as hashes, keep product files in private storage that only entitled buyers can download, and limit internal access. No system is completely secure. If a personal data breach happens, we'll notify you and the authorities as the UU PDP requires.

10. Children

Tauta is not meant for children. If you're not a legal adult, use Tauta only with the consent of a parent or guardian. Parents who find their child's data being processed without consent can contact support@tauta.id.

11. Changes to this policy

If we add features that collect new data, this policy will be updated first. Important changes are announced in the app or by email. The version and update date are shown at the top of this page.