Privacy policy

Google sign-in

We store your verified email, display name and Google account identifier to identify your account. Google handles sign-in using openid, email and profile scopes.

We do not receive your Google password, request Gmail or Drive access, or retain Google access and refresh tokens.

Stored information

• Account data: Google identity, account status, role, creation and sign-in times, and recent authenticated activity times used for account statistics.
• Onboarding answers: how you found the service, your intended use and community size.
• Security data: session records, one-time login and verification challenges, and salted hashes of network/browser/device signals.
• API key data: key name, visible prefix, authentication hash, creation/use/revocation times, and an encrypted copy for owner-only recovery of newly created keys.
• Request data: submitted public Facebook URLs, requested metadata groups, request times, results, normalized fetched payloads and quota usage.
• Administration: access grants, scheduled limits, account status changes and audit records.

Request records include fetched captions and account information when providers return them, including some metadata you did not select for your public API response. Do not submit sensitive information in URLs, labels or survey answers.

Cookies and browser storage

Essential, Secure and HttpOnly cookies hold opaque login and device tokens. The login cookie expires after seven days unless you sign out or the session is revoked first. The device cookie can persist for up to one year; the temporary OAuth browser-binding cookie lasts up to ten minutes. Stored session tokens are hashed. Browser JavaScript cannot read these cookies.

Browser or network changes can trigger a Turnstile check. Salted signal hashes detect changes rather than permanently identify a device. Your theme choice is saved in this browser.

Cloudflare and Google may process technical information needed for their security and sign-in services. See Cloudflare’s privacy policy and Google’s privacy policy.

Use and access

We use this data for sign-in, downloads, quotas, security and troubleshooting. Administrators can inspect request records, adjust access and suspend or ban accounts.

Your account pages are private. Only you can reveal your API keys after verification. Administrators can inspect request records but cannot reveal your keys through the admin interface.

Third-party services

Cloudflare hosts the application, database and media proxy. Google handles sign-in. Cloudflare Turnstile checks for abuse. Your Facebook URL is sent to extraction providers; several may be tried if a lookup fails or details are missing.

Providers do not receive your Google credentials or API key. Media is streamed through this service. Anyone with an issued media link can use it until it expires.

Third-party services process requests under their own practices. Facebook Downloader is independent of Facebook, Meta and Google.

Notifications

Notices and security alerts appear in your private inbox. You can choose browser notifications for security alerts only, all notices or none. Permission is requested only when you choose to enable it.

We store your notification preferences, read status and browser push subscription endpoint and encryption keys. Push providers used by your browser deliver the messages; delivery depends on browser and device settings. Turning browser notifications off stops delivery but keeps the saved subscription. Choose “Remove browser” in Notifications to delete it. Signing out stops push delivery; enable it again after a new sign-in. Silent notices stay in the website inbox.

Repeated rejected requests using a known key can generate an unusual-volume alert. These alerts do not establish who used a key or guarantee detection of unauthorized use. Review the key’s history and revoke it if needed.

Retention and history

Account, survey, key, request and administrator audit records are retained without an automatic deletion schedule. Expired authentication challenges and expired or revoked session records are removed by scheduled cleanup. Temporary media records and cached metadata expire; keeping request metadata does not keep the media file available.

“Clear history” and individual removal controls remove entries from your visible history. They do not erase the service’s retained audit or quota records. Removing a revoked key entry likewise removes it from your list, not from previously logged request records.

You can sign out, revoke API keys and stop using the service. For account or privacy questions, contact the maintainer through wikram.in. Do not publish credentials or sensitive account details in public support messages. Any data request is assessed against applicable obligations and the records needed for security and service operations.

Policy changes

Changes will be published here with an updated date. See the terms of service for permitted use.