Privacy Policy

App Store “App Privacy” & Google Play Data safety (summary)

When you complete Apple’s App Privacy labels or Google Play’s Data safety form, the categories you declare should match what you actually collect. For AIW’s current mobile and web model, typical declarations include (non‑exhaustive — verify against your build and SDKs):

• Identifiers — account IDs, Google subject identifier for sign‑in, session tokens, device/app identifiers the OS exposes.
• Purchase history — subscription state / eligibility (from Apple or Google; not full card numbers).
• User content — comments, stories, or other content you submit.
• Usage data — interactions with the site or app, diagnostics, approximate location from IP where collected.
• Advertising data — only if you ship ad SDKs (for example AdSense on web); declare partners and purposes per their docs.

Purposes usually include app functionality, analytics, fraud prevention, personalization, and (if applicable) third‑party advertising. Cross‑check the detailed sections below and your integrated SDK documentation when completing storefront forms.

Who we are & scope

AIW operates the editorial and community storytelling platform marketed as “Am I Wrong?” For privacy inquiries, contact: contact@amiwrong.net. Capitalized terms where cross‑referenced follow our Terms of Use.

Information we collect

The categories listed below overlap with disclosures you’ll provide in storefront privacy/data forms (Apple App Privacy, Google Play Data safety).

• Identifiers and account data: When you authenticate with Google for web dashboard/mobile account flows, we may receive your name, email address, subject identifier/token from the provider, and profile image URL. We associate this with internally generated identifiers.
• Mobile playback credentials: We generate and store a username and password pair (or successor credential) strictly to sign in to the AIW apps for audio access. Passwords are stored using industry-standard hashing where applicable (you should never share passwords).
• Content you submit: Stories (if submission is enabled), comments, contact form messages, and similar volitional posts.
• Commercial / subscription signals: We do not process your payment card numbers for mobile subscriptions (Apple/Google do). We may receive minimal metadata from storefronts indicating subscription state (for example eligibility for audio playback, trial/active/expired cues) and transaction identifiers as required to operate entitlement.
• Technical & usage data: IP address (may be shortened or hashed), approximate location derived from IP, browser/app type, OS, device identifiers the platform exposes, referrer, pages/screens viewed, interaction events, timestamps, diagnostics, crash logs where enabled, cookies or local storage keys, session IDs.

Sources of collection

• You, when you submit information or sign in;
• Your device and browsers automatically;
• Identity/sign-in platforms (such as Google);
• Apple or Google billing platforms (limited subscription status);
• Analytics/advertising SDKs/partners where present (see Cookies & advertising).

Purposes of processing

• Operate, secure, troubleshoot, personalize, and improve the Services;
• Authenticate accounts, provision mobile credentials, and enforce entitlement to paid features;
• Moderate content, investigate abuse/fraud/legal requests, comply with applicable law;
• Communicate with you about policies, notices, incidents, support requests;
• Measure aggregated usage and efficacy of features;
• Show advertising where activated (consistent with publisher policies).

Legal bases (EEA, UK, Switzerland)

For individuals in those regions where GDPR/UK GDPR or Swiss law applies:

• Contract necessity — running the Services you requested (accounts, entitlement, transactional emails);
• Legitimate interests — moderation, analytics that are not intrusive, fraud prevention and security;
• Consent — where legally required or where we explicitly ask before placing non‑essential cookies/ads personalization;
• Legal obligation — responding to lawful government requests;
• You may lodge a complaint with your local supervisory authority; you also have GDPR/UK GDPR rights summarized below.

Sale / sharing of personal information for advertising (U.S.)

We do not sell personal information for money. Where U.S. state laws define “sale” or “sharing” (such as CPRA/CCPA‑style disclosures for cross‑context behavioral advertising through third‑party SDKs/ad tags), use of certain advertising/analytics vendors may constitute “sharing”; you may opt out of those technologies to the extent feasible via cookie controls, OS settings (“Limit Ad Tracking” / “Ask App Not to Track”), partner opt‑out portals, or by contacting us. We honour applicable statutory signals where required.

In‑app purchases (Apple/Google)

Transactions on mobile occur through Apple or Google billing. They process payment instruments and contractual purchase records pursuant to their own privacy policies: Apple Privacy Policy, Google Privacy Policy. We retain only limited records needed for provisioning and support.

Sharing with service providers & third parties

We share information with subprocessors/hosting, security providers, moderation tooling, analytics/ads SDKs integrated into our apps/sites, analytics platforms, Customer identity/OAuth providers (for example Google), email delivery vendors, fraud prevention, and advisors where necessary. Contracts require safeguards and limited use.

