UpToGlide is a read-only marketplace aggregator. This page explains the data needed to browse, save listings and searches, receive alerts, send feedback, request listing review, and control optional analytics.
Public launch draft. Legal review owns the final legitimate-interest balancing test, retention windows, and takedown SLA before launch.
Optional analytics
Change or remove your optional analytics choice at any time.
No optional analytics choice stored.
Read-only marketplace role
UpToGlide aggregates public marketplace listings into a read-only catalog. We do not broker sales or edit source marketplace records. We show source attribution and, where available, send users back to the original source through the app's deep-link flow.
Public listing and source data
Listing titles, public specifications, prices, images, source names, source attribution, and public listing identifiers come from source marketplaces. Listing text remains in the source language. Report or request removal when a public listing should be reviewed.
Account and profile data
If you sign in, UpToGlide uses Supabase Auth for email magic links and supported providers. Profile data can include display name, avatar URL, home region, preferred language, and theme preference. Email is read from the auth provider for account access and is not stored in the profile table.
Favorites, saved searches, notifications, and push
Signed-in features store the listings you favorite, saved-search definitions, match notifications, unread state, push preferences, and browser push-subscription state after you opt in. Push payloads contain only safe app-owned identifiers and localized alert copy.
Location choices
Precise browser geolocation is requested only when you use the current-location results filter. Approximate location can be inferred from request headers for distance or locale fallback, but IP-derived coordinates are not written into results URL state.
Necessary cookies and storage
Necessary first-party storage keeps the app working: NEXT_LOCALE for locale, theme for display preference, Supabase auth/session cookies, auth_intent_nonce for safe sign-in replay, push-subscription state after opt-in, and uptoglide_consent to remember this privacy choice. Declining analytics does not block these necessary functions.
Optional analytics consent
Optional analytics remains off unless you accept it. The consent record stores only the current privacy version and whether optional analytics is accepted or rejected. After acceptance, PostHog EU may receive event categories for searches, listing views, contact reveals, favorites, saved searches, and completed sign-ins, using anonymous browser identifiers and a stable pseudonymous signed-in identifier. Analytics properties exclude gated source/contact fields, seller fields, raw scraped rows, hrefs, auth/session data, email, profile data, push secrets or payload bodies, raw search text, and precise coordinates.
Report and request removal flow
Suggest improvement saves your topic, message, optional subject, optional contact email, and app page path so the team can review feedback. Listing detail pages include report / request removal; that path still opens a support email draft with safe listing context. UpToGlide does not promise automatic erasure from source marketplaces.
Legal launch prerequisites
The legitimate-interest balancing test, final retention windows, and public takedown SLA are Legal-owned prerequisites for public launch. This draft flags those gates without hard-coding an unapproved SLA.