Privacy / Actual system boundaries

Public evidence and private operations stay separate.

This page describes the data handled by RocketFang LLC while operating Ad Space Atlas. It does not replace the separate terms for an Atlas sponsorship.

Last reviewed 1 September 2026

The short version

Atlas publishes reviewed catalog facts—not private request or payment details.

Public listings retain their source, observation time, extraction method, and verification state.
Submission, correction, claim, sign-in, and order records are not public catalog data.
Stripe receives card and payment credentials directly; Atlas does not receive card numbers.
Opaque receipts are excluded from product analytics, caching, and search indexing.

01 / Public catalog

Evidence is historical.

Atlas stores public URLs, source snapshots, extracted observations, review decisions, and published projections. Earlier evidence is normally retained when a current listing changes or is archived so the catalog does not rewrite history.

02 / Requests and accounts

Intake details stay private.

A submission includes its public destination and request identifier. Corrections and ownership claims can also include contact details, explanations, and evidence links. Invited users provide an email for a single-use sign-in link, and authenticated sessions use secure cookies.

03 / Sponsorship orders

Atlas stores what fulfillment needs.

Atlas records the buyer email, company and campaign copy, destination, optional UTM values, immutable price and date terms, provider identifiers, creative bytes and hashes, payment state, moderation, and refund history. A creative remains quarantined until approval; only approved campaign material becomes public.

04 / Service providers

Infrastructure has narrow jobs.

Cloudflare hosts the site, Workers, database, object storage, abuse checks, and transactional email path. Stripe hosts checkout and processes payment and refund events. Atlas verifies signed Stripe events before changing payment state.

05 / Product analytics

Only allowlisted public routes emit events.

The production site uses Google Analytics for a small public-route event vocabulary. Page events contain a path without its query string; search terms, emails, source URLs, receipt IDs, and request bodies are excluded. Google Signals, ad personalization, and automatic page views are disabled. Private and unknown routes do not emit Atlas analytics events.

06 / Retention and requests

There is no invented deletion deadline.

Atlas retains evidence and operational history while it remains useful or required for catalog integrity, fulfillment, security, accounting, disputes, and applicable obligations. To ask about access, correction, removal, or a sensitive-data exception, email support@adspaceatlas.com.

Related controls

Receipts are bearer links.

Keep an opaque receipt URL private. It intentionally shows a limited status view without buyer contact data. For sponsorship-specific commitments, read the advertising policy.