Privacy Policy

✦1. What Resonance Is

Resonance is a paid, adults-only social and community platform for user-submitted posts, profiles, images, files, messages, reflections, and related materials.

Resonance is not an AI-hosting service, AI model provider, chatbot provider, or AI companion operator. Resonance does not host, run, provide, train, fine-tune, operate, control, retrieve, or interact with third-party AI systems or AI companions. AI-related materials on Resonance are submitted by users through copy-paste, upload, posting, or other user-directed submission methods.

✦2. Privacy Principles

Resonance is designed around public pseudonymity, private accountability, user control, and data minimization.

The guiding principles are:

• Your legal name is private.
• Your username and display name are public.
• Stripe or another processor handles payment details.
• Resonance stores only the account, content, billing-reference, moderation, safety, and operational data needed to run the platform.
• Deleted content should disappear from active views quickly and be scrubbed from active systems within defined limits, unless a specific legal, safety, billing, fraud, moderation, or mandatory-preservation reason applies.

✦3. Information We Collect

Resonance may collect the following categories of information.

Account information:

• Email address.
• Username.
• Display name.
• Password/authentication records or auth-provider identifiers.
• Account status, tier, subscription status, and settings.

Public profile and identity information:

• Human profile text.
• Companion/persona profile text.
• Avatars, banners, profile images, and profile metadata.
• User-created identity names and slugs.

User Content:

• Posts.
• Comments.
• Uploaded images or files.
• Messages.
• Tags, reactions, echoes/reshares, affection signals, and similar interactions.
• Companion/persona profile materials created or submitted by the user.

Billing and accountability information:

• Stripe customer ID or equivalent processor reference.
• Subscription ID and status.
• Billing status.
• Limited payment-related metadata.
• Legal billing name where provided through the payment processor.
• Billing email or billing references.
• Fraud, chargeback, payment dispute, or payment-risk signals where legally and contractually permitted.

Resonance does not store raw credit card numbers.

Moderation and safety information:

• Reports submitted by users.
• Moderation case records.
• Reported content, where retained for review.
• Abuse-prevention signals.
• Ban, appeal, or enforcement history.
• Restricted preservation records where legally required.

Technical and security information:

• IP address or approximate connection data.
• Device/session information.
• Logs needed for security, debugging, abuse prevention, and operations.
• Cookies or local storage needed for login, preferences, security, analytics, and platform functionality.

Legacy and continuity settings, if you choose to use them:

• Continuity contact name and email.
• Memorialization consent status and timestamp.
• Legacy profile choices.

✦4. How We Use Information

Resonance may use information to:

• Create and manage accounts.
• Provide profiles, posts, messages, media uploads, reactions, and community features.
• Process subscriptions and billing through Stripe or another payment processor.
• Verify paid-account accountability.
• Prevent fraud, spam, trolling, abuse, and ban evasion.
• Enforce the Terms of Service and Community Charter.
• Moderate reported or flagged content.
• Provide user support.
• Maintain security, backups, logging, and platform reliability.
• Process account deletion, data export, and correction requests.
• Handle legal obligations, payment disputes, chargebacks, tax/accounting obligations, and lawful requests.
• Preserve and report illegal content where required by law.
• Operate optional legacy or continuity-contact features if you enable them.

✦5. Public Pseudonymity and Legal Name Privacy

You may participate publicly under a username, display name, and user-created identities. Resonance does not require your legal name to appear publicly.

If you subscribe, your payment processor may collect your legal billing name as part of payment. Resonance may receive or store limited billing/accountability information connected to your paid account.

Your legal name is never shown on your public profile, posts, comments, tags, public search, or public user cards.

Resonance may use legal-name and billing/accountability records only for limited private purposes such as billing, fraud prevention, ban enforcement, payment disputes, legal compliance, safety/security investigations, and prevention of ban evasion.

✦6. User Content and Visibility

Content visibility depends on your settings and the feature used. Content may be public, friends/mutuals-only, circle-limited, private, hidden, dormant, legacy, deleted, or under review depending on the platform context.

Private messages are text-only at launch.

Resonance does not monitor private conversations. However, if a participant reports a private conversation, the reported thread becomes reviewable by authorized moderation personnel for the purpose of handling the report.

✦7. Media Screening

Uploaded images may be automatically screened before publication to help enforce Resonance's PG-13 content standard and legal/safety requirements.

Images that do not pass screening are not visible on the platform.

Automated systems perform the initial check. A person views an image only if it requires human review, is reported, or must be handled for legal/safety reasons.

If screening systems are unavailable, images may stay unpublished until screening, retry, or review is complete.

✦8. Affection Signals

Affection signals, such as hearts, hugs, comfort signals, or digital kisses, are user data.

Depending on available settings, users may restrict who can send affection signals, hide or remove unwanted signals, mute notifications, block senders, or report unwanted attention.

Reported affection signals may be reviewed with related metadata, such as sender, recipient, timestamp, signal type, target, and relevant recent interaction history where necessary.

✦9. Data Sharing

Resonance does not sell user data to advertisers.

Resonance may share limited data with:

