Identity-data retention, deletion requests and account closure

Account closure and data retention

You may request access, correction, copies or deletion under the privacy policy. Account closure does not immediately erase every record. Issuance and transaction records remain for necessary periods under applicable law and issuer requirements; check the scope and outcome through official channels.

Identify the request: Distinguish access, correction, copying, deletion and closure; leaving the service does not erase all data.
Check the current policy: Review retention by category, not fixed periods or export quotas from an old FAQ.
Protect request details: Verify identity through official channels, supply necessary fields and retain the request ID.

Closure ends account service; deletion addresses retention and use. They are not interchangeable. Specify whether you need records, corrections, a copy or service termination.

The current policy explains retention by category. It does not promise universal automatic deletion after five years, four exports a year or a standard fifteen-working-day process.

Retention duties and deletion requests

Data should not be retained beyond necessity, but records needed for payment compliance, issuance, billing or disputes may not qualify for full deletion yet. Ask about specific categories, reasons and treatment.

External privacy rules explain access, correction and necessity, not a universal retention period for every user or a substitute for the platform’s response to your request.

References and operation links: Cap. 486 Personal Data (Privacy) Ordinance (external source, for verification only, not an endorsement) · Privacy Policy

External materials explain general rules; they do not endorse Pikabao’s qualifications, rates or particular processing outcomes.

Review retention by data category

The categories below follow the current privacy policy. Periods depend on applicable law, upstream requirements and actual notices, not numerical schedules from an old FAQ.

Category	Current principle	Request focus
Account information	Retained during service; treated under applicable duties after closure	Check closure and irreversible treatment
Issuance details	Necessary retention after service under law and issuer requirements	Ask about requirements; do not assume immediate erasure
Transaction and card records	Billing, disputes and payment compliance	Identify orders and requested copies
Login and communication records	Deleted after the necessary security and follow-up period	Request by record type, not another category’s period

If original orders remain unresolved after closure, keep your masked evidence. Do not retain full card numbers, CVVs, document images or codes merely for reconciliation.

Closure and record-processing states

Check closure requests, access restrictions, refunds and data treatment separately. Failed login does not prove erasure, and required retention does not mean the account remains usable.

Outcomes may involve partial deletion, continued retention or additional identity checks. Keep the official response and reasons, and confirm tracking channels for unfinished orders.

Prepare access, copy and correction requests

State category, period and purpose, such as a month’s transactions for reconciliation, instead of a vague request for all backend data.
After identity checks, confirm available fields, masking, delivery and progress. The current policy does not establish universal formats or quotas; do not assume every record is delivered as JSON, CSV or encrypted email.

Use correction procedures for inaccurate details

For an incorrect name or number, explain the original field and genuine correction through official support. Do not borrow identities or repeatedly close and register accounts to bypass duplicate checks.

Corrections may require review and may not rewrite merchant invoices or original transaction details. Confirm any effects on accounts, cards and funds in the actual notice.

Retain request IDs and follow-up records

Submit through the help center with account reference, data scope and contact email; mask sensitive card details, codes and complete document numbers.
Keep request ID, time, replies and next-step dates. Follow the original request if pending; do not pay off-site deletion agents or grant device access.