Summary
Two different worlds:
Website data (marketing site, help center, checkout) → used to understand traffic and improve the signup experience.
Product & usage data (your phone service) → runs on REALLY’s PrivateCore™ with no PII, no centralized, identity-linked archive, short retention, and no monetization.
Hard boundary. Website analytics never flow into your phone-service records. Host networks don’t receive any identifier mapping from us, and Aura does not receive telco usage data.
Control on the marketing side. You can reduce/stop website tracking using browser settings, tracker blockers, or Tor: https://www.torproject.org/download/
Bottom line. We spend marketing dollars to reach people who want a better carrier—but we don’t mix that with your phone-service data. Your service stays private by design.
The Critic’s Question
“Are you tracking me for ads? Is my browsing on your website tied to my phone-service usage or identity?”
Why This Distinction Matters (Plain English)
Most companies blur the lines between marketing analytics and product/usage data. We don’t. We separate them so your phone-service privacy isn’t affected by how you browse our website.
Website data helps us answer: “Did this page load fast? Which checkout step is confusing? Which ad campaign brought folks here?”
Product & usage data is what’s required to run a phone line: authenticate a SIM, route calls, handle billing, support, and security.
Keeping these worlds separate protects you from adtech creep and “shadow profiles.”
What We Collect on the Website (and Why)
Purpose: make the site useful, measure performance, and understand high-level funnels.
Typical website signals (examples):
Page views/loads, device/browser type, coarse geolocation (e.g., city), referral source, A/B test group, checkout step completion/fail.
If you submit a form or join a waitlist, we store only what you provide for that purpose (e.g., email).
What we don’t do on the website:
We don’t merge website analytics into your phone-service records.
We don’t collect sensitive PII by default.
We don’t sell your data to brokers.
Your controls:
Browser tracking prevention (Safari/Firefox/Brave), content blockers (uBlock Origin, etc.).
Adjust cookie preferences (when presented).
Browse via Tor if you want stronger IP/network privacy: https://www.torproject.org/download/
What We Collect for Phone Service (and Why)
Principle: If it’s not required to deliver service or meet a legal duty, we don’t collect or keep it.
Anonymous account (no PII), plan & SIM details, payment tokens/receipts (no full card numbers).
Network operations events (technical only) to authenticate and route service.
Security signals for SIM-swap and fraud defense.
We do not:
Build a centralized, identity-linked archive of your historical usage.
Share account↔network identifier mapping with host networks.
Monetize customer data.
Retention: Minimal and short-lived, with a published Retention Matrix (plain English).
Hard Boundaries (What Never Crosses)
Website → Product/Usage: Website analytics do not join to your phone-service records.
Product/Usage → Aura: Aura does not receive telco usage data (no CDRs, no tower history, no subscriber mapping).
Product/Usage → Host: Hosts (towers) see radio technical events but don’t receive our account↔identifier mapping.
No adtech pipes from phone-service systems. Ever.
Practical Examples
1) You read our coverage page and click “Get Started.”
We see that the page was visited and a button was clicked so we can improve the funnel.
None of this touches your phone-service data (which doesn’t exist yet).
2) You sign up with an anonymous account and activate a SIM.
Your line runs our PrivateCore™; we collect the bare minimum to operate it.
This data stays separate from website analytics.
3) You turn on Aura’s VPN.
Aura gets only what’s needed for that feature (e.g., the email you provide).
Aura does not get telco usage data from us.
4) You want less website tracking.
Use a tracker blocker, limit cookies, or browse via Tor.
Big Wireless vs. REALLY (At a Glance)
Topic | Big Wireless (typical) | REALLY |
|---|---|---|
Website ↔ Product data mix | Often blended | Separated by design |
PII at signup | Common | Anonymous (no PII) |
Identity-linked archives | Centralized, long-term | No centralized, identity-linked archive |
Host access | Broad | No mapping sent to hosts |
Data monetization | Common | None |
Retention | Multi-year | Short, purpose-bound TTLs |
FAQs
Does visiting your site affect my phone-service privacy?
No. Website analytics are separate and never merged with your service records.
Do you sell my data?
No. We don’t monetize customer data, website or product.
If I use Tor on your website, will my service still work the same?
Yes. Website browsing method has no impact on how your phone service is delivered.
Does Aura see my telco usage?
No. Aura doesn’t receive CDRs, tower history, or any subscriber information not given by you.
Can the host network tie tower events to me?
Not via us. We don’t send any account or identifier mapping to hosts.
Wrap-Up
We separate marketing analytics from phone-service data so your service privacy never depends on how you browse our site. Your line runs on anonymous accounts, no one-stop identity-linked archive, short retention, and no monetization, with clear boundaries to hosts, Aura or other partners.
Want no web analytics at all? Use blockers or Tor. Your phone service remains private either way.
Proof & verification (in progress)
Policy:
Public Website vs. Product Data statement defining systems, purposes, and what never crosses.
No-Monetization Statement (website & service).
No-PII Signup policy for service accounts.
Audit:
SOC 2 / ISO 27701 summaries covering access, logging, retention, vendor controls.
Quarterly reviews confirming no analytics identifiers are ingested into service systems.
Tests:
“Join test” showing website IDs cannot be used to query service records.
TTL drills confirming website logs and service logs follow independent retention.
Network inspection validating no telco usage data sent to Aura.
Transparency:
Public Retention Matrix (site vs. service).
Privacy/security changelog (e.g., “removed web pixel X,” “reduced TTL on site logs”).
Join the only carrier that makes privacy non-negotiable.
