What we collect, where it lives, how to remove it.

1. Who we are

LE TEEN (le-teen.com) is operated by Quasilife, a Canadian sole proprietorship registered to TJ Jankowski. This is a Phase 0 notice — concise on purpose. As the operation incorporates and the data surface expands, we'll update this page and date the change.

2. Audience

LE TEEN is intended for readers aged 13 and older. We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided information to us, contact us via the channel published in §10 below and we will delete it.

3. What we collect

Three categories, in plain terms:

• Email and audience type — only if you sign up at dispatches. The form asks whether you're a teen or a parent / guardian; that selection is stored alongside your email for content tailoring later.
• Calculator inputs — when you use worth-it, the values you enter are sent to our server for analytics (anonymous unless you purchase the premium report, in which case Stripe collects the information needed to bill you). The calculation itself runs in your browser; the server only sees the result event and the inputs that produced it.
• Site analytics — server-side request logs and event signals routed via RudderStack into a Postgres database we operate. We do not run third-party analytics or session-replay tools, and we do not place advertising tracking pixels on this site.

4. Where it lives

• Subscriber emails — stored in Resend (our email delivery vendor). We do not duplicate subscriber emails into our analytics database; events about subscription state (subscribed, confirmed, unsubscribed) are stored without the email itself.
• Calculator events and site analytics — stored in a Postgres database on a virtual private server we control. We will document the data center's jurisdiction and our backup policy on this page once both are finalised; until then, treat the storage as "managed by Quasilife on a single VPS, not yet redundantly backed up."
• Stripe payment information (if you buy the premium report) — handled directly by Stripe; we never see card numbers. Stripe sends us a webhook with the transaction outcome and a receipt reference.

5. How to unsubscribe

Every email we send includes an unsubscribe link in the footer. Clicking it removes you from our Resend audience immediately. If the link doesn't work, the contact channel in §10 is the manual fallback.

6. How to request deletion

Use the contact channel published in §10 with the subject "delete my data". Include the email address you used to interact with us (if applicable). We will delete subscriber records from Resend and the corresponding event entries from our database within 30 days, and reply to confirm.

Note that some records may persist in operational backups for a period after deletion (we cannot selectively delete from a backup); we will not restore from a backup in a way that re-creates a deleted record. The backup policy will be specified here once it's formalised.

7. Cookies and tracking

We do not set advertising cookies. The site uses a small number of essential first-party cookies (e.g. session for secure form submission). We do not load third-party tracking scripts.

8. AI crawlers and machine readers

LE TEEN explicitly allows reputable AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Applebot-Extended) to read our public pages, including this notice. See /robots.txt for the specific list. If you operate a crawler not on that list and would like to request access, use the contact channel in §10.

9. Changes to this notice

We will update the date at the top of this page when we change it. Material changes (new categories of data collected, new vendors with access, change of operator) will be flagged in the next dispatch we send.

10. Contact

Brand-side email infrastructure (e.g. privacy@le-teen.com) is not yet live. Until it ships, this notice describes our intended posture but the operational contact mechanism for privacy requests is not fully wired. Phase 0 of LE TEEN has limited contact-handling capacity; if you need a guaranteed-deletion or rapid-response channel, we recommend waiting until this section lists a stable email address before submitting personal data.

The current dispatch / subscribe form at /dispatches is the de facto best-effort contact surface during Phase 0 — submit a signup with a clear audience tag and we will see it; this is not a binding privacy-request channel and does not start the 30-day deletion clock.