1. Overview
67 Path is a digital wellness application designed for students, schools, and families. Privacy is not a feature we added — it is the foundation the product was built on.
The short version: we collect no personally identifiable information from anyone. The app uses a small amount of anonymous, aggregated analytics to function and improve — never linked to your identity, never used for advertising or tracking.
This policy explains what that means in practice, how the app works technically, and what rights you have.
2. Data We Collect
67 Path does not collect personally identifiable information (PII).
Specifically, we do not:
- collect names, email addresses, phone numbers, or any personal identifiers
- track which specific social media apps a student opens or how long they use them
- access, view, or store social media content
- link any usage data to any individual user
- require an account to use the app
The limited data we do process is anonymous and never tied to your identity:
Anonymous in-app analytics. 67 Path uses Firebase Analytics to collect anonymous usage data — such as app launches, screen views, and feature interactions — to understand how the app is used and improve it. This data contains no personal identifiers and is not linked to you. Google Signals and Ad Personalization are disabled, and we never use this data for advertising or tracking.
Diagnostics. We collect anonymous crash and performance data to keep the app stable and fix problems. This data is not linked to your identity.
Subscription data. 67 Path uses RevenueCat to manage subscriptions. RevenueCat processes anonymous purchase data — such as subscription status — solely to deliver the features you've subscribed to. Payment itself is handled entirely by Apple. We never see or store your payment information.
3. Children's Privacy
COPPA (Children's Online Privacy Protection Act) requires operators to obtain verifiable parental consent before collecting personal information from children under 13.
67 Path does not collect personal information from anyone — children or adults. The anonymous analytics described above contain no personal identifiers and cannot be used to identify a child. There are no profiles to build and no personal information to protect under COPPA's framework.
4. FERPA
FERPA (Family Educational Rights and Privacy Act) protects student educational records held by schools and their designated partners.
67 Path does not receive, access, store, or process individual student educational records. No student data — not grades, not attendance, not behavioral records — flows to us at any point. Because 67 Path maintains no individual student data, FERPA's data protection requirements have nothing to apply to on our end.
5. iOS Screen Time API
67 Path uses Apple's Screen Time API (Family Controls framework) to create intentional entry prompts before social media apps open.
This API operates entirely at the iOS operating system level. It does not give 67 Path access to:
- app content or communications
- browsing history
- messages or notifications
- any data stored in other apps
The Screen Time API creates the pause mechanic. It does not create a data pipeline to 67 Path.
6. Analytics
We use two separate, anonymous analytics tools:
In the app. Firebase Analytics collects anonymous usage data as described in Section 2 — app launches, screen views, and feature interactions, with no personal identifiers and no advertising use.
On our website. 67path.com uses Google Analytics 4 to understand how visitors interact with our pages — which sections they read, how they navigate, where they come from. This data is anonymized and aggregated.
Neither tool links data to any individual student, and the two are never combined. You can opt out of Google Analytics tracking using the Google Analytics Opt-out Browser Add-on.
7. Data Retention
Because we collect no personal data, there is nothing to retain, delete, or export on an individual basis.
Anonymous analytics are retained only as long as needed to operate and improve the service.
8. Changes to This Policy
If we ever change our data practices in a meaningful way, we will update this page. The "last updated" date at the top of this page reflects the most recent revision.
9. Contact
For privacy questions, data requests, or concerns, contact us at: