THS Privacy Notice

1. Draft status and scope

This is an operational draft and is not yet effective. It covers the THS website, private Society, guardian tools, verification, communications, and THS-operated events. The legal operator, privacy contact, mailing address, vendor list, and jurisdiction-specific disclosures must be inserted before activation.

The notice is written for guardians and students. Guardians receive controls and safety visibility, while students should also understand what THS collects and who can see it.

2. Information THS may collect

• Guardian and household data, such as name, confirmed email, account credentials, contact preferences, household relationship, and billing or subscription status.
• Student identity data, such as display name, date of birth, age lane, grade, graduation year, homeschool status, guardian links, eligibility state, and account status.
• Verification data, such as attestations, evidence references, reviewer decisions, revision history, and expiration dates. Sensitive evidence should remain in restricted systems and not appear in ordinary profiles.
• Society data, such as selected interests, learning goals, Circle membership, posts, comments, attendance, hosting commitments, reports, blocks, restrictions, and progress records.
• Event data, such as applications, tickets, eligibility, emergency and pickup information, accessibility requests, attendance, incidents, and event-specific permissions when those features are offered.
• Communications data, such as delivery address, purpose, region preferences, consent version, suppression state, delivery status, and support correspondence.
• Technical and security data, such as IP address, browser or device details, authentication events, cookies needed for sessions, rate-limit signals, audit events, and error logs.

3. Why THS may use information

• Create and secure guardian-linked accounts, calculate age lanes, and verify eligibility.
• Provide age-appropriate rooms, explain interest-based recommendations, and operate requested programs or events.
• Manage consent, billing status, communications, accessibility, check-in, support, and account requests.
• Prevent fraud, enforce rules, respond to reports, preserve necessary evidence, and protect members, staff, and the service.
• Measure reliability and improve THS using the minimum information reasonably needed, without optimizing a youth feed for outrage, virality, or time spent.
• Comply with law, respond to valid legal process, and establish or defend legal claims.

4. Youth privacy boundaries

The private youth community begins at age 13 in this release. A person known to be under 13 is not eligible for a youth social seat. If THS learns that it collected an under-13 child's personal information outside an approved guardian or event process, THS will restrict the youth seat and follow its approved deletion and parent-notice procedure.

Student profiles and posts are not public or intended for search-engine indexing. THS does not expose an exact home address, school address, routine location, private verification evidence, or guardian contact details to ordinary members. Uploaded location metadata is not an approved feature in this release.

5. Guardian visibility

An authorized guardian may view and manage the identity, consent, payment, event, and safety information permitted by that guardian's exact relationship and capability record. Household membership alone does not create authority over every student.

Ordinary guardian access is not a transcript of every student conversation. When a safety matter requires content review or disclosure, THS should expose only the information reasonably needed through a logged, role-bound process.

6. Matching and sensitive information

THS may recommend a Circle, supervised event, or structured introduction using information a student or guardian intentionally provides, such as topic, experience level, preferred group size, broad region, schedule, and a declared learning edge.

THS does not infer religion, health, disability, race, politics, sexual information, or other sensitive traits for matching. It does not offer youth dating matching, public follower counts, or public popularity rankings.

7. When information may be shared

THS does not sell personal data, use student data for behavioral advertising, or permit third parties to build advertising profiles from student activity. A materially different practice requires a new notice, a new policy version, and any separate consent required by law.

• With contracted service providers that need limited information to provide hosting, authentication, email, payments, security, support, verification, or event operations, under approved data-protection terms.
• With vetted event or Chapter personnel only to the extent needed for an approved duty. Local operators do not receive a raw family contact list merely because they operate locally.
• With guardians and authorized staff according to exact permissions, safety duties, and audit controls.
• With emergency responders, law enforcement, courts, regulators, or other parties when reasonably necessary for immediate safety or when required or permitted by law.
• As part of a proposed organizational transaction only after child-data safeguards, notice duties, and legal constraints are reviewed.

8. Communications and event location

General marketing and local event marketing are separate guardian choices. Withdrawing either choice does not stop necessary account, security, billing, safety, policy, or registered-event messages.

Public event discovery uses broad geography. An exact private venue should be disclosed only to an eligible, approved registrant at the approved time and should not be included in public analytics or list exports.

9. Retention and deletion

THS should keep each category only as long as reasonably necessary for its stated purpose, then delete, de-identify, or securely isolate it. Child information may not be retained indefinitely. A written schedule must define periods for identity, verification evidence, content, reports, consent, financial, event, security, backup, and legal-hold records before activation.

Deletion may be delayed or limited for safety evidence, fraud prevention, completed transactions, legal claims, valid legal process, or another documented lawful duty. A request should not silently erase records needed to protect another member.

10. Choices and rights

After identity is reasonably verified, a guardian or other eligible person may request access, correction, deletion, portability, or information about applicable processing, and may appeal a denied privacy request where applicable law provides that right. THS must publish the request channel, response process, identity-verification standard, and jurisdiction-specific rights before activation.

A guardian may change optional communication choices without losing membership solely because of that choice. Required permissions may be withdrawn by ending or pausing the affected student service, subject to lawful retention.

11. Security, incidents, and international use

THS uses administrative, technical, and physical safeguards appropriate to the sensitivity of youth information, but no system can promise absolute security. The implemented program must include least privilege, access logging, vendor review, secure deletion, incident response, and required notifications before activation.

This draft assumes an initial United States launch. THS must complete a separate legal and operational review before intentionally offering youth services in another country or transferring information under another country's rules.

12. Changes and contact

Material changes use a new version and are presented to the appropriate guardian or student. THS will request fresh permission when required and will not treat silence as consent where affirmative consent is required.

A monitored privacy email, request form or equivalent channel, legal operator name, and physical mailing address must appear here before this notice is activated.