Reference

Privacy Policy for Your sarana 365 Account

Our sarana 365 Privacy Policy shows how we collect, use and protect details connected with your account, wallet activity and device access.

Clear data choicesPhone verification explainedMobile access coveredIndonesia payment context
sarana 365 Privacy Policy for Your sarana 365 Account
CONTACT PATHS

Contact Us About Your Privacy Policy

A clear contact route helps when you want to ask about the Privacy Policy, check an account detail or request a correction. We connect your request to the account step involved, such as phone verification, a DANA receipt or a wallet status that has not updated. From Yogyakarta or elsewhere in Indonesia, use the support contact path shown on our site and include the relevant reference without sending a wallet password.

Team online

Policy questions

Ask us to clarify how sarana 365 uses a specific account, device or payment reference. Include the email or phone detail linked to your account, but never send your password, PIN or full wallet credentials with the request.

Correction requests

If your name, phone detail or account record needs attention, tell us which field appears incorrect and why. We may ask for an account step that confirms ownership before changing the record connected with your sarana 365 access.

Receipt status

For a DANA, OVO, GoPay or QRIS receipt, share the transaction reference and visible status rather than private wallet credentials. We use that reference to locate the payment event and respond about the related data held in the account.

SECURITY PRACTICE

Account Security Across Your Devices

Privacy choices work best when they match the way you actually access the account. We explain the practical controls behind browser sessions, cookies, phone checks, payment references and stored records, so you…

Account data

We use details such as your phone number, account identifier and selected settings to create and maintain your access. Phone verification is an account step before entry, helping us connect a request with the correct sarana 365 record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave a reference, timestamp and status in our records. We use these details to match cashier events and investigate a receipt without storing your wallet PIN.

Cookies

Cookies can keep a browser session, language choice or sign-in state working between pages. If you clear them, you may need to verify your phone or sign in again; the Privacy Policy explains which access functions depend on them.

Device signals

A mobile browser or computer can provide session and device signals used to protect account access and detect unusual sign-in patterns. These signals help us respond to security events and are handled as part of the policy data process.

Record retention

We keep account and transaction records for as long as needed for the stated service, security, dispute and legal purposes. Retention can differ by record type, and we can explain the applicable period when you make a specific request.

Policy changes

When we change the Privacy Policy, we place the updated wording on sarana 365 and adjust the displayed date or notice where appropriate. Check this page before using a new account step if you want to compare the current data terms.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened. We focus on practical points: what your phone check does, why a DANA or QRIS reference appears, how cookies affect mobile access, and where to send a request. Account eligibility and access depend on local law.

It covers account details, phone verification, device signals, cookies, payment references and requests about stored records. It also explains how we use those details for account access, transaction matching and security when you use sarana 365 where local law permits.

No. We may receive a payment reference, amount and status for DANA or QRIS activity, but your wallet password and PIN stay with the payment provider. Do not send either credential to our support contact when asking about a receipt.

Phone verification connects an account request to the correct record before access and helps us respond to unusual sign-in activity. The phone detail is handled under the Privacy Policy, and access eligibility depends on local law.

Cookies can keep your browser session and selected settings available while you move through account pages. Clearing them may sign you out or require another phone check. The policy explains this browser behaviour and the purpose connected with each cookie type.

Yes, you can contact us with a request to explain, correct or access eligible account data. Include the account-linked phone or email detail and describe the record involved. We may confirm ownership before responding or making a change.

Retention depends on the record and the service, security, dispute or legal purpose connected with it. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may therefore have a different period. Ask us about the specific transaction.

Use the support contact path displayed on our site and mention the section or wording you want clarified. We can explain the current Privacy Policy, the account step affected and any practical change to mobile access or payment reference handling.