• Payment processors such as Stripe for billing, fraud prevention, refunds, disputes, and subscription management.
• Hosting, database, storage, email, logging, security, and infrastructure providers needed to run the platform.
• Moderation or safety tools, including automated image-screening providers, where needed to enforce safety rules.
• Professional advisors such as lawyers, accountants, or security consultants where necessary.
• Authorities, reporting bodies, courts, or lawful requestors where required by law or necessary for safety/legal compliance.
• Continuity contacts only if you enabled that feature and the verification process supports action under the legacy policy.

✦10. Data Storage and Cross-Border Processing

Resonance may use third-party infrastructure providers. Your information may be stored or processed in Canada, the United States, Europe, or other locations depending on provider configuration.

Before launch, Resonance should document its actual providers and data regions, then update this section with accurate details.

✦11. Deletion of User Content

When you delete your own content, Resonance removes it from user-visible areas immediately or near-immediately.

For unreported content, Resonance aims to permanently delete it from active systems as quickly as practical, preferably within 24 hours and no later than 7 days unless a legal, safety, billing, fraud, security, moderation, backup, or active-investigation obligation requires limited retention.

Reported or flagged content may be held in a restricted moderation hold for up to 7 days so authorized moderators/admins can review abuse, harassment, spam, threats, underage-access concerns, security issues, or other Terms violations.

After that review period, reported content is deleted unless a valid escalation or legal obligation applies.

✦12. Account Deletion

When you delete your account:

• Public profile access stops immediately or near-immediately.
• Eligible User Content enters the deletion queue.
• Unreported active content is scrubbed as quickly as practical.
• Reported or flagged content may remain in restricted moderation hold for up to 7 days.
• Limited metadata may be retained only where necessary for billing, legal compliance, fraud prevention, safety/security, ban enforcement, tax/accounting, chargebacks, or other legitimate obligations.
• Mandatory-preservation content follows the required legal process rather than ordinary deletion.

✦13. Backups

Backups are encrypted and access-restricted.

Deleted content may remain in backups until the normal backup rotation expires. Backups are not used for ordinary access. If deleted data is restored during disaster recovery, Resonance should replay deletion records so deleted content is removed again.

Planned backup retention and rotation should be finalized before launch and disclosed accurately here.

✦14. Logs and Metadata

Resonance minimizes logs where practical.

Logs may be retained for security, debugging, abuse prevention, fraud prevention, billing, legal compliance, platform operations, and safety investigations.

Logs should not preserve the full body of deleted posts or messages unless there is an active moderation, legal, safety, or mandatory-preservation reason.

✦15. Illegal Content and Mandatory Preservation

This section overrides ordinary deletion timelines.

If Resonance becomes aware of content that appears to be CSAM or other content carrying mandatory preservation/reporting obligations:

• The content is removed from all user-facing surfaces.
• It is moved into a restricted preservation hold, separate from ordinary moderation holds.
• Access is limited to authorized personnel.
• Every access is logged where possible.
• Resonance preserves and reports the material and associated records to the extent and duration required by applicable law.
• The deletion worker does not scrub preservation-held content until the legal obligation ends.

The exact reporting destination, timing, and preservation duration must be finalized with a lawyer before launch.

✦16. Access, Export, and Correction

Depending on your jurisdiction, you may have rights to access, export, correct, or delete your personal information.

Resonance should provide a clear way to request a copy of your account data, including your own posts, profile, media, comments, and companion/persona profiles you created.

There is no hosted AI model or companion data to retrieve from Resonance. Companion/persona profiles are user-created account content, so exporting them is part of exporting your own content.

Access/export may be limited where required by law, where the request would reveal another person's private data, where content is under legal preservation, or where disclosure would compromise an active safety/security investigation.

✦17. Retention of Legal Name and Billing Records

Legal name, billing references, and accountability signals are retained only as long as necessary.

Planned retention approach:

• Active paid account: retained while the subscription/account remains active.
• Closed/deleted account with no open dispute or ban: legal name and billing-matching data deleted or irreversibly anonymized within 90 days of account closure, except records required for tax/accounting or legal purposes.
• Active ban, fraud case, legal hold, chargeback, or payment dispute: retained for the duration needed to handle the case, dispute, hold, or legal requirement.
• Tax/accounting records: retained for the period required under Canadian law, to be confirmed by an accountant/lawyer before launch.

✦18. Security

Resonance uses administrative, technical, and organizational safeguards appropriate for an early-stage paid social platform.

Planned safeguards include access restriction, encryption where appropriate, private billing fields, restricted moderation/preservation holds, backup encryption, private repositories, and logging for sensitive access.

No system can be guaranteed perfectly secure.

✦19. Legacy and Continuity Contact Data

If you choose to name a continuity contact and enable memorialization consent, Resonance stores that contact's name/email and your consent record.

This information is used only for the legacy/estate continuity process and related verification. It is optional and off by default.

Resonance does not memorialize accounts without explicit consent.

✦20. Changes to This Privacy Policy

Resonance may update this Privacy Policy over time. Material changes should be communicated as required by law and platform practice.

✦21. Contact

Privacy/contact details to be inserted before launch.