Privacy policy

DRAFT • Guuber Indianapolis pilot Information we collect Account name and email; service addresses and instructions; booking and support records; pickup and disposal images; contractor business, vehicle, document, and approval records; electronic acceptance history; and technical security logs. The payment processor handles payment-card and payout-bank details. Do not upload Social Security numbers, bank credentials, or unnecessary identity data to support or evidence fields. Why we use it To authenticate accounts, quote and arrange service, screen providers, record completion, process payment events, address claims, maintain safety, and meet applicable obligations. Pickup addresses are disclosed to an assigned collector; open job listings show a general service area. Access to operational and financial information is restricted by staff role. Service providers and sharing The planned infrastructure uses Vercel for application hosting and Supabase for account authentication, database, and private file storage. Stripe handles payments when configured. Navigation links may take you to an external mapping provider under that provider's policy. No advertising trackers are included in this first release. We do not build a sale-of-data or targeted-advertising program into this release. A final vendor list and contractual terms must be reviewed before launch. Retention and security We use restricted access, encrypted provider connections, private file storage, and limited-life file links. No system is perfectly secure. Before live launch, Guuber must adopt and publish retention periods for operational images, compliance documents, transaction records, consent evidence, backups, and security logs, including legal holds and deletion procedures. Demo environments are for fictional data only. Your choices and requests Use in-app support to request access, correction, deletion, or a downloadable copy of your information. We may need to verify identity and retain records required by law or to resolve an active dispute. Mandatory rights depend on your location and applicable law. The legal entity, direct privacy contact, response process, and applicability of Indiana privacy legislation must be finalized before launch. Cookies and children Essential session cookies keep you signed in. The app uses a service worker only for public offline fallback assets; private booking and identity information is not intentionally cached for offline use. The service is intended for adults 18 and older. We do not intentionally provide accounts to children. Changes Published versions are retained. Material changes will be communicated through the app and, where required, renewed consent will be requested.