Use the privacy or account controls available in Ripple, submit an applicable support ticket, or email kisschou@gmail.com. Include your Ripple ID, login email, country of residence, the right you want to exercise and enough detail to locate the relevant data. Never send your password, one-time verification code, full payment card information or unnecessary identity documents.
Ripple may verify control of the account through the normal login channel or request proportionate additional evidence where required. Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability or withdrawal of consent. Ripple may withhold another person's data, security-sensitive information, privileged material and records that must be retained for transactions, payouts, fraud, reports, disputes or law. Account deletion instructions are available at https://rippleim.com/legal/account-deletion.html.
1. Purpose
This Data Request Procedure explains how Users and other individuals may exercise applicable rights concerning their personal information processed by the Platform.
The procedure is designed to provide a clear and secure process for requests concerning:
access to personal information;
correction;
deletion;
data portability;
restriction of processing;
objection to processing;
withdrawal of consent;
certain marketing preferences;
information about processing activities; and
other rights available under applicable data protection law.
This Procedure operates together with the Platform's Privacy Policy and does not limit any mandatory rights provided by applicable law.
2. Scope
This Procedure applies to personal information processed by the Platform in connection with the Service.
Depending on the User's jurisdiction and circumstances, applicable rights may arise under:
the UK GDPR;
the EU GDPR;
applicable United States privacy laws;
other applicable national or regional privacy laws; or
other data protection requirements applicable to the relevant processing.
The availability and scope of individual rights may differ depending on the User's location, legal status, type of request, and applicable law.
3. Who May Submit a Request
A request may generally be submitted by:
the individual to whom the personal information relates;
an authorized representative;
a parent or legal guardian where legally permitted;
an authorized legal representative; or
another person legally entitled to exercise the relevant right.
Where a representative submits a request, the Platform may require appropriate evidence of authority.
4. Data Privacy Center
Where available, Users may submit requests through the Platform's Privacy Center.
The Privacy Center may provide options including:
Request My Data;
Download My Data;
Correct My Information;
Delete My Account;
Request Processing Restriction;
Object to Processing;
Withdraw Consent;
Marketing Preferences; and
Contact Privacy Support.
Privacy Center: https://rippleim.com/legal/data-request.html
5. Privacy Support Contact
Requests may also be submitted to:
Privacy Email: kisschou@gmail.com
Data Protection Contact: kisschou@gmail.com
Privacy Portal: https://rippleim.com/legal/
Operator: Individual developer and operator of Ripple
Where the Platform has appointed a Data Protection Officer or representative for a particular jurisdiction, the relevant contact information will be provided in the applicable Privacy Policy.
6. Types of Data Requests
Depending on applicable law, Users may request:
6.1 Access
A User may request information about personal information held or processed by the Platform and, where legally required, a copy of that information.
6.2 Correction
A User may request correction of inaccurate or incomplete personal information.
6.3 Deletion
A User may request deletion of personal information where applicable legal requirements are satisfied.
6.4 Portability
Where applicable, a User may request personal information in a structured, commonly used, and machine-readable format.
6.5 Restriction
Where applicable, a User may request restriction of certain processing.
6.6 Objection
Where applicable, a User may object to particular processing activities.
6.7 Consent Withdrawal
Where processing relies on consent, a User may withdraw consent where legally applicable.
Withdrawal of consent does not necessarily affect processing that was lawfully carried out before withdrawal.
7. Information That May Be Covered
Depending on the request and applicable law, relevant information may include:
account information;
profile information;
profile photographs;
uploaded media;
communication-related information;
location information;
matching and recommendation information;
usage and activity information;
device and technical information;
payment and transaction records;
subscription information;
Creator information;
KYC-related status or information;
safety reports;
moderation records;
security records;
customer-support records; and
other personal information processed by the Platform.
Not all information is necessarily subject to every legal right.
8. Data Categories That May Be Excluded
Certain information may be excluded from a request where permitted or required by applicable law.
Examples may include information that:
is protected by legal privilege;
concerns another person's rights;
would compromise security;
is subject to a lawful retention obligation;
is necessary for legal claims;
is subject to applicable exemptions;
cannot reasonably be separated from another person's protected information; or
is otherwise exempt under applicable law.
Where information is withheld under an applicable exemption, the Platform may provide an explanation to the extent legally permitted.
9. Identity Verification
The Platform may take reasonable steps to verify the identity of a person making a data request.
Verification may be necessary to prevent unauthorized disclosure of personal information.
Depending on the circumstances, verification may involve:
account authentication;
confirmation through a registered email address;
confirmation through an authenticated account;
security questions;
account-specific information;
identity verification; or
other proportionate measures.
The Platform will seek to avoid collecting unnecessary information solely for verification.
10. Verification Requests
If additional verification is reasonably necessary, the Platform may request information sufficient to establish that the requester is the relevant individual or authorized representative.
Users should not provide:
passwords;
private keys;
wallet seed phrases;
payment authentication codes; or
other credentials
unless a secure process specifically requires otherwise.
The Platform will not ordinarily request highly sensitive authentication credentials through ordinary email.
11. Requests Made by Authorized Representatives
Where permitted by law, a User may authorize another person to submit a request.
The Platform may request:
proof of authorization;
information necessary to verify the requester;
information necessary to verify the relevant individual; and
other information reasonably necessary to process the request securely.
The Platform may communicate directly with the individual where necessary to confirm the authorization.
12. Request Submission
A request should contain sufficient information to allow the Platform to:
identify the relevant account;
understand the request;
determine the applicable legal right; and
securely process the request.
A request may include:
account identifier;
registered email address;
username;
request type;
relevant jurisdiction;
description of the requested action; and
any supporting information reasonably necessary.
13. Request Acknowledgment
Where appropriate, the Platform may acknowledge receipt of a request and provide:
request reference number;
request type;
date received;
verification status;
expected processing timeline; and
contact information for follow-up.
Requests may be recorded internally as a Data Subject Access Request (DSAR) Case or equivalent privacy case.
14. Internal DSAR Case Management
The Platform may maintain an internal privacy case record containing, as appropriate:
DSAR Case ID;
User ID;
request type;
date received;
jurisdiction;
verification status;
applicable legal basis;
relevant systems;
assigned reviewer;
processing status;
response date;
outcome;
reason for any limitation or refusal; and
audit information.
Access to such records should be limited according to internal permissions.
15. Data Inventory and System Search
To process a request, the Platform may identify relevant systems and data sources.
Depending on the request, this may include:
account database;
profile systems;
messaging systems;
media storage;
payment systems;
subscription systems;
Coin Ledger;
Gift Ledger;
Creator Earnings systems;
KYC systems;
moderation systems;
safety systems;
customer-support systems;
security logs;
audit systems; and
other relevant systems.
The Platform's data inventory and data-flow documentation may be used to identify relevant processing locations.
16. Access Requests
Where an applicable access right exists, the Platform may provide:
confirmation that personal information is being processed;
categories of personal information;
purposes of processing;
relevant recipients or categories of recipients;
information concerning international transfers where required;
applicable retention information;
available information concerning the source of data where required; and
a copy of relevant personal information, subject to applicable law.
17. Data Export
Where applicable, the Platform may provide personal information through a downloadable or otherwise transferable format.
Depending on the information requested, an export may include:
account information;
profile information;
uploaded content;
available communication data;
transaction history;
subscription information;
relevant account activity; and
other information required by applicable law.
The exact contents and format may vary according to the request and applicable law.
18. Data Portability
Where a portability right applies, the Platform may provide eligible personal information in a structured, commonly used, and machine-readable format.
Portability may not apply to:
all information processed by the Platform;
information processed solely under certain legal bases;
information concerning other individuals;
information protected by legal restrictions; or
information otherwise exempt under applicable law.
19. Correction Requests
Users may request correction of inaccurate or incomplete personal information.
Where appropriate, Users may also directly modify certain information through account settings.
Examples may include:
display name;
profile description;
language preferences;
profile information;
certain location settings; and
other editable account information.
Where direct editing is unavailable, the User may submit a correction request.
20. Deletion Requests
Users may request deletion of personal information where applicable law provides a right to deletion or erasure.
The Platform may delete or anonymize relevant information where legally and technically appropriate.
Deletion may involve:
account information;
profile information;
uploaded content;
selected activity information; and
other eligible personal information.
21. Account Deletion
Where the Service provides account deletion functionality, Users may initiate account deletion through the designated account settings or Privacy Center.
Account deletion may trigger related processes concerning:
account status;
active sessions;
profile visibility;
subscriptions;
Coins;
Gifts;
Creator participation;
pending transactions;
stored content; and
associated personal information.
The Platform may provide additional information before completion where necessary.
22. Data That Cannot Immediately Be Deleted
Certain information may need to be retained where permitted or required by law.
Examples may include information necessary for:
legal obligations;
tax and accounting records;
fraud prevention;
payment disputes;
chargeback management;
security investigations;
legal claims;
evidence preservation;
enforcement of contractual rights;
regulatory requirements; or
other lawful purposes.
Where deletion is not possible, the Platform may restrict or segregate the relevant information where appropriate.
23. Retention After Account Deletion
Account deletion does not necessarily mean that every record associated with the account is immediately erased from all systems.
Certain records may remain temporarily or for a legally required period in:
backups;
security systems;
financial records;
dispute records;
legal records;
fraud-prevention systems; or
other systems where immediate deletion is technically or legally inappropriate.
The Platform will handle retained information according to applicable retention requirements and the Privacy Policy.
24. Objection Requests
Where applicable law provides a right to object, Users may request that the Platform stop or limit specified processing.
The Platform may assess:
the processing activity;
the applicable legal basis;
the User's circumstances;
the Platform's legitimate interests;
legal obligations; and
applicable exceptions.
Where the law requires processing to stop, the Platform will take appropriate action.
25. Direct Marketing
Users may generally control certain marketing communications through:
unsubscribe mechanisms;
account settings;
Privacy Center controls; or
other designated preference tools.
Where applicable law provides an absolute or specific right to object to direct marketing, the Platform will respect that right.
Operational or legally required communications may continue where permitted.
26. Restriction of Processing
Where applicable law provides a right to restrict processing, the Platform may limit processing while:
the accuracy of information is disputed;
the lawfulness of processing is being challenged;
the information is required for legal claims; or
another legally recognized ground for restriction applies.
Restricted information may continue to be stored while processing is limited.
27. Consent Withdrawal
Where processing relies on consent, a User may withdraw consent through an available control or by contacting the Platform.
Withdrawal does not:
invalidate processing that occurred before withdrawal;
necessarily require deletion of all information; or
affect processing based on another lawful basis.
28. Automated Decision-Making
Where applicable law provides rights concerning automated decision-making or profiling, Users may request information or exercise applicable rights.
The Platform may use automated systems for purposes such as:
matching;
recommendations;
fraud detection;
safety;
moderation;
payment risk; and
security.
Not every automated system constitutes legally defined automated decision-making that produces legal or similarly significant effects.
Where a legally protected right applies, the Platform will handle the request according to applicable law.
29. Data Concerning Other Individuals
A User's request may contain or relate to information about other individuals.
The Platform may take measures to protect the rights and privacy of those individuals.
For example, an export may:
remove another person's contact information;
redact private information;
exclude information belonging to another User; or
provide information in another lawful form.
30. Communications and Message Data
Requests involving messages may require additional review because communications can contain information belonging to multiple people.
The Platform may consider:
the requester's rights;
the rights of other participants;
applicable privacy law;
legal obligations;
security requirements; and
technical limitations.
Where appropriate, information may be redacted or withheld to protect another person's rights.
31. Payment and Financial Records
Transaction information may be retained where necessary for:
accounting;
tax;
payment processing;
refunds;
chargebacks;
fraud prevention;
financial reconciliation; or
legal obligations.
A User's deletion request does not necessarily require deletion of financial records that must legally be retained.
32. Creator and Payout Data
Creator-related requests may involve:
Creator account information;
KYC status;
payout records;
tax information;
earnings records;
withdrawal records;
payment-provider information; and
related compliance records.
Certain records may be subject to financial, tax, fraud-prevention, or legal retention requirements.
33. Safety and Moderation Records
Safety, moderation, and security records may be retained where reasonably necessary to:
protect Users;
investigate abuse;
prevent fraud;
maintain platform security;
enforce policies;
respond to legal claims; or
comply with legal obligations.
Where appropriate, information may be restricted or anonymized rather than immediately deleted.
34. International Data Transfers
Where personal information is processed across borders, applicable international-transfer requirements will be considered.
Depending on the applicable jurisdiction, the Platform may use appropriate transfer mechanisms or safeguards.
A data request does not necessarily change the location where data is lawfully processed.
35. Response Time
The Platform will process requests within the timeframe required by applicable law.
The applicable period may depend on:
the type of request;
the User's jurisdiction;
whether identity verification is required;
the complexity of the request;
the number of requests received; and
whether lawful extensions are available.
Where an extension is legally permitted and necessary, the Platform may notify the requester.
36. Complex or Repeated Requests
Where permitted by applicable law, the Platform may take appropriate steps where requests are:
manifestly unfounded;
excessive;
repetitive;
abusive; or
technically disproportionate.
Any refusal, limitation, or fee will only be applied where permitted by applicable law.
The Platform will not use this provision to improperly prevent a User from exercising legitimate privacy rights.
37. Fees
Requests will generally be handled without charge where required by applicable law.
Where applicable law permits a reasonable fee for certain excessive or repetitive requests, the Platform may charge an appropriate fee or take another lawful approach.
Any applicable fee will be communicated before processing where required.
38. Secure Delivery
Data exports and responses may be delivered through secure methods.
Depending on the request, delivery may occur through:
authenticated account access;
secure download;
encrypted transfer;
verified email;
another secure digital method; or
another method appropriate to the sensitivity of the information.
The Platform may avoid sending highly sensitive personal information through insecure channels.
39. Request Completion
When a request is completed, the Platform may record:
completion date;
data categories processed;
action taken;
information provided;
information withheld;
legal basis for any limitation; and
relevant audit information.
The requester may receive confirmation of completion where appropriate.
40. Request Denial or Limitation
If a request is denied or limited, the Platform may explain:
the relevant reason;
the applicable legal exception;
any information that can still be provided;
available appeal or review options; and
applicable complaint rights.
The explanation may be limited where disclosure itself would violate applicable law or compromise security, fraud-prevention measures, or another person's rights.
41. Appeals and Internal Review
Where a User disagrees with the handling of a data request, the User may request an internal review where available.
An appeal may include:
the original request;
the response received;
the reason for disagreement; and
additional information relevant to the request.
The Platform may assign the review to an appropriate privacy or legal reviewer.
42. Regulatory Complaints
Where applicable law provides a right to complain to a data protection authority or other regulator, Users may exercise that right.
Depending on the User's location, this may include the relevant national or regional privacy regulator.
Nothing in this Procedure prevents a User from exercising a legally available regulatory complaint right.
43. Security of Data Requests
The Platform will apply reasonable security measures to the request process.
These measures may include:
access controls;
administrator authentication;
role-based permissions;
audit logging;
secure data transmission;
identity verification;
restricted export access; and
appropriate retention controls.
The objective is to prevent unauthorized disclosure of personal information during the request process.
44. Internal Audit Trail
The Platform may maintain an audit trail for privacy requests.
Relevant records may include:
request creation;
identity verification;
systems searched;
information accessed;
administrator actions;
response generation;
approval;
completion;
appeal; and
final resolution.
Administrator access to privacy requests should be recorded and restricted according to internal security controls.
45. Relationship With the Privacy Policy
This Procedure supplements the Platform's Privacy Policy.
The Privacy Policy describes:
categories of personal information;
purposes of processing;
legal bases;
recipients;
international transfers;
retention;
security;
User rights; and
jurisdiction-specific privacy information.
This Procedure describes how eligible data requests may be submitted and processed.
Where applicable law requires a different procedure or provides stronger rights, the applicable law will prevail.
46. Relationship With Account and Service Policies
A data request does not automatically:
cancel a subscription;
refund a purchase;
reverse a Gift;
restore a suspended account;
restore deleted content;
remove a Creator payout obligation; or
terminate a legal dispute.
Those matters may be governed by separate Platform policies.
47. Changes to This Procedure
We may update this Procedure from time to time to reflect:
changes in applicable privacy law;
changes to the Service;
changes in data architecture;
changes in Privacy Center functionality;
new security procedures; or
improvements to privacy rights management.
Where required by law, appropriate notice will be provided.
48. Contact Information
For data protection requests:
Privacy Center: https://rippleim.com/legal/data-request.html
Privacy Email: kisschou@gmail.com
Data Protection Contact: kisschou@gmail.com
No Data Protection Officer has been formally appointed. Privacy requests may be sent to kisschou@gmail.com.
Operator: Individual developer and operator of Ripple
Formal notices: kisschou@gmail.com
49. Final Principle
The Platform is committed to providing Users with a clear and secure mechanism for exercising applicable data protection rights.
The Platform will seek to balance:
individual privacy rights;
User security;
the rights of other individuals;
legal obligations;
fraud prevention;
financial recordkeeping;
platform integrity; and
legitimate operational requirements.
Nothing in this Procedure is intended to exclude or restrict a privacy right that cannot lawfully be excluded.
End of Data Request Procedure