How rina4d Handles Your Account Data
This privacy policy is the part of rina4d that explains what we hold about you, why we hold it, and how long it stays with us. We wrote...
Scope, Jurisdiction and Your Consent
This policy applies to your rina4d account and any session you open on rina4d.bet, where local law permits. We collect identity fields you submit at signup, device fingerprints used for login security, and transaction references generated when your DANA, OVO, GoPay or QRIS wallet pings our cashier. We do not sell your data. We share it only with payment partners completing your
top-ups, with verification vendors confirming your KYC, and with regulators in supported regions when they request it in writing. By keeping your account active you accept the version of this policy posted on the page; we date every revision and notify you in-app before material changes take effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reach Our Privacy Desk
If a clause here is unclear, or you want to exercise a data right, our privacy desk answers in English and Bahasa Indonesia. Use any of the routes below and reference your account email so we can pull the right record.
Privacy Email
Send data access, correction or erasure requests to our privacy mailbox. Include the email tied to your rina4d account so we can match the record and reply within seven working days.
In-App Chat
Open the chat bubble from your account header and type 'privacy' to route the conversation to our compliance team rather than the standard cashier queue. Sessions are logged for your protection.
Postal Channel
For formal notices or regulator-led requests, our registered correspondence address is listed in the account footer. Written letters receive written replies, signed by the data officer on duty.
How We Maintain This Policy
This document is reviewed by people, not auto-generated. Here is who touches it and how often, so you can judge whether the wording you are reading still reflects how rina4d actually behaves...
Quarterly Review
Our compliance lead re-reads every clause every three months and stamps the version date at the top. If nothing changed, the date still moves so you know the review happened.
Legal Sign-Off
External counsel based in Jakarta vets material edits before we publish them. Their notes sit in our internal ticket log and can be summarised on written request from regulators.
Vendor Audits
Each payment and KYC vendor we name in this policy is audited annually. We drop vendors who cannot show current certifications and update this page when the list changes.
Breach Protocol
If account data is exposed, we notify affected holders within seventy-two hours through the email tied to your account and post a dated incident note inside the help centre.
Plain Language
We rewrite legalese into readable English whenever a clause sees more than three support tickets in a month. Clarity is treated as a privacy feature, not a stylistic choice.
Staff Training
Anyone at rina4d who can see your data sits a privacy refresher twice yearly. Access logs are sampled monthly and unusual queries are reviewed by the compliance lead.
Consistency Across Our Policy Pages
This privacy policy works alongside our terms, cookies and KYC pages. The table below shows how the same data principles repeat across each document so nothing contradicts.
| Data Collected | Identical list across privacy, KYC and cookies — name, contact, device, wallet reference. No page adds a hidden category. |
|---|---|
| Retention | Five years post-closure on all policy pages, matching Indonesia financial record obligations under supported regions' rules. |
| Sharing | Payment partners, KYC vendors, regulators on request. The same three-bucket list appears in privacy and terms verbatim. |
| Your Rights | Access, correction, erasure, portability. Listed identically in privacy and the account settings panel inside your dashboard. |
| Cookies | Privacy references the cookie page; the cookie page references back. Categories and lifespans match in both directions. |
| Updates | Quarterly review date stamped on every policy page. If one moves, the others move within the same publication window. |
| Contact | Same privacy desk email and chat route appear on every policy page so you never hunt for the right channel. |
What This Policy Page Shows You
The privacy page is laid out so you can scan it without reading top to bottom. These are the on-page elements we keep visible so the...
Version Stamp
A dated badge at the top of the hero tells you which revision you are reading. Older versions remain accessible through the archive link in the footer for reference.
Scope Block
The jurisdiction paragraph sits high on the page so you confirm the policy applies to your supported region before reading the operational clauses underneath.
Rights Summary
Your data rights are summarised in plain English near the support cards, with the long-form clauses linked beneath. Skim the short version, dive in only if needed.
Contact Cards
Three clearly labelled routes — email, chat, post — sit in the middle of the page so a privacy question never sends you back to the homepage to find help.
Consistency Table
The comparison grid maps this policy against terms, cookies and KYC pages so you see at a glance that nothing contradicts across our legal stack.
FAQ Anchor
Common questions sit at the bottom with anchor links you can share. Send a teammate straight to the clause that answers their concern without forwarding the whole page.