← Back home

Privacy

How the current Student Steals application handles account information, browser storage, activity, and maps.

Accounts and profiles

Supabase handles account registration, password sign-in, and session restoration. Registration sends your email and password to Supabase Auth. Profile information includes your username, name, school, and any phone number or profile image you supply. Signed-in profile edits are stored in the project’s Supabase database. Photos uploaded through profile editing are stored in a private Supabase Storage bucket; the profile row stores their reference. The app requests a temporary photo link for the signed-in owner. Replacing or removing a photo updates the profile first, then attempts to delete the previous uploaded file. If deletion fails, the app reports it; the old file may remain in private storage.

The Supabase client keeps session information in your browser so it can restore your sign-in. Sign out when using a shared device.

Saved items and browser storage

When you sign in, Supabase stores eligible saved discounts and events with your account so they can appear on your devices. Guest saves stay in this browser until they can be added to your account. Card-use counts, your map campus selection, and up to eight recent map searches stay in this browser.

You can remove saved items using their save controls and clear recent map searches in the map interface. Clearing this site’s browser storage removes browser-local selections, activity identifiers, and sign-in storage; it does not delete your Supabase account, profile, or records already sent to the database.

Activity and project measurements

The application records account creation and signed-in visits and actions, including saving an item and marking a card offer used. Records can include browser and visit identifiers, action type, time, related item, and your account identifier.

Supabase stores these records, and the team’s restricted OKR dashboard shows aggregate measurements. A card-use action records what you mark in the app.

Maps and location

Using “Find my location” asks your browser for location permission. The map uses the returned coordinates to show your position. The current map code does not save those coordinates as a profile field or map-search-history entry. Map and tile providers still receive network requests needed to display the map, including the area being viewed.

Map backgrounds use MapTiler when configured, or OpenFreeMap, with OpenStreetMap data attribution. Choosing directions opens Google Maps or Apple Maps with the selected destination; those services handle their own directions and location settings. You can deny or revoke location access in your browser.

Reports and external services

Listing reports send the listing identifier and label, issue category, optional details, and current page URL to Supabase. Avoid including private information in report text. Website bugs posted to the project’s GitHub issue tracker are public.

The website is deployed through Vercel. Fonts are requested from Google Fonts, and some business icons may be requested from Google or DuckDuckGo. Offer-source links and directions take you to external services. Providers receive network information when your browser contacts them and apply their own policies. In editor previews, available Lovable error-reporting hooks may receive error details and the page path.

Your choices

You can browse listings without creating an account, decline location permission, sign out, remove local saved items, and clear site storage through your browser. These actions have different effects on local and account data as described above. See Contact to email the student team about account or privacy questions, report a listing, or submit a public website bug report. Do not put account information in a public issue. Clearing site storage does not make a deletion request for records held by the project or its providers.