Privacy policy
Version 1 · Effective 16 November 2026
This policy explains what personal data esnc.app collects, why we collect it, who helps us handle it, how long we keep it, and what you can ask us to do. "Personal data" means any information that is about you or can be linked to you, such as your email address. We follow Indonesia's Personal Data Protection Law (UU PDP, Law No. 27 of 2022).
Who we are and how to reach us
esnc.app is run by PT Senada Dengan Jiwa ("ESNC", "we", "us"). We decide why and how your data is used. Under UU PDP that makes us the data controller: the party responsible for your data.
Email us about privacy questions and requests at privacy@youresnc.com.
The short version
- You can take our DISC tests without an account. To see your result, you give us your email address. Tapping Show my result also means you agree to get ESNC news and offers by email. You can unsubscribe at any time.
- Our app and database run on Google Cloud in Jakarta, Indonesia. Every visit first passes through Firebase Hosting, the Google service that delivers our pages. It runs on Fastly's worldwide network and on Google's own servers, so what you send us, including what you type into our forms, passes through servers outside Indonesia before it reaches Jakarta. Some services that help us are also outside Indonesia. They are listed under "Who helps us".
- We use no analytics tools, no ad trackers and no social media plugins. Visitors get no cookies from us.
- You can ask to see, fix or delete your data at privacy@youresnc.com.
- We do not sell your personal data.
What we collect and why
When you take a test
While you answer, your answers stay in your browser. We receive them only when you tap Show my result. The quick test keeps them in that one browser tab. The full test also keeps a copy that every esnc.app tab in the same browser can open, so you can go on in a new tab or come back later. This copy stays after you close the tab. It is removed when you send the test or tap Start over, and we stop using it 24 hours after your last answer. So on a shared phone or computer, someone who opens the full test in that browser within those 24 hours carries on from your answers and can see the ones you picked, unless they tap Start over. See "Cookies and browser storage".
Two things do reach us while you answer. When you start a test, and when you finish its last question, your browser tells our server, together with a random code for this test run, which test it is and its language. We use this only to count how many people start and finish (see "Usage counts"). And, as on any website, every page you open reaches our server, which logs the request (see "Visit logs").
When you tap Show my result, we save:
- your email address, as you typed it (spaces removed, capital letters made small)
- which test you took (quick or full), the version of the test, and its language (English or Indonesian)
- every answer: for each group of words, the one you picked as most like you and the one least like you
- your scores, your main and second DISC type, and whether two types tied
- the time, and a random code that stops the same test from being saved twice
We save every test you take, retakes too.
We use this to work out your type and show your result, to send your report, and to check and improve the tests (for example, by comparing quick and full test results). Our server works out your scores from your answers. We never use a score sent by your browser.
Your result page
Your result has its own web address with a long random code in it, so nobody can guess it. There is no login: anyone who has the link can open your result. The page shows your types, your scores, which test you took, its language, and whether your report email was sent. It never shows your email address or your answers.
We ask search engines not to list result pages. Our delivery network does not keep copies of them.
If you tap the share button on your result, your phone's own share menu opens, or the link is copied. The link it shares opens a friend's view of your result: it says "Your friend is type …" and leaves out whether your report email was sent, but it shows the same types, scores and profile. The link hides nothing: the same link without "?shared=1" at the end opens the page as you see it. We do not see who you share it with. Anyone you send the link to can see your result.
When you post the link in a chat app or on social media, such as WhatsApp or Facebook, that service opens the page, from your phone or from its own servers, to make a preview card (the box shown under a link). The card shows your type and a one-line summary of it, so everyone who sees the post can see your type without tapping the link. So that these cards work, our robots.txt file (the public list of what crawlers, programs that read web pages on their own, may open) lets crawlers open the shared link, and no other result address. The AI crawlers named in that file stay out of every result. Search engines are still asked not to list a shared page, but another crawler that finds your shared link in a public place, such as Common Crawl's, may keep a copy of it.
If you tap a link from your result page to another website, that website sees only that you came from esnc.app, not the address of your result.
Your email address and your report
Before we save your email address (here and on the join form), our server checks that its domain (the part after the @) can receive mail. To do that, it asks DNS (the internet's address book), through Google Cloud's own DNS service, about the domain only, never your full address. These lookups can reach servers outside Indonesia. If the domain looks like a typo of a popular one, such as "gmial.com", we suggest a fix. That typo check runs on our own server.
You cannot see your result without giving an email address. Above the button you read: "This test is free. In return, we’ll send ESNC news and offers to your email. Tapping Show my result means you agree. You can unsubscribe anytime." When you tap the button, we save a record of your consent: your email address, the version of the wording you saw, the language, where you gave it, the time and, later, when and why you withdrew it.
We then email your report to the address you typed. It holds your type, your strengths, the scent that matches you, links to buy the matching SORA bottles in our Shopee, TikTok Shop, Tokopedia and Lazada stores (both types' bottles if your two types tie), a link to join ESNC's free WhatsApp community chat, a button to your result page, and an unsubscribe link (or, if you unsubscribed before, a link to get news and offers again). Its pictures load from esnc.app and are the same for everyone. We put no tracking pixels in it, and our email service does not record whether you open it or click its links. Our visit logs do record when your result page or unsubscribe page is opened (see "Visit logs"). If sending fails, we try again for up to 23 hours. We send at most 3 reports to one inbox in an hour. If you take more tests in that hour, we still save them and show your results, but we do not email them.
If someone else types your address. We do not send a confirmation email first. So if someone types your address without asking you, you get the report, and our records show consent for your address. If that happens, tap Unsubscribe in the email, or write to privacy@youresnc.com and we will delete it.
Emails that bounce or are marked as spam. If an email to you can never be delivered, or you mark one as spam, our email service, Resend, puts that exact address on its own block list and sends nothing more to it, reports included, until we take it off the list. Your tests and results stay.
News and offers. Right now the only email we send is your report. When we start sending news and offers, they will come by email and be about ESNC's own scents, offers and ESNC Society. We will not send offers from other companies, and we will not give your email address to them. If you still get them after you unsubscribe, write to privacy@youresnc.com.
Replies. If you reply to one of our emails, your reply goes to ESNC's mailbox on Google Workspace, Google's email service for companies. We then have your email address, the name your mail app shows, what you wrote, and any part of our email you quote.
One inbox, many spellings. Some email addresses reach the same inbox. For example, r.ani+test@gmail.com and rani@gmail.com both reach Rani's Gmail. For our email limits, for unsubscribing and for the order numbers on join requests, we treat them as one inbox. We still store and email the spelling you typed.
When you ask to join ESNC Society
The join form asks for your name, email address, Indonesian WhatsApp number, the marketplace you bought from (Shopee, TikTok Shop, Tokopedia or Lazada), and 1 to 10 order numbers. Before saving, we check your email's domain as described above. Our admins (staff with the admin role) later add a status, a short note, who handled your request and when, and, if you became a member, the day your membership starts: the date of the order that brought your spending to the amount needed to join.
As the form says, we use these details only to check your orders and contact you about ESNC Society. Sending this form does not sign you up for news and offers. Only signed-in ESNC admins can see your request. Other staff, such as the hosts who run our sessions, cannot. From your request, admins can start an email or a WhatsApp chat with you.
Checking your orders. AHA is ESNC's order system (see "Who helps us"). When an admin presses Check with AHA on your request, our server sends AHA only the marketplace and your order numbers, never your name, email address or WhatsApp number. AHA tells us whether each number is an ESNC order and, if it is, its status, when it was ordered and what was in it. We save each answer with your request, with the time of the check and which admin ran it. If another join request holds the same order number, the admin also sees that request's name, date and status, and whether it came from the same email address and WhatsApp number. AHA does not send order amounts yet, so our admins add up your orders by hand in the marketplace's seller center (the pages where ESNC sees its own orders on that marketplace). The marketplaces hide the buyer's details there (they show as ***), so our admins can only confirm that the order is real. They keep no copies outside our app. As the join page says, our team contacts you on WhatsApp.
One inbox per order number. An order number can back the request of only one inbox (see "One inbox, many spellings"). When you send the form, we record that your request claimed each of its order numbers, and when. If a request from another inbox uses one of them, we refuse it and tell that person only that a number is already in another join request, never which number or whose. A claim stays until your request is deleted, or until we release your request's claims by hand, all at once, for example after checking who placed an order. Releasing them also clears the start date of a membership that rested on them.
If you are ESNC staff
Staff sign in with their Google account through Google Firebase Authentication. We store the staff member's email address, their roles (host, admin or links), their Firebase user ID (a code Firebase gives each account), when the account was added, which join requests they handled, and which order checks with AHA they ran, and when. When someone leaves our staff, we remove their roles but keep their email address and Firebase user ID, so the requests they handled and the checks they ran still show who did them.
We also keep a history of every staff role added or removed: whose role it was (their email address), which role, when, and who made the change (their email address), or that it was made with one of our background jobs. Nothing deletes this history on its own, and an address typed wrong stays in it too. Staff with the links role edit our Links page. We keep a history of every change made there: which item, what it was before and after the change, when, and who made the change (their email address). Staff with the links role see the latest changes, with that email address. Nothing deletes this history on its own, and it keeps the email address after that person leaves our staff. Only admins see join requests, so other admins can see who handled each one. Admins can also open the staff list, which shows every staff member's email address and roles.
Staff are normally added and removed on the staff list page. When we add or remove a staff member with one of our background jobs (programs we run on Google Cloud) instead, their email address is also kept in Google Cloud's record of that job run, in Jakarta (see "How long we keep it"). Signing in sets one cookie, described under "Cookies and browser storage".
If anyone tries to sign in to the staff area with Google, Firebase keeps a basic record of that Google account (email, name, profile photo link, account ID and sign-in times), even if the person is not on our staff list and is turned away. These records stay until the person asks us to delete them. We then delete them by hand in the Firebase console, and Firebase clears them from its systems within 180 days. Firebase also records the IP address and browser details used to sign in, to guard against abuse, and keeps the IP address for a few weeks.
Technical data
- Visit logs. Google Cloud keeps a log of requests to our app: the page address, the time, your browser type and the page you came from. It can also include your IP address (the number that identifies your internet connection). Page addresses can include your result link or an unsubscribe link. These logs stay in Jakarta for 30 days. Firebase Hosting, which delivers our pages, also keeps the IP addresses of visits for a few months, to detect abuse and to report usage. Google sets this period.
- Our own app logs. Our app is written to leave visitors' email addresses and IP addresses out of its own logs. They hold short notes on what happened, internal codes, counts and error details. When we add or remove a staff member with one of our background jobs instead of the staff list page, they also record that person's email address. These logs stay in Jakarta for 30 days.
- Abuse limits. To stop abuse, we count requests per hour from each IP address (for example, at most 100 tests an hour), the reports sent to each inbox, and the uses of each "Send me ESNC news again" link. For staff, we also count some actions per staff member, such as order checks and staff list changes. We store each count with a one-way scrambled code (a hash) of the IP address, inbox, link or staff account, never the address itself. This is not fully anonymous: someone who already knows your address could check it against the code. Each count covers one hour, and we delete it once that hour began more than 2 hours ago.
- Usage counts. To see how many people start a test, finish it and give an email, we store a random code for each test run, the step reached, the test, the language and the time. We store no email or IP address with them. Someone with access to our database could still match them to your test by the time, so we treat them as personal data.
- Taps on our Links page. When you tap a link on our Links page (esnc.app/id/links), your browser tells our server which link it was. We add one to that link's count for the day and store nothing else: not your IP address, not your browser, and not the app you came from. Like any request, the tap also appears in our visit logs for 30 days (see "Visit logs"), but they don't show which link you tapped.
- Bot check. On the email page and the join form we use Cloudflare Turnstile to tell people from bots. Cloudflare's script loads as soon as the page opens, runs in your browser, and sees your IP address and some information about your browser and device. Our server also sends your IP address to Cloudflare to confirm the check. Our own server does not log your IP address for this, but Cloudflare keeps records of these checks for us, and our Cloudflare account can show the IP addresses that ran the most checks.
What we learn from others
- AHA, ESNC's order system, tells us, for each order number our admins check, whether it is an ESNC order and, if it is, its status, when it was ordered and what was in it.
- The marketplace you bought from shows our admins, in its seller center, the orders you list, with the buyer's details hidden. They look them up there to add up what you spent, to find the day your membership starts, and to check an order when someone else says it is theirs (see "Checking your orders").
- Cloudflare tells us whether your browser passed the bot check.
- Google tells us, for staff, the email address and account ID of the Google account used to sign in.
Your DISC type is worked out automatically
Your DISC type is a profile our server works out from your answers, by a fixed formula, with no person involved. We use it only to choose the scent we show you and the text of your report. Nothing else depends on it: not prices, not ESNC Society membership, and no staff decision. The staff pages in our app do not show test results. Our email service sees your type only inside your report email. It is not saved as a detail of your contact there. We do not use your type to choose which news and offers you get. If we ever want to, we will update this policy and tell you first.
If you do not want this, you can object at privacy@youresnc.com. Because the type is the result of the test, we will then delete your tests.
Our legal basis
- Your request for your result, when you tap Show my result: to save and score your test, show your result and email your report (UU PDP, Art. 20(2)(b)). The same tap gives your consent to news and offers (UU PDP, Art. 20(2)(a)). If you unsubscribed before, we still save your test and send your report, but we record no new consent.
- Checking and improving the tests (for example, comparing quick and full results): our legitimate interest in making the tests accurate (UU PDP, Art. 20(2)(f)). We use only the tests already saved.
- Join requests: your request to join, which we act on before you become a member, and then your membership (UU PDP, Art. 20(2)(b)). This covers checking your order numbers with AHA and keeping the date your membership starts. Keeping each order number tied to the first request that sent it, so one order cannot back two people's requests: our legitimate interest in preventing misuse (UU PDP, Art. 20(2)(f)).
- Staff accounts: our legitimate interest in letting only our staff into the staff area, and in knowing who handled each request, who checked each order with AHA, who gave or took away each staff role, and who changed our Links page (UU PDP, Art. 20(2)(f)).
- Security, abuse limits, the bot check, usage counts and logs: our legitimate interest in keeping the service safe and knowing how it is used (UU PDP, Art. 20(2)(f)).
- Keeping proof that you withdrew your consent after we delete your data: our legitimate interest in being able to show that you gave and withdrew it (UU PDP, Art. 20(2)(f)). While we use your data, UU PDP requires us to be able to show proof of your consent (Art. 24).
When you withdraw consent, we stop from then on. It does not undo what we did before.
Who helps us, and where they are
We use these services. The table says what each one gets.
Google Cloud (Cloud Run, Cloud SQL, Secret Manager, Cloud Logging)
- What it does for us
- Runs our app; stores the database, backups and visit logs
- What it gets
- Everything described above
- Where
- Jakarta, Indonesia
Google Cloud audit logs
- What it does for us
- Records changes ESNC makes to its cloud setup
- What it gets
- Staff email addresses, with the IP address and the browser or tool used for each change; our cloud settings; the scrambled code (hash) used when we delete a person's data; and the code of a join request when we release the order numbers it claimed (the code only, no order number, name or email)
- Where
- Google's global systems, not limited to Indonesia. Kept 400 days, a period Google sets
Google Firebase Hosting
- What it does for us
- Delivers every page. Every visit passes through it first, and the secure connection ends there
- What it gets
- Every request, including what you type into our forms. It keeps copies only of public pages, such as the home page and this policy
- Where
- Worldwide, on the network of Fastly, Inc., a US company, and on Google's own servers, so also outside Indonesia
Resend
- What it does for us
- Sends our emails and keeps our mailing list
- What it gets
- Your email address, the full report email (your type, scent and result link), whether you unsubscribed, and whether emails to you were delivered. No name
- Where
- United States, where Resend stores all its data. The email itself may be sent from Resend's servers in another country
Google Workspace (Gmail)
- What it does for us
- Holds ESNC's mailbox. Replies to our emails arrive there
- What it gets
- If you reply to one of our emails: your email address, the name your mail app shows, what you write, and any part of our email you quote
- Where
- Google's systems worldwide, which can be outside Indonesia
AHA, ESNC's order system
- What it does for us
- Checks whether an order number on a join request is a real ESNC order, when our admins press Check with AHA
- What it gets
- Only the marketplace and the order numbers. No name, email or WhatsApp number. It answers whether it found each order and, if it did, its status, date and items, and we keep that answer with your join request
- Where
- AHA's server runs on Google Cloud in Jakarta, Indonesia. AHA keeps these records only for ESNC's internal use, never sells them, and keeps them confidential
Cloudflare Turnstile
- What it does for us
- Bot check on the email page and the join form
- What it gets
- Your IP address and some information about your browser and device
- Where
- Not stated for Turnstile. Cloudflare's general privacy policy says it mainly stores data in the United States and the European Economic Area, and may access it from other countries
Google Firebase Authentication
- What it does for us
- Staff sign-in
- What it gets
- The Google account details of anyone who signs in to the staff area
- Where
- United States
DNS (the internet's address book)
- What it does for us
- Says whether your email's domain can receive mail
- What it gets
- Only the domain, not your address
- Where
- Google Cloud's DNS service, then wherever that domain's servers are
Cloudflare also manages esnc.app's domain name records (DNS). It does not carry your visits to our pages.
Inside ESNC. Only admins, the staff who handle join requests, see them. When an admin checks a request with AHA, they also see AHA's answers and any other request that used the same order number, with its name, date and status. Admins also see the staff list: each staff member's email address and roles. Hosts, who run our sessions, and staff who only edit our Links page see neither. Staff with the links role see the items on our Links page, how many taps each link had, and the latest changes, with the email address of whoever made each one. Only the one person at ESNC who runs our Google Cloud account can open the database and the logs. Apart from the services in the table, nobody outside ESNC can see this data.
Transfers outside Indonesia. Every service in the table that is not in Jakarta means some of your data leaves Indonesia. UU PDP allows this under three conditions, checked in order: the receiving country protects personal data at least as well as UU PDP; if it does not, there are adequate and binding safeguards; and if neither applies, we need your consent (UU PDP, Art. 56). The authority that is to assess transfers abroad (UU PDP, Art. 60) has not been set up yet, so no country has been officially found to protect data as well. We therefore rely on binding safeguards: each company's data protection terms, which oblige it to protect the data it handles for us. These are Google's Cloud Data Processing Addendum (it covers Google Workspace as well as Google Cloud), Firebase's Data Processing and Security Terms, Resend's Data Processing Addendum and Cloudflare's Data Processing Addendum, which Cloudflare makes part of every customer's agreement. Google and Cloudflare also use some of this data for their own purposes: Google keeps Firebase Hosting IP addresses to detect abuse, and Cloudflare uses bot-check signals to improve Turnstile. For that use, their own privacy policies apply.
Links to other services. Our store links open Shopee, TikTok Shop, Tokopedia or Lazada, and our Links page also opens ESNC's Instagram, TikTok and Threads accounts and our shop at youresnc.com. What you do there falls under their own privacy policies, not this one. Our community link, on your result page and in your report, opens ESNC's own WhatsApp community, which ESNC runs and where we post announcements. WhatsApp's privacy policy covers how WhatsApp handles your data. If you join, ESNC can see your phone number and WhatsApp name. Other members may see them too, depending on the kind of group, as WhatsApp sets it.
WhatsApp chats with ESNC. Some buttons on our Links page open a WhatsApp chat with ESNC's number, sometimes with a message already written for you. The Custom Gifting message, for example, asks for your full name, the kind of event, about how many pieces you need and the event date. Nothing is sent until you press send in WhatsApp, and you can change or delete the text first. What you send reaches ESNC on WhatsApp, and WhatsApp's privacy policy covers how WhatsApp handles it.
We use no analytics tools, ad trackers, tag managers or social media plugins. Our fonts, photos and logo are served from esnc.app, so your visit does not load them from Google Fonts or anyone else.
How long we keep it
Your tests
- How long
- Until you ask us to delete them
Your consent records
- How long
- Until you ask us to delete them, except the one record in the next row
Proof that you withdrew, kept after deletion
- How long
- No end date. It stays after your data is deleted, as proof
Join requests
- How long
- Until you ask us to delete them
AHA's answers about your order numbers
- How long
- As long as your join request: until you ask us to delete it. We keep every check, with when it ran and which admin ran it
Your claim on each order number
- How long
- As long as your join request, or until we release it sooner by hand, for example when someone shows that an order is theirs. A release frees every order number on that request at once. Your request then stays, but releasing also clears its membership start date. A claim holds the marketplace, the order number, which request it belongs to and the time, not your name or email
Usage counts
- How long
- No end date. Not deleted, even when you ask us to delete your data
Abuse-limit counts
- How long
- About 2 hours. Each count covers one hour, and we delete it once that hour began more than 2 hours ago, whether or not you ask us to delete your data
Staff accounts
- How long
- When someone leaves our staff, we take away their staff roles, on our staff list page or with one of our background jobs. Their record stays: their email address, their Firebase user ID (once they have signed in) and when it was added, so the join requests they handled and the order checks they ran still show who did them. A request to delete your data as a visitor leaves it alone, and nothing removes it on its own. A former staff member can ask us to delete it, and we then delete it by hand. Their email address stays in the history of changes to our Links page, even then
History of staff changes
- How long
- No end date. Each time someone gets or loses a staff role, we record their email address, which role, when, and whether the change was made on our staff list page or with one of our background jobs. For a change made on the page, we also record the email address of the staff member who made it. If we type an address wrong when adding someone, that address stays in this history and in our staff records. Nothing deletes it on its own
History of changes to our Links page
- How long
- No end date. For each change: which item, what it was before and after the change, when, and the email address of the staff member who made it. It stays after that person leaves our staff. Nothing deletes it on its own
Visit logs
- How long
- 30 days. Firebase Hosting keeps the IP addresses of visits for a few months, a period Google sets
Tap counts on our Links page
- How long
- No end date. One number per link per day, with nothing about who tapped. Deleted with its link
Database backups and recovery logs
- How long
- About a week. We keep the 7 most recent daily backups, and recovery logs for up to 7 days. Older ones are removed automatically
Google Cloud audit logs (staff changes)
- How long
- 400 days
Google Cloud's record of each run of our background jobs, in Jakarta
- How long
- Until 1,000 newer runs of the same job have replaced it (Google then removes it on its own), or until we delete it by hand. It holds what we pass to the job: the email address of a staff member we add or remove, the scrambled code (hash) of an email whose data we delete, or the code of a join request whose order numbers we release
Resend's contacts, its log of sent emails and its block list
- How long
- Contacts: until you ask us to delete your data. Log of sent emails: for the period Resend sets (30 days on its standard plans). Block list: until we take the address off it
Firebase's records of Google accounts that signed in to the staff area
- How long
- Until the person asks us to delete them. Firebase then clears them from its systems within 180 days. It keeps the IP addresses it logs at sign-in for a few weeks
Staff sign-in cookie
- How long
- 12 hours, or until the staff member signs out
Answers kept in your browser tab
- How long
- Until your test is sent, or you close the tab
A copy of your full test's answers in your browser's local storage
- How long
- Until your test is sent, or you tap Start over. We stop using it 24 hours after your last answer, and the full test page removes it the next time it opens in that browser, or when you clear esnc.app's data in your browser. We never receive this copy: your answers reach us only when you tap Show my result
How we protect it
- The database, its backups and our secret keys stay in Jakarta, on Google Cloud. Only our app, our two background jobs and the one person at ESNC who runs our Google Cloud account can reach the database. One job runs every 10 minutes: it re-sends report emails that did not go out, tells Resend about unsubscribes it missed, and deletes old abuse-limit counts. We also use it to carry out deletion requests. The other job updates the database before each new version of the app goes live. We also use it to add or remove staff, and to release order numbers that a join request claimed. Our automatic deploys on GitHub install the code that the app and these jobs run, and can start the jobs, so whoever can change our private code on GitHub can also change what happens to your data.
- Your browser never talks to the database. Only our server does.
- esnc.app works only over encrypted connections (HTTPS).
- Staff sign in with Google. Every staff page and staff action checks the sign-in and the staff role again.
- Unsubscribe and resubscribe links carry a digital signature, never your email address.
- Our forms refuse requests that another website tries to send from your browser.
- Our app's own logs leave out visitors' email addresses and IP addresses.
- Limits and a bot check make it harder to misuse the service.
No system is perfectly safe. If we fail to protect your personal data (for example, it leaks, is lost or is changed without permission), we will tell you in writing within 3 x 24 hours, that is 72 hours (UU PDP, Art. 46). We count those hours from when we find out. We will say which data was exposed, when and how, what we are doing about it, and who to contact at ESNC. UU PDP also requires us to tell the authority for personal data protection. As of October 2026 that authority has not been set up. Until it is, we will tell the Ministry of Communication and Digital Affairs (Komdigi). If the failure seriously affects the public, we will also tell the public.
Your rights
Under UU PDP you have the right to:
- Know who we are, what we collect, why, and on what basis. This policy is our answer.
- See your data and get a copy.
- Fix data that is wrong or incomplete.
- Delete your data, or ask us to stop using it.
- Withdraw your consent at any time.
- Object to decisions made only by a computer, including profiling such as your DISC type.
- Pause or limit how we use your data.
- Take your data with you in a common format that computers can read, or ask us to send it to another company, as long as both systems can exchange it safely (UU PDP, Art. 13).
- Complain to the personal data protection authority. Under UU PDP, the President sets it up (Art. 58 to 60). As of October 2026 it has not been set up. You can also go to court or to arbitration, and claim compensation if we break the law (UU PDP, Art. 12 and 64).
How to use them. Write to privacy@youresnc.com from the email address you used with us. If you write from another address, we will email the address you used with us and ask you to confirm from there. When you ask us to fix your data, show it to you, stop using it after you withdraw consent, or pause or limit how we use it, we act within 3 x 24 hours of receiving your request, as UU PDP requires (Art. 30, 32, 40 and 41). For a copy of your data or a deletion, UU PDP sets no deadline. We still reply within 3 x 24 hours and tell you when it will be done. When we delete your data, we tell you once it is done (UU PDP, Art. 45). This is free.
Unsubscribing. Tap Unsubscribe in any of our emails, then tap the Unsubscribe button on the page that opens. Opening the page alone changes nothing. You can also use your mail app's own unsubscribe button. This stops news and offers to every spelling of your inbox. If you take a test again later, you still get your result and your report, but no news and offers. To get them again, tap Send me ESNC news again in a report we sent after you unsubscribed, and confirm. The link works for 30 days after the test that report belongs to. After that, take a test again: your new report has a new link.
Deleting. When you ask, we delete your tests, your join requests and your consent records, and we delete your contact at Resend. With your join requests go AHA's answers about their order numbers and their claim on those numbers, so anyone can send those order numbers again. If you are a member, the date your membership started goes too. Your result links stop working, the shared link too. If you shared your result, a preview already shown in a chat (your type and a short line about it) stays there, and a service that fetched the shared page, such as a chat app making a preview, may keep its own copy. We cannot delete those. We keep one record that you withdrew your consent. In it, your email address is replaced by a scrambled code (a hash), and it keeps only the kind of consent, where you gave it, the dates, the version of the consent wording, the language and the reason. Someone who already knows your address could still match that record. Running the deletion also leaves that scrambled code in the record of that job run, in Jakarta, until Google removes it (see "How long we keep it"), and for 400 days in Google Cloud's audit log, outside Indonesia. Our usage counts are not deleted; they hold no email or IP address. Our abuse-limit counts are deleted on their own within about 2 hours, whether you ask or not. If an email to you bounced or was marked as spam, Resend's block list keeps your address, so nothing is sent to it again. Some copies disappear on their own: backups within about a week, visit logs within 30 days, Resend's log of emails it sent you after the period Resend sets (30 days on its standard plans), and the IP addresses Firebase Hosting keeps after a few months. After that, Google, which hosts our database and logs, can take up to about six months to clear the last copies from its own systems. If you used more than one spelling of your address (with or without dots, or with a +tag), tell us each one. If you take a test again after a deletion, we treat you as new: tapping Show my result gives your consent again.
Cookies and browser storage
A cookie is a small file a website saves in your browser.
- Visitors get no cookies from esnc.app.
- While you take a test, your browser tab keeps your answers in session storage (a small store that lasts only while the tab is open). This way a reload does not lose your answers, and the email page can send them. A second item holds a random code, so a retry after a lost connection is saved only once. Both are removed after your test is sent, and when you close the tab.
- The full test also keeps a copy of your answers in local storage (a small store in your browser that stays after you close the tab), so another esnc.app tab in the same browser, or a later visit, can continue it. The copy holds your answers so far, the test's language and version, the random code of this test run, and the time of your last answer, but no email address. We never receive this copy. It is removed when your test is sent, or when you tap Start over. 24 hours after your last answer we stop using it, and it is deleted the next time the full test is opened in that browser. Opening the test without answering does not make it last longer. The quick test keeps nothing in local storage.
- For visitors, esnc.app keeps nothing else in your browser.
- Cloudflare's bot check may keep its own data in your browser. Cloudflare describes what Turnstile collects in its Turnstile Privacy Addendum: https://www.cloudflare.com/turnstile-privacy-policy/
- Staff only: signing in sets one cookie, named
__session. It keeps the staff member signed in for 12 hours, then they sign in again. It is removed when they sign out. Google's sign-in tools, which run when staff sign in, may keep their own data in the browser.
Children
We do not ask your age. Under UU PDP, using a child's personal data needs the consent of the child's parent or guardian (UU PDP, Art. 25(2)). UU PDP itself does not say who counts as a child. Indonesia's Child Protection Law counts anyone under 18 as a child (UU 23/2002 as amended by UU 35/2014, Art. 1 point 1), and from 16 January 2027 UU PDP's implementing regulation counts anyone under 18 who has never married (PP 33/2026, Art. 1 point 21). So if you are under 18, please ask a parent or guardian to agree before you give us your email address. If a parent or guardian tells us their child used esnc.app, we will delete the child's data.
Changes to this policy
This policy has a version number and a date at the top. When we change it, we publish a new version with a new date and keep earlier versions. Write to us if you want to read one. If a change affects how we use your data, we will tell you on esnc.app and by email before it applies. We expect a new version before we add accounts and membership features.
Every consent record also stores which version of the consent wording it rests on. When you tap Show my result, that is the version shown above the button. When you tap Send me ESNC news again, that page shows its own shorter wording, and the record stores the version of the consent wording in use that day.
Contact
PT Senada Dengan Jiwa
Email: privacy@youresnc.com