Kanzad privacy policy
Draft, pending legal review. This text is a draft written from the service's data map. It is not yet in force.
Last updated: 2026-11-17 (draft).
This policy says what personal data Kanzad keeps about you, why, who else handles it, how long it stays, and how to use your rights.
1. Who is responsible
The controller of your personal data is Brillune Dış Ticaret Limited Şirketi, a limited company registered in Türkiye (Istanbul Trade Registry 1069839, MERSİS 0187172075400001), at Demirkapı Mah. 1654. Sk. Metro Konutları Sitesi C No: 17 İç Kapı No: 9, Bağcılar, İstanbul, Türkiye. You can reach us at [DRAFT: contact email address]. [TO CONFIRM: any data protection officer or representative.]
2. What we keep, and why
Kanzad sends alerts about coin and banknote auction lots. To do that we keep the data below.
- Your account. Your email address. We use it to sign you in and to identify your account.
- Sign-in codes. The email address a sign-in code was requested for, with hashes of the code and the link. We never keep the code itself.
- Sign-in sessions. A record that ties a signed-in session to your account. It is deleted when you delete your account.
- Emails we send. The address of each email we send you (a sign-in email, or a waitlist confirmation), with only the expiry in minutes or the language.
- The waitlist. If you joined the landing-page waitlist, your email address, the language of the page you joined from, the landing-page version you saw (A or B), the version of the consent text you agreed to, when you joined, when we sent the confirmation email and when you confirmed. Joining uses double opt-in: the entry counts only after you confirm it, and until then the confirmation time is empty. The confirmation token is stored only as a keyed hash.
- Your plan. The plan on your account and its store reference.
- Plan changes. A history of changes to your plan.
- Billing events. The identifier RevenueCat uses for you, on the events it sends us about purchases. We keep them so that an event delivered twice is read only once.
- Your devices. For each device that receives alerts: the push token and the installation identifier of the app on it.
- Your watched lots. The lots you chose to watch. Scheduled alerts belong to a watched lot and are deleted with it.
- Alert settings. Your alert preferences.
- Alert history. A record of each alert sent: the lot title, the alert or text body (lot title, bid and time) and the result. It holds no number and no name. When your account is deleted every link back to you is cut and the history stays without a person attached.
- Text message consent. If you turn on text alerts: your phone number, the version of the consent text you accepted, when you consented, when you verified the number and when you stopped. When your account is deleted the number is removed and the consent is marked stopped. What stays is a record that a consent existed and when it ended, with no person and no number.
- Phone number checks. A pending check of a phone number holds the number being proven.
- Text count. The number of texts sent to you in a month.
- Administrator log. A log of administrator actions. Today it records the key of a data source, never a person. If a row ever names you by id or address, it is rewritten to "erased" when you delete your account.
- Deletion requests. When you ask us to delete your account we keep the proof that the request was made and served: your account identifier, the times and a count per table. It holds no email address and no phone number.
- Sign-in attempt limits. To limit repeated attempts we keep keyed hashes of the email address, the phone number or the network (IP) address an attempt came from, with the time. A hash is not the address or number itself, but it can still be linked to it by whoever holds the key, so we treat it as personal data. Nothing in a row names your account. The same table holds the counters that limit how often a waitlist confirmation is sent to one address or requested from one network.
- Beta build start. Only in a beta test build: an identifier made for the beta alone, the build number, the time that build first asked whether the beta is still open, and the latest time it asked. On an iPhone the identifier is random and is kept in the phone's keychain. On an Android phone it is worked out on the phone from the device identifier Android gives this app, so the identifier itself never leaves the phone and the same value comes back after a reinstall. It holds no email address, phone number or account identifier, and no other record holds it, so nothing links it to you or to your account. We use it to count the days of the beta.
Data that does not concern you personally is also kept: auction lots and their bid history, the sources we read, rate counters, and measurements per minute. Measurements carry a metric name and counts from a closed set of categories and contain no personal data.
3. Lawful basis
- Contract. We process your email address, sessions, plan, devices, watched lots, alert settings and alert history to provide the service you asked for. [TO CONFIRM: lawful basis wording for billing records.]
- Consent. Text messages and the waitlist rest on your consent. You can withdraw it at any time: stop text alerts in the app, and ask us to remove a waitlist entry.
- Other. [TO CONFIRM: the basis for sign-in attempt limits, the administrator log and the deletion-request record, for example legitimate interests or a legal obligation.]
4. Who else handles your data
- RevenueCat handles purchases and subscriptions. When you delete your account we ask RevenueCat to delete your subscriber record. Your store subscription is separate: it keeps renewing until you cancel it in the store.
- Twilio sends text messages: it receives your phone number and the text. [TO CONFIRM: what Twilio keeps and for how long.]
- Resend sends email: it receives the address and the message. [TO CONFIRM: what Resend keeps and for how long.]
- Firebase (Firebase Cloud Messaging) delivers push notifications to your device. [TO CONFIRM: what Firebase receives and keeps.]
- Railway hosts the service and its database. [TO CONFIRM: hosting region.]
- eBay is a source of auction listings. We read lots from eBay; we send it no data about you.
[TO CONFIRM: transfers of personal data outside your country and the safeguards used.]
5. How long we keep it
- Account data stays until you delete your account. We erase it within 30 days of your request.
- Waitlist entries that you never confirm are deleted after 30 days, by a job that runs every hour. The confirmation email of an address that never confirmed is deleted with its waitlist entry.
- Confirmed waitlist entries are kept until the address is erased, and so is the confirmation email of a confirmed address. [TO CONFIRM: how long confirmed waitlist entries are kept.]
- Sign-in and waitlist limiter records hold only keyed hashes of an email address, a phone number or a network address. A job that runs every hour deletes them once they are about an hour old. Two kinds are kept longer: the record that limits how often a device's push token may be moved is kept about two hours, and the record that limits confirmation emails to one address is kept about a day and an hour.
- Beta build start records are deleted once 120 days have passed since that build last asked, by a job that runs every hour.
- Deletion records are kept as proof that a request was served.
- Metrics contain no personal data and are kept without a personal link.
- Logs. Our logs carry your account identifier. An email address appears only as a shortened keyed hash. [TO CONFIRM: log retention period, set by our hosting platform.]
6. Your rights
Under the EU General Data Protection Regulation (GDPR) and the Personal Data Protection Law (PDPL) [TO CONFIRM: which PDPL applies, the UAE law named in the product requirements or the Saudi law], you can ask to access your data, correct it, delete it, restrict or object to its use, receive it in a portable form, and withdraw consent. You can also complain to your data protection authority.
How to use them:
- Delete your account in the app, in the account view. We erase your data within 30 days.
- Anything else, including removal of a waitlist entry that has no account, write to [DRAFT: contact email address]. [TO CONFIRM: response time.]
7. Children
Kanzad is not directed at anyone under 16. We do not knowingly collect their data. If you think a child has given us data, write to us and we will delete it.
8. Changes
We will change this policy when our handling of data changes. The date at the top shows the latest version. [TO CONFIRM: how users are told of a material change.]