If we reorganize or are acquired we may assign information as part of a merger or asset sale with notice consistent with applicable law.

International transfers

Depending on deployment, servers or processors may be located in countries outside your jurisdiction, including the United States. Where required by law (for example GDPR), transfers from the EEA/UK/Switzerland rely on safeguards such as the EU Commission‑approved Standard Contractual Clauses, UK IDTA/addendum equivalents, Swiss adequacy, or other transfer tools. You may contact us for a summary of safeguards.

Retention

We retain data only as long as necessary for operational, legal (tax/accounting/evidence preservation), moderation, contractual, or legitimate security purposes described in this policy. Deleted accounts may persist in encrypted backups briefly. Historical comments may persist in anonymised form when removal is technologically complex or mandated to remain for legal defenses.

Security

We deploy administrative, technical, and organisational measures reasonably appropriate to risks (encryption in transit TLS, hashing for secrets, restricted access roles). No method of transmission/storage is guaranteed secure; notify us promptly if you suspect account compromise at contact@amiwrong.net.

Cookies & advertising identifiers

Websites may use strictly necessary cookies, analytics cookies (where opted or allowed), functional cookies remembering preferences. Third‑party advertisers (such as Google AdSense if deployed) maintain their cookie policies consent frameworks in supported regions (TCF banners where triggered). Apps may expose advertising identifiers to ad/MMP partners subject to SDK documentation and parental controls.

Your privacy rights — EEA, UK, Switzerland

You may request:

• Access to categories/specific pieces of processing;
• Rectification of inaccuracies;
• Erasure (“right to be forgotten”) subject to exemptions;
• Restriction or objection where grounds apply;
• Data portability in structured machine‑readable formats where feasible;
• Withdraw consent without affecting lawful prior processing;
• You may complain to your supervisory authority (for example in the UK: ICO).

Exercise rights via contact@amiwrong.net with subject line Privacy request. We verify identity appropriately.

California residents — supplemental notice (CPRA/CCPA‑style categories)

Residents of California have additional rights summarized here; we follow CCPA as amended (“CPRA”) conceptually although final interpretation depends on regulations. Categories may include Identifiers (A), Protected classifications (minimal), Commercial information regarding subscriptions (transactions via stores), Internet activity (interaction), Audio/electronic if you engage audio uploads (if any geolocation inferred from coarse IP qualifies as Approximate geo). No sensitive personal information is collected for sale; any sensitive‑like inference is minimized.

• Right to Know / Access: obtain categories and specific pieces disclosed.
• Deletion: request deletion subject to exemptions (legal holds, transactional evidence).
• Correction: inaccuracies.
• Opt‑out of Sale/Sharing: we do not sell for money—see Sharing section regarding advertising‑related sharing/opt‑out avenues.
• Limit use of Sensitive PI: not materially applicable given current offerings.
• Non‑discrimination: we won't penalize lawful requests.
• Authorized agents may submit with proper proof.

Submit requests via contact@amiwrong.net titled California privacy rights. Appeals (if denial) handled per statute.

Shine the Light disclosure: California’s “Shine the Light” (Civil Code §1798.83)—we currently do not share personal info with third parties for their independent direct mail marketing absent your opt‑in.

Residents of other U.S. states

If you live in a state with a comprehensive privacy law (examples: Virginia, Colorado, Connecticut, Utah, other states as enacted), you may have rights to access, correct, delete, opt out of certain profiling or targeted advertising, appeal our response to a denial, and/or obtain a portability copy. Submit via contact@amiwrong.net noting your state; we’ll respond per applicable timelines and requirements.

Children

AIW is not directed to children under 13 (U.S. COPPA conception) nor children under minimum digital consent ages elsewhere. We don't knowingly solicit or collect personal information from minors under those thresholds. Parents/guardians: use device‑level parental controls; contact us promptly for removal suspicions via contact@amiwrong.net.

Account deletion & mobile credentials

You may delete or deactivate AIW profile data tied to amiwrong.net and revoke dashboard/mobile credentials via contact@amiwrong.net from your authenticated email (subject line Data / account deletion). This is separate from canceling storefront subscriptions—cancellation must occur in Apple or Google billing settings—see Terms of Use → Subscriptions.

Changes to this policy

We revise this Privacy Policy materially when practices change—post updates with revised “Last updated” date below. Continue using Services after effectiveness means acknowledgment of changes where permitted by applicable law—except where heightened consent regimes require explicit acceptance.

Contact

Privacy questions and rights requests: contact@amiwrong.net

Operational support: contact / support