Privacy Policy

Operator and requests

ServeUp is operated to provide volunteer-opportunity matching and service record management. For privacy, support, or safeguarding inquiries, please reach out through the official platform support channels.

Information you provide

Account information includes email, password handled by Supabase Auth, optional display name, signup interest, 13+ self-declaration and verification/authenticator status. Supabase manages session and authenticator secrets; ServeUp does not store plaintext passwords or recovery codes in its application tables. We store Terms version, fingerprint, time and source of acceptance, without adding IP address or user agent to that receipt.

Registrations, service dates, task descriptions, minutes, organizer decisions, correction history, goals and optional private streak summaries support your records. Organizer applications contain authority references, decisions, and private uploaded PDF/PNG/JPEG evidence. Upload only necessary evidence; do not upload government IDs, health information, payment details or school rosters.

Who can read records

Public visitors can read minimized eligible published opportunity information. Signed-in users can read full listing details and any deliberately shared public venue address. Your private goals, streaks, email, applications and service ledger are not a public student directory. You can choose separate registration-name sharing. Authorized organization staff see scoped registrations and service facts. Independent reviewers can access safety-cleared evidence through audited authorization. Trusted operators and infrastructure providers can have administrative access needed to run the service.

Messaging, institutional programs and external sourcing/community events remain unavailable for launch. Their storage structures exist but do not authorize collection or use. They require new Terms, operational prerequisites and review before activation.

Location, AI and external links

Device location is requested only when you choose it and is transient, rounded for nearby search and excluded from AI context and saved account records. Exact ZIP matching needs no lookup; nearby ZIP lookup sends the chosen ZIP to Zippopotam.us. Optional public venue matching starts disabled and, when explicitly enabled and chosen by an organizer, sends a public street/city/ZIP to the US Census service. Map links send the selected public address or approximate city/ZIP to Google Maps when opened. Do not submit private homes.

AI interpretation starts disabled. If enabled, bounded user requests, prior filters and task taxonomy go to OpenAI gpt-4o-mini; listing text, precise location, credentials, account records and assistant replies are excluded. Keep personal data out of your requests. Chat stays in component memory for the current session, not a saved ServeUp transcript. Usage and budget counters persist. Providers can retain request data under their own policies; no zero-retention agreement is claimed. Development-only local Ollama cannot run in production.

Providers and information leaving ServeUp

Supabase processes authentication, application database records and private file storage. Hosting infrastructure serves the app and may process request IP addresses and operational logs. Standard SMTP providers handle verification and recovery email. No advertising, analytics or third-party tracking package is included. Optional AI and location services are described above; external destinations apply their own policies.

Cookies, device storage and offline use

Essential Supabase session and PKCE verification cookies support sign-in and mailbox/recovery flows. They use SameSite=Lax and Secure on HTTPS; browser-readable authentication cookies are required by this implementation and are not claimed to be HttpOnly. serveup-theme is the only explicit localStorage preference used by application source. No transcript, password, private location, registration or evidence is written to localStorage or sessionStorage.

The production service worker caches exactly nine public fonts, icons and a generic offline page. It does not cache account HTML, API or RSC responses, private files or AI replies. Offline work cannot be submitted. Browser, network and host caches must also be configured and checked by the operator.

Retention, exports and deletion

Open Privacy and deletion in your account to manage sharing, export approved service history and request deletion. The private CSV and printable report contain approved service facts; they are not a complete export of every application or security record. Contact support for other access requests. Withdrawal from a registration does not erase review history.

Deletion revokes access, removes private stored files before deleting the Auth account, cascades owned records and nulls personal actor references in justified shared proof. Partial failure remains pending. Evidence legal holds, institutional holds or justified safeguarding holds can delay deletion and cleanup. Shared organization verification and other people’s legitimate service records can remain with departing actor identifiers removed.

Finalized evidence normally becomes eligible for byte cleanup after 30 days unless held; pending records remain until finalization or expiry. Narrative cleanup runs through scheduled maintenance and has feature-specific bounds. Original ledger facts and limited shared proof do not have a universal automatic expiry. Systems, audit logs, and backups retain data according to standard operational and safety policies. Provider backups may retain prior data until their documented expiry; instant deletion of every backup is not promised.

Minors and security

Accounts are for ages 13+. The age statement is a self-declaration, not identity verification or guardian consent. If it is learned that an account belongs to someone under 13, contact platform support so access and records can be handled appropriately. Applicable guardian, school and organization requirements remain separate. Do not enter other students’ records.

Access checks, row-level database policies, staff MFA, private storage, upload quarantine, bounded requests and audited evidence access reduce risk. They do not guarantee that every incident, malware file or false record will be detected. Do not use ServeUp as an emergency service; contact local emergency services and a responsible adult for immediate danger.

Notice changes

This notice is versioned for transparency. A Terms receipt does not imply consent to all processing or a separately recorded Privacy acceptance. Material changes and any new optional-feature activation require review of notice, Terms and any separate consent needed. Contact support with privacy questions before submitting information.