Document record
The current version of this document.
- Record
- ASCA Public Legal Record · 2025.08
- Applies to
- Users and Organizations
- Acceptance context
- Applies Through the Governing Terms and Service Context
- Effective and updated
- August 12, 2025
- Version history
- Replaces the January 28, 2025 version
Effective policy. This document is effective August 12, 2025. Replaces the January 28, 2025 version.
Retention principles
ASCA retains information according to its purpose, sensitivity, organization relationship, configured feature, service tier, security value, transaction state, dispute status, and legal requirements.
Customer-visible context limits do not require ASCA to delete separate security, payment, audit, legal-preservation, or incident records prematurely. Those protected records are not presented as customer context features.
Record classes
| Record class | Typical retention basis |
|---|---|
| Public content | While published, plus version and removal evidence |
| Account and profile | Active relationship, recovery, closure, and applicable request period |
| Organization operations | Organization need, authority transition, contractual and legal requirements |
| Customer-visible context | Selected configuration and applicable plan maximum |
| Transactions and billing | Reconciliation, refund, dispute, tax, accounting, and legal need |
| Security and abuse | Threat detection, incident investigation, evidence, prevention, and legal preservation |
| Support and legal requests | Case resolution, audit, dispute, and required preservation |
| Backups | Bounded recovery cycle followed by overwrite or secure expiration |
Moderation and connected content
Moderation services may retain configured usable context for the period selected by the organization up to the applicable service limit. Separate security and service-integrity evidence may be retained for a longer period where needed to investigate abuse, protect users, maintain auditability, improve safety and reliability, or meet legal obligations.
This policy describes retention by purpose and record class. It does not expose confidential technical, evidence-protection, or security architecture.
Organization and account closure
Closing an individual account does not automatically delete records that an organization must continue to administer or that ASCA must retain for security, transactions, disputes, safety, or legal preservation.
Organization closure requires verified authority and a transition plan covering administrators, exports, integrations, pending transactions, public content, security records, and remaining retention obligations.
Export
Where supported and authorized, ASCA may provide account or organization data in a commonly usable format. Export scope depends on identity, authority, another person’s rights, organization ownership or stewardship, security, and the selected service.
Exports may exclude secrets, security detection material, privileged records, another organization’s information, internal provider data, or information that cannot lawfully be disclosed.
Deletion and de-identification
When deletion is approved, ASCA deletes, redacts, or de-identifies applicable active records and schedules protected copies for expiration. A request may be limited or delayed when information remains necessary for:
- Security, fraud prevention, abuse investigation, or incident response.
- Transaction reconciliation, refunds, disputes, tax, or accounting.
- Legal hold, valid legal process, or the establishment or defense of claims.
- Organization recordkeeping and the rights of other users.
- Demonstrating consent, authority, voting, safety, or policy history.
ASCA records completion or the reason for a lawful exception.
Service providers
ASCA requires applicable service providers to follow scoped processing and deletion or return obligations. Provider backup and deletion cycles may require time to complete. Connected services independently control information they hold outside ASCA.
Review and contact
Retention schedules must be reviewed when a service, provider, legal requirement, risk, or purpose changes. Questions and requests may be sent to [email protected].