Privacy posture

Effective 2026-04-24 · Plain language first · Legal boilerplate at the bottom
Cognielo is architecturally incapable of reading your data. Not because we promise. Because we designed it that way.

What we collect from you

Nothing. We have no analytics endpoint that receives user behavior data. The privacy dashboard inside Cognielo shows a running byte counter of everything Cognielo has sent to Cognielo's servers. It will always read zero.

What your phone talks to, and when

The app is local-first. Four outbound connections happen only when you explicitly authorize them:

Four free public databases also run on-device queries (OpenFoodFacts, OpenFDA, NHTSA vPIC, Open Library) when you scan a barcode. The scanned value goes to the database; nothing about you does.

How the architecture enforces privacy

  1. The master key is generated on your device the first time you launch the app. It is never transmitted. If you wipe the app, it is gone forever.
  2. Every kit derives its keys from the master via HKDF-SHA256 with a domain-separated context string (RFC 5869). Savelo cannot read Healthelo's vault. Healthelo cannot read Legelo's. The keys are mathematically distinct.
  3. Every row stored is AES-256-GCM ciphertext at rest under the kit's derived key.
  4. Cross-app reads require a grant record. When Healthelo wants to correlate with Savelo, a grant record (signed by both) authorizes the read. You can revoke any grant in Settings.
  5. A hybrid post-quantum complement via CRYSTALS-Kyber (NIST FIPS 203) complements the classical suite so your data stays safe against future quantum attackers.

Subpoena posture

Cognielo receives no user data. If we receive a subpoena, we have nothing to hand over that contains your data — we have no copy of your master key, no copy of your derived keys, and no copy of your ciphertext. The most we could disclose is the fact that you installed the app (if we even know your email from a waitlist signup, which is optional). This is subpoena-resistance by construction, not by policy.

What happens if Cognielo shuts down

Nothing. Your data was always on your device. Profile → "Export Everything" dumps the entire corpus as plain-text JSON at any time, with no server involvement. If Cognielo disappears, your data stays where it always was.

HIPAA

Cognielo implements HIPAA-grade encryption and access controls. Formal HIPAA compliance certification is a post-launch milestone — the architecture is ready for the audit; the paperwork is in progress.

Children

Cognielo is rated 4+ on the App Store. We do not knowingly collect any data from children under 13. If you are a parent and discover that a child has entered data into Cognielo, note that the data lives on that device only — no server collection occurred.

Third-party trackers

Zero. No Google Analytics. No Facebook Pixel. No Mixpanel. No Segment. No Amplitude. No Sentry without on-device opt-in for crash reporting. No ad SDKs.

Your controls

Regulatory notices

Changes to this policy

If we change this policy, the updated version lives at cognielo.com/privacy. Because we collect nothing, most changes are cosmetic.

Contact

Privacy-specific questions: privacy@cognielo.com. General: hello@cognielo.com.

Patent Pending — U.S. App. No. 64/041,821 · Elo AI · Greeley, Colorado