Skip to main content
Gather HQs
  • Help
  • Sign in
  • Start free trial
← Legal center

Pre-launch policy draft — legal review required before public launch

Data Retention & Deletion

How Gather HQs balances active service needs, safe deletion, subscriber export, financial integrity, consent evidence, legal obligations, and backup recovery.

Effective date
July 30, 2026
Applies to
Gather HQs and subscriber sites

Policies

Terms Privacy Cookies Payments & refunds Acceptable use Retention Security Reviews

Questions?

For an event, ticket, membership, or subscriber-held record, contact the group that operates the subscriber site first.

support@gatherhqs.com

1. Retention principles

Gather HQs keeps information only as long as reasonably needed to provide and secure the Service, honor subscriber and attendee requests, preserve reliable financial and consent history, resolve disputes, prevent fraud, meet legal obligations, and recover from operational failures. Different records require different periods.

2. While a site or account is active

Account, site, content, contact, event, registration, participant, attendance, membership, campaign, review, task, file, form, and related operational information is generally retained while the applicable account or subscriber site remains active and as needed afterward for the purposes in this policy.

Subscriber administrators can download a site data export where the Service provides one. An export may not include provider-controlled information, credentials, internal security data, or data that belongs to another person or tenant.

3. Cancellation, suspension, and deletion requests

Canceling a platform subscription stops future renewal as configured in the billing portal; it does not instantly erase a subscriber site. Immediate deletion could destroy refund, dispute, attendance, consent, safety, or tax evidence and could be difficult to reverse.

A site must be suspended, canceled, or archived before platform deletion can be requested. One platform administrator records the request and reason. A different platform administrator must approve it. After approval, the request remains cancelable and cannot be executed for at least 90 days. The final deletion action requires separate operator confirmation of the exact site.

This safeguarded period is a minimum operational hold, not a promise that every record will be erased exactly on day 90. A request may be delayed when preservation is reasonably required by law, dispute, fraud investigation, security incident, court order, tax or accounting rule, provider obligation, or another documented exception.

4. Records that may be kept longer

Even after public content or an account is removed, Gather HQs or the relevant subscriber may retain limited records such as:

  • orders, tickets, subscription invoices, refunds, disputes, application fees, payout references, and related financial transitions;
  • communication consent, withdrawal, unsubscribe, suppression, complaint, and delivery evidence;
  • security, authentication, moderation, support-access, export, deletion, and audit records;
  • agreement, waiver, attendance, incident, or event records needed for a valid legal or safety purpose;
  • information needed to detect duplicate abuse, enforce a restriction, or defend legal claims; and
  • de-identified or aggregated information that no longer identifies a person.

Access to retained records is limited according to role and purpose. Retention does not permit use for an unrelated purpose.

5. Messages, links, and temporary records

Invitation, response, checkout, unsubscribe, and review capabilities are designed to expire, be revocable, or be stored in hashed form where the workflow permits. Message bodies awaiting delivery are retained long enough for delivery and troubleshooting, then redacted after successful delivery or terminal failure under current operating rules. Provider identifiers and delivery status may remain for audit and suppression purposes.

Payment inventory holds and other temporary workflow records expire or are released under their applicable service rules. Expiration of a link does not necessarily delete the underlying event, consent, order, or attendance record.

6. Backups and provider systems

Encrypted or access-controlled backups are retained on a limited recovery cycle determined by the production infrastructure configuration. Deleted information may remain in a backup until that backup expires, but it is not restored to ordinary use unless needed for disaster recovery and remains subject to this policy.

Stripe, email providers, hosting providers, and other independent or contracted services retain information under their own legal and operational requirements. A Gather HQs deletion does not automatically erase a record another provider is legally entitled or required to retain.

7. Individual requests

For information held by a subscriber group, contact that group first. For a Gather HQs account or platform-controlled record, contact support@gatherhqs.com. We may verify identity, account ownership, or authority before exporting, correcting, or deleting information. We will explain an applicable exception when the law requires us to do so.

Contact

Gather HQs
support@gatherhqs.com

The approved public mailing address must be configured before launch.

© 2026 Gather HQs
Legal center Privacy Terms Payments & refunds Acceptable use Review guidelines Support