@TheYard legal
Privacy Policy
A plain-language privacy baseline for TheYard beta. It explains what data the product collects, how it is used, and where third-party infrastructure may fit.
Last updated May 9, 2026
@TheYard legal
A plain-language privacy baseline for TheYard beta. It explains what data the product collects, how it is used, and where third-party infrastructure may fit.
Last updated May 9, 2026
TheYard may collect account information, email verification state, profile fields, handles, display names, school or program details, interests, avatars, posts, comments, discussions, messages, reports, blocks, follows, friend requests, and group activity.
TheYard may also collect technical data such as device type, browser, IP address, session cookies, security logs, error logs, usage events, and approximate performance information.
Data is used to operate TheYard, authenticate members, recover accounts, personalize feeds, display profiles, power discussions and messages, enforce blocks, review reports, prevent abuse, debug issues, and improve beta readiness.
Email addresses are used for authentication, verification, password reset, account notices, support, safety, and essential product communication.
Posts, comments, discussion replies, group content, profile details, and uploaded media may be visible to other members depending on where you share them and the product settings available at the time.
TheYard may store, resize, cache, transcode, and display uploaded media through storage and delivery providers so the product can load quickly and reliably.
Messages are not intended to be public, but they may be processed, stored, and reviewed when members report abuse, when safety tooling flags risk, when required by law, or when needed to protect the service.
TheYard may review message content when necessary for safety, support, legal compliance, platform integrity, or policy enforcement. Admin message review is controlled and logged where applicable.
Reports and blocks may include reporter identifiers, reported user identifiers, content identifiers, reasons, details, timestamps, and moderation status.
TheYard uses auth cookies and session storage so members stay signed in across browser restarts, tab switches, and return visits unless they manually log out.
Security cookies, session refreshes, and anti-abuse signals help keep accounts available and reduce logged-out UI flicker on app load.
TheYard may use Supabase for authentication, database, storage, row-level security, and email workflows; Vercel for hosting and deployment; and additional providers for email delivery, analytics, logging, media processing, or moderation.
Before launch, verify this policy reflects the exact processors, subprocessors, retention practices, and data locations used in production.
Members can update profile information, use blocking tools, report content, request password resets, and ask support for account help during beta.
For access, deletion, correction, or support requests, contact support@jointheyard.co. Response timelines and legal rights should be finalized with counsel before broad public launch.
TheYard keeps data as long as needed to operate the product, comply with legal obligations, resolve disputes, enforce policies, maintain safety records, and improve the beta.
No service can guarantee perfect security. TheYard uses provider security features, Supabase session controls, row-level security, and moderation tooling to reduce risk.
TheYard is not intended for children under 13. If a member is under the age of majority where they live, they should use TheYard only with any parent or guardian consent required by law.
Privacy/support: support@jointheyard.co. Legal: legal@jointheyard.co. DMCA: dmca@jointheyard.co. Confirm these inboxes are monitored before launch.