Last updated Nov 14, 2026
Privacy Policy
This policy explains in plain words what Nucleic Table does with personal data. It has two parts because we play two roles: for restaurant owners’ own accounts we decide how data is used, while for each restaurant’s guests the restaurant decides and we only work on its behalf.
1. Two roles
| Whose data | Our role | Where it is explained |
|---|---|---|
| Restaurant owners and their staff accounts, and visitors of this website | Data controller | The Personal Data Notice (KVKK) and this policy |
| A restaurant’s guests: their accounts, phone numbers, orders, reviews and loyalty | Data processor. The restaurant is the controller. | The Data Processing Agreement and the restaurant’s own privacy notice |
2. Who is the controller
For the data we control, the controller is:
- Data controller contact: Not yet published
- Registered e-mail (KEP): Not yet published
- Postal address: Not yet published
3. What we collect about owners
- Account: e-mail address and a salted hash of your password; we never store the password itself.
- Restaurant: its name, its address on the platform, your chosen preset and the trial and billing state.
- Records of the documents you accepted at sign-up, with the version, time and technical details of the acceptance.
- Sign-in and security records: IP address, browser and device details, and the actions recorded in the audit log.
- Billing references from Polar (customer and subscription numbers). Card details are handled by Polar only.
- Messages you send us.
4. Why we use it
- To create your restaurant and run the service you signed up for
- To keep the service secure and prevent abuse
- To bill you and to meet tax and accounting duties once sales are open
- To answer your questions and to establish or defend legal claims
We do not sell personal data and we do not use it for advertising.
6. How long we keep it
- Owner account and restaurant data: while the restaurant exists. After it is closed, the restaurant is archived and its database is deleted after a limited retention period.
- Security and audit records: only as long as needed for security and to defend legal claims.
- Billing and tax records: as long as the law requires.
7. How we protect it
- Every restaurant has its own database schema and its own accounts, so restaurants are separated.
- Passwords are stored as salted hashes; sessions use cookies that scripts cannot read.
- Access follows roles, support access is time-limited and logged, and sign-up and sign-in are rate-limited.
8. Your rights
You can ask us whether we process your data, ask for a copy, have it corrected or deleted, object to its use and ask about the recipients. The full list and how to apply are in the Personal Data Notice (KVKK). If you are a guest of a restaurant, address your request to that restaurant first; we will help it answer.
9. Contact
- E-mail: Not yet published
- Registered e-mail (KEP): Not yet published
- Postal address: Not yet published