ProfileGlance
Privacy Policy
Learn what ProfileGlance processes, why it is used, and the choices available to you.
Last updated:
Information we process
Depending on how you use the service, we may process an anonymous session identifier; account email address and optional country; profile usernames and public profile details you request; saved profile history; generated previews; plan access and purchase status; and basic request, device, and diagnostic information. Passwords are stored as salted scrypt hashes, not as plain text.
How we use it
We use this information to provide profile lookup and previews, maintain your account and session, remember recently checked profiles, apply paid access, protect the service, and understand aggregate product usage. Saved profile history is intended to expire after seven days; other records may be kept for as long as needed for the relevant feature, account, legal, or payment record.
Firebase and analytics
The web app uses the Firebase JavaScript SDK for Firebase App initialization and Firebase Analytics. It does not use Firebase Authentication or Firestore. Analytics records page views using normalized route names and events such as generic control interactions, searches, account submissions, and checkout starts. The app does not intentionally add entered usernames, search terms, email addresses, passwords, or comment text to those event parameters. Firebase and Google may process device, browser, app-instance, cookie, and network information as described in their own documentation and privacy terms. Advertising personalization signals are disabled in this integration.
Cookies, storage, and providers
The service sets an HTTP-only `ig_secret` session cookie and an HTTP-only `site-locale` preference cookie. Both are configured for up to one year, use SameSite=Lax, and are marked Secure on HTTPS. Firebase Analytics may use browser storage or identifiers to measure usage. App records are stored through the configured LibSQL database; the deployment may use a local database file or a configured remote database. A third-party payment provider processes checkout and payment details under its own terms. Profile information may be requested from third-party platforms, and generated content may involve the providers configured by the service.
Security, choices, and contact
We use measures such as signed session cookies, password hashing, access checks, and restricted server-side credentials, but no online service can promise absolute security. You can sign out, avoid creating an account, clear cookies in your browser, or stop using the service. For account, privacy, or deletion requests, email reshadeniz@gmail.com. Payment records may also be subject to the payment provider’s processes.
External services
Profile usernames or search queries may be sent to Instagram or Google when a lookup requires those sources. Requests for generated previews or story imagery may send related profile inputs to the configured Gemini-powered generator. These providers handle information under their own privacy terms.
Contact for privacy requests
For account, privacy, or deletion requests, email reshadeniz@gmail.com. Include only the information needed to identify your request; do not send your password or full payment-card details.