Privacy Policy

Information We Collect

• Account details such as name, email, and optional teaching contexts provided during signup or in Profile.
• Decks and cards; seminar settings; team nicknames, icons and technical membership identifiers; card choices, ballots, nominations, scores, rounds, and Atlas records.
• Text entered into Map explanations, reflections, voting annotations, Atlas annotations, team notes, and host notes, together with moderation and read status. Although Maps may be made and shared in the classroom, text entered into these app features is stored by the service.
• Subscription status, product, renewal, cancellation, refund, and provider identifiers associated with paid billing.
• Technical data such as device information, log data, and limited product-lifecycle analytics.

How We Use Information

• To operate, maintain, and improve the platform and its features.
• To provide support, communicate updates, and respond to inquiries.
• To protect the security of the service and comply with legal obligations.

Who Can See Classroom Records

Hosts can access their own seminars and the team writing submitted within them. Teams can access their own private writing and the records made available to seminar members. Ballot annotations are delivered to their recipients after host approval and the relevant reveal; approved freeform team notes can be delivered during active play. A note sent to multiple teams receives one moderation decision, with a separate delivery for each recipient. Atlas annotations become visible when approved. Exported reports can include released gameplay and approved writing.

Unsubmitted freeform team-note drafts are saved in this browser, rather than sent to the server. Existing Map explanations and reflections use server saving. Authorized service administration and support may access records when necessary to operate, secure, or support the service. Submitting a deck to the public Library is a separate, explicit publication process.

Sharing and Disclosure

We do not sell personal information. Google Firebase provides hosting, authentication, database storage, and server processing. These services process technical identifiers and request information, including IP addresses and device or browser information, for operation and security. Our primary classroom database is configured in the United States multi-region; this is not a guarantee that all provider processing occurs in one location. Lemon Squeezy acts as Merchant of Record and receives account and billing information needed to process checkout, subscription management, tax, receipts, payment recovery, cancellations, and refunds. Atlas Seminar does not receive or store full card details. We may share data with service providers who assist in operating the platform, or if required by law or to protect the rights, safety, and security of users.

Data Security and Retention

Atlas Seminar implements HTTPS encryption in transit, Firebase encryption at rest, and enforced host/team permissions through database security rules and server checks. Private invitation links are access credentials and should be shared only with their intended teams. Database deletion protection guards against deletion of the whole database. Seven-day point-in-time recovery and daily backups configured for 30-day retention support resilience; they do not replace access controls.

We retain classroom records until the host deletes the relevant deck or seminar, or a deletion request is processed. There is no automatic classroom-record expiry in this version. A plan downgrade, cancellation, or moving items into Shelf Vault does not delete them. Deleting a deck does not delete an existing seminar’s snapshot of that deck or copies previously published or added through the Library.

Deleting a seminar removes its live seminar records and associated Atlas. Cleanup can take time and can be retried if interrupted. Minimal ownership and deletion-status records are retained to authorize cleanup retries without retaining the deleted classroom text. Deleted records may remain in point-in-time recovery for up to seven days and configured backups for up to 30 days. If a backup is restored, deletion requests must be accounted for before restored data is returned to use.

Authentication records, billing records, security logs, and provider backups are handled separately from classroom documents. Their retention follows the relevant provider processes and any applicable operational or legal requirements. Deleting a seminar is not the same as deleting a host account or its authentication records. See Firebase’s privacy and data-processing information for provider handling.

Product-lifecycle event records contain account/resource identifiers, milestones, and timestamps, rather than report text, cards, or classroom submissions. These events are assigned an expiry 18 months after collection; database expiry cleanup is asynchronous. This period does not describe classroom content, aggregate statistics, or every operational log.

Browser drafts and downloaded reports are local copies. Deleting server records does not remotely erase downloads or drafts on other devices. On shared devices, remove local drafts or site data and manage downloaded reports separately.

Your Choices

Hosts can delete decks and seminars from the Shelf. For account deletion, privacy questions, or assistance removing information entered into a classroom record, contact the address below. We will verify the request and explain its scope, including separate provider records and backup retention. We do not promise that every copy disappears immediately when a live record is deleted.

Newsletter

The optional newsletter form is operated by Substack. Loading the embedded form makes a third-party request to Substack before form submission. Atlas Seminar does not send Atlas account details to it or receive, store, transfer, or reconcile newsletter signup, confirmation, delivery, or unsubscribe data. Manage a newsletter subscription through Substack.

Contact

For privacy questions or requests, email support@atlasseminar.com.