Reference

Privacy Policy for Your r50s Account Data

Before you open an account, this page tells you what we collect, why we use it, and how you can ask for changes where local law permits.

Data UseCookiesLocal LawAccount Requests
r50s Privacy Policy for Your r50s Account Data
REACH US DIRECTLY

Ways to Send a Privacy Request

If you want a copy of your stored details, need a correction, or want us to look at a privacy concern, use the contact path that matches your request.

Help form Send the account email, the change you want, and any dates that help us find the record. We use this path for corrections, copies, and deletion requests where local law permits.
Support chat If you need quick clarification on what we hold, start a chat and mention the privacy request at once. That helps us route it without mixing it with wallet or login questions.
Mail request For a written trail, send your request from the email linked to your account. We may ask for a verification step before acting, so we know the request belongs to you.
DATA HANDLING RULES

How We Handle Your Data

We keep the policy tied to actual account work: collecting only what we need, limiting who can see it, and logging changes that affect your profile.

Data collection

We collect details you give at sign-up, during wallet actions, and in support messages, plus technical data from the device…

Cookies

Cookies store session state, language choice, and page settings so you do not repeat the same steps on every visit.

Security checks

If we need to confirm identity, we may ask for a fresh login, device check, or matching account detail before…

Retention

We keep records only as long as needed for account service, dispute handling, fraud checks, tax duties, or other legal…

Your changes

You can ask us to correct stale details, update contact points, or explain how a record was used.

Contact trail

For privacy requests, use the same contact channel each time so we can track the thread.

Questions About Your Privacy Rights

This section answers the privacy points you are most likely to check before opening an account or sending a request. We keep the answers tied to real account handling: what we collect, how cookies work, who can see your details, and how to ask for access or change. If a right depends on local law, we say so plainly and apply it where local law permits.

We collect the details you enter for your account, payment activity, device signals, and support messages. That lets us create the profile, process requests, and keep a record of changes tied to your account.

Yes, you can ask for access to the record we hold about you. Where local law permits, we will share the relevant copy after we check the request against the account and any security step we need.

Yes. If a contact field or other stored detail is wrong, send the correction and the account email it belongs to. We will update the record once we confirm the request and local law allows the change.

Cookies help keep you signed in, remember page settings, and tell us when a session ends. They do not let us read anything outside the record tied to your account, and you can clear them through your browser.

Only the people who need the record for account service, support, security, or legal duties can see it. We do not share it more widely than needed for that purpose, and we limit access by role.

We keep records for the time needed to run the account, answer requests, settle disputes, check misuse, or meet legal duties. After that, we delete or anonymise them where local law and our systems allow.

Use the contact path listed on this page and say what you want changed, copied, or checked. If we need to confirm identity, we will ask for a quick verification step before acting.