Privacy Policy
This beta privacy policy explains what Noteese collects, why it collects it, how proof files are handled, and how privacy settings affect Achievement Cards.
Beta legal version: phase2a-beta-2026-07-10
Proof files stay controlled
Public card viewers should see proof status, not the raw proof file or storage URL.
You control sharing
Settings let users manage default card privacy, profile visibility, and whether sharing tools are enabled.
Analytics are used to improve Noteese
Events help us understand signup, card creation, proof upload, sharing, reports, and beta reliability.
Minors require extra care
Guardians should review what minors submit and share.
Do not upload sensitive unrelated information. Achievement proof should support the achievement without exposing unnecessary private data.
1. Information Noteese collects
Noteese may collect account information, profile information, school or organization names, user segment, achievement details, proof metadata, uploaded proof files, card privacy choices, user settings, legal consent records, analytics events, referral/campaign data, and report/takedown records.
2. Proof files and proof metadata
Proof files are intended to be private by default. Admins may review proof to support the achievement review workflow. Public card viewers should see proof status, not the raw private proof file.
Proof metadata may include file name, file type, file size, proof type, upload status, and related achievement/card identifiers.
3. Public and protected cards
Private cards are limited to the user and authorized reviewers. Protected Public cards are shareable by link. Public cards may become discoverable when public discovery features launch.
If a user pauses sharing or changes card visibility, public card links may stop working or show a message that the card is not currently shareable.
4. Analytics, attribution, cookies, and local storage
Noteese tracks product and growth events such as page views, signup starts/completions, OAuth starts, password reset actions, achievement starts, proof uploads, submissions, Card Ready events, card views, shares, reports, legal consent completions, source/campaign data, and quality-assurance events.
Noteese may use cookies, browser storage, authentication/session storage, attribution/session IDs, and localStorage settings such as theme preference. Read the Cookie / Tracking Policy.
5. Reports and safety records
When someone reports a card, Noteese may store the report reason, optional note, related card information, page URL, report status, admin action history, and timestamps so the trust/safety workflow can be reviewed.
6. Legal consent records
Noteese records beta legal consent events, such as acceptance of terms/privacy/community/beta/minor notices and achievement submission attestations. These records may include user ID, email, consent type, policy version, source, user agent, metadata, and timestamp.
7. Minors and guardians
Minor accounts require extra care. Parents or guardians should review what is submitted, what is shared, and whether a public or protected-public card is appropriate.
8. Your choices
You can update profile visibility, default card privacy, guardian settings, user segment, card sharing controls, and profile photo settings from account settings when signed in.
9. Beta data handling
During beta, Noteese may use manual admin review, diagnostic logs, quality-assurance tools, and analytics validation tools to improve reliability and safety. Internal testing records are kept separate from intentional user-facing achievement content.
Early Beta
We’re testing Noteese with early users and organizations as we continue improving the experience. Please review our Terms, Privacy Policy, and Beta Safety Notice for information about using Noteese during the beta period.