RoyalAce Privacy Policy, Personal Data and Requests
RoyalAce collects personal information connected with account registration. This can include your name, email address and date of birth.
The privacy policy also describes technical information generated through use of the site, including IP address, device information and browsing behaviour.
RoyalAce states that personal data is used for purposes that include account verification and payments. The privacy policy also provides routes for requesting access to, correction of or deletion of personal information.
What Personal Data RoyalAce Collects
The information described in the privacy policy falls into more than one category. Some details are provided directly when an account is created, while other information can be generated through the device and browser used to access the site.
- Name.
- Email address.
- Date of birth.
- IP address.
- Device information.
- Browsing behaviour.
These categories should not be expanded into a broader identity-document list unless a separate account process specifically requests additional information.
Registration and Technical Data Differ
Name, email and date of birth relate to account registration. IP address, device information and browsing behaviour are technical data associated with use of the site.
If you are creating an account, the registration information requirements explain the separate need to provide accurate and verifiable account details.
Why RoyalAce Uses Personal Information
The privacy policy identifies account verification and payments among the purposes for which personal information can be used.
For example, account information may be relevant when RoyalAce needs to confirm details connected with an account, while payment-related processing can require information associated with deposits or withdrawals.
This page does not add purposes that are not stated in the published privacy information. It should not be assumed that every category of data is used for every account action.
Verification and Payments Are Named Purposes
Account verification and payment processing are specifically identified as uses of personal information. The exact data involved can depend on the account action or service being used.
When Selected Data May Be Shared
The privacy policy states that selected information may be shared with certain service-provider categories where those services are required.
| Provider Category | Published Privacy Role | Boundary |
|---|---|---|
| Payment providers | Selected data may be shared for payment-related services | No specific payment company is established here |
| ID-verification providers | Selected data may be shared for verification services | No specific provider or universal document list is established |
| Support providers | Selected data may be shared to support service delivery | Not every support request necessarily requires identity information |
The wording matters: selected data may be shared with these provider categories. This should not be read as meaning every piece of personal information is sent to every provider.
Sharing Does Not Mean Every Detail
Data sharing is connected with the service being provided. A payment-related task, verification check or support request can involve different information, so the same data set should not be assumed in every case.
Review the Published Security Measures
The RoyalAce privacy policy states that SSL encryption and restricted databases are used as security measures.
These statements should be understood as the controls described in the policy. They should not be expanded into claims about specific encryption standards, server locations, independent security certification or protection against every possible risk.
Security Measures Are Not a Guarantee
The privacy policy describes SSL encryption and restricted database access. These are published security measures, not a guarantee that every security risk can be eliminated.
Users should still protect their own login credentials and avoid sharing passwords through support or privacy requests.
Make a Privacy or Data Request
The RoyalAce privacy policy allows users to make several types of requests concerning their personal information.
- Request access to personal data.
- Request correction of inaccurate information.
- Request deletion of data.
- Opt out of marketing messages.
- Send the privacy request to [email protected].
A deletion request should be treated as a request rather than a promise of immediate or universal erasure. The published privacy information does not establish a fixed completion time for every type of request.
Use the Published Privacy Contact
Privacy requests are directed to [email protected]. State clearly whether the request concerns access, correction, deletion or marketing preferences.
If you need help reaching the published contact route, the support contact options explain the available RoyalAce support channels.
Keep Privacy and Account Terms Separate
The privacy policy deals with personal information, data use, sharing, security statements and privacy requests. General account conditions cover a different set of issues, including eligibility, account conduct, promotions and withdrawals.
The supported privacy information does not establish a fixed schedule for privacy-policy updates or a particular notification method for every revision. When privacy details matter, use the currently published version rather than assuming an older copy remains unchanged.
Do Not Assume an Update Schedule
No annual revision cycle, advance-email notice or other fixed privacy-notice update process should be assumed unless it is explicitly stated in the current policy.
For contractual rules outside personal-data handling, review the general account terms separately from the privacy policy.
Prepare a Clear Privacy Request
A privacy request is easier to understand when it identifies the action you want without adding unnecessary account information.
- State whether the request concerns access, correction, deletion or marketing.
- Identify the account information relevant to the request.
- Explain what information needs to be reviewed or corrected where applicable.
- Send the request to [email protected].
- Do not send your password.
- Follow any account-specific verification request if one is presented later.
No universal passport requirement, mandatory privacy form, fixed ticket number or processing deadline should be assumed unless the specific request process states otherwise.
Deletion Is a Request, Not an Instant Guarantee
The privacy policy allows requests for deletion of data. Submitting such a request should not be described as automatically deleting every record immediately or bypassing other account requirements that may still apply.
FAQ – RoyalAce Privacy Policy Questions
What Personal Details Are Collected?
Registration-related information can include your name, email address and date of birth.
Can RoyalAce Collect Device Information?
Yes. The privacy policy states that technical data can include device information and browsing behaviour.
Why Are IP Addresses Processed?
IP addresses are listed among the technical data described by the privacy policy. The stated data-use purposes include account verification and payments, without assigning a separate unsupported purpose specifically to IP addresses.
How Are Payment Details Used?
Payments are one of the stated purposes for processing personal information. Selected data may also be shared with payment providers where needed to provide payment-related services.
Are Data Requests Available?
Yes. The privacy policy allows requests for access, correction and deletion of personal data.
Can I Correct Outdated Information?
Yes. You can request correction of personal information that needs to be updated or amended.
How Do I Request Deletion?
Send a privacy request to [email protected] and state that you are requesting deletion of personal data. The request should not be treated as a guarantee of immediate deletion in every circumstance.
Can I Opt Out of Marketing?
Yes. The privacy policy describes an option to opt out of marketing messages.
Are Service Providers Given Some Data?
Yes. Selected data may be shared with payment, ID-verification and support providers where those services are required.
What Security Controls Are Described?
The privacy policy states that SSL encryption and restricted databases are used. These are published security measures rather than a guarantee that every security risk can be eliminated.
Where Are Privacy Requests Sent?
Privacy requests are sent to [email protected].
Can the Privacy Notice Be Updated?
The supported privacy information does not specify a fixed update timetable or notification process. Review the current published privacy policy when you need the latest information.