Privacy Policy

Bulk Photo Delete & Download for Facebook · Last updated: July 27, 2026

Summary: Facebook photo content is processed locally in Chrome and is not sent to a server operated by Athinin. The Extension communicates with Meta to perform the actions you request and with ExtensionPay to provide and verify paid access.

Athinin ("we," "us," or "our") provides the Bulk Photo Delete & Download for Facebook Chrome extension ("the Extension"). This policy describes the data the Extension accesses, why it is needed, where it is stored, and the limited circumstances in which it is transmitted.

1. Scope and single purpose

The Extension's single purpose is to help you find, back up, download, untag, and delete photos belonging to Facebook profiles or Pages you are authorized to manage. It operates on Facebook photo pages that you open and only performs download or destructive actions after you request them.

2. Data processed locally

The Extension uses chrome.storage.local to retain the following data in your Chrome profile:

Data	Purpose
Photo identifiers, image URLs, captions, timestamps, source type, profile/Page scope, and processing status	Build the local photo index, create downloads, avoid duplicates, and apply safety rules.
Deletion/untag history and active job state	Show a local activity record and safely resume or stop work.
Settings, folder choices, timing, and safety limits	Remember your preferences.
Download and ZIP job identifiers and temporary progress	Track completion and report failures without duplicating files.
Free-use counter, the minimum identifiers of photos included in the Free allowance, and cached Premium status	Apply the allowance without counting the same photo more than once and unlock paid features.
Page ID and Graph API access token, only if you enter them in optional Page Mode	Authenticate direct requests to Meta's Graph API for a Page you manage.

The Free plan includes up to 10 unique photos. A photo is included in that allowance only the first time it is successfully downloaded, included in a completed ZIP, deleted, or untagged. Performing another supported action on that same photo does not count it again. The minimum photo identifiers needed to recognize those photos remain in chrome.storage.local and are not sent to Athinin, ExtensionPay, or Stripe.

This locally stored Facebook content is not uploaded to Athinin or to the payment provider. The Extension does not collect your Facebook password, session cookie, fb_dtsg token, private messages, contacts, or friends list.

3. Facebook website content and activity

On supported Facebook photo pages, the Extension reads the visible page and, only during a scan you explicitly start, reads relevant photo metadata from Facebook's own GraphQL responses in that tab. Outside that capture window, GraphQL responses are not cloned, read, or parsed by the Extension.

This processing is necessary to identify full-resolution images and determine which photos belong to the current profile or Page. We do not use this information for advertising, analytics, profiling, credit decisions, or any purpose unrelated to the Extension's photo-management features.

4. Direct communication with Meta

Your browser communicates directly with facebook.com and fbcdn.net to display and download photos and to perform actions you request. If you enable Page Mode, it also communicates directly with graph.facebook.com using the Page token you provide. Athinin does not proxy or receive this traffic. Meta processes it under Meta's Privacy Policy.

5. Downloads

Photos and ZIP files are saved through Chrome's downloads system. They remain on your device and are not uploaded to Athinin. Clearing Extension data or uninstalling the Extension does not delete files already saved in your Downloads folder.

6. Premium payments

Premium checkout and entitlement verification are provided by ExtensionPay, which uses Stripe for payment processing. When you open checkout or restore Premium, ExtensionPay receives the information needed to identify the Extension and the purchase. During checkout, ExtensionPay and Stripe may collect your email, billing details, payment method information, IP address, and transaction data under their own privacy policies.

Athinin and the Extension do not receive or store your full card number.
The ExtensionPay library stores a pseudonymous provider API key, installation timestamp, and cached entitlement data in chrome.storage.sync when available, with chrome.storage.local as fallback. If Chrome Sync is enabled, Chrome may synchronize this limited payment state between browsers signed in to your Google account.
No Facebook photos, captions, photo URLs, deletion history, or Page tokens are sent to ExtensionPay or Stripe.

See ExtensionPay's privacy information, Stripe's Privacy Policy, and our Terms of Sale.

7. Data sharing and sale

We do not sell personal data. We do not share Facebook content with advertisers, data brokers, analytics providers, or unrelated third parties. Data is disclosed only as described above to Meta for requested Facebook operations, to ExtensionPay/Stripe for payments, or when required by law.

8. Chrome permissions and host access

Permission/access	Reason
`storage` and `unlimitedStorage`	Store the local index, preferences, history, job state, and payment status. Large accounts may exceed Chrome's standard storage quota.
`downloads`	Save individual photos and ZIP backups and monitor their completion.
`offscreen`	Create large ZIP blobs in an invisible extension document, because a Manifest V3 service worker cannot create them directly.
`https://.facebook.com/`	Run on Facebook photo pages and, in optional Page Mode, communicate with Meta's Graph API.
`https://.fbcdn.net/`	Fetch the photo files selected for download or ZIP backup.
`https://extensionpay.com/*` (optional)	Requested only when you choose to buy, verify, or restore Premium. It opens the checkout and verifies the purchase entitlement; it is not required to install or use the Free features.

9. Retention and deletion

The panel's profile-clear action removes the local index for the selected profile only.
Settings → Clear local data removes operational Extension data from chrome.storage.local, including settings, photo indexes, history, active jobs, free-use state, and Page credentials. It preserves only purchase-entitlement data needed to avoid losing or repeatedly reactivating a valid purchase. It does not erase ExtensionPay data in chrome.storage.sync.
Uninstalling removes the Extension's local operational storage. Synced payment metadata or provider transaction records may remain available for purchase restoration or required retention.
Files already downloaded remain on disk until you delete them yourself.
To request deletion of payment records held by ExtensionPay or Stripe, contact contact@athinin.com or the applicable payment provider. Transaction records may be retained where required for tax, fraud prevention, or legal compliance.

10. Security

Local data is protected by the security of your Chrome and operating-system profile. Page access tokens are sensitive; use a token with the minimum necessary permissions and clear it when no longer needed. No method of storage or transmission is completely secure.

11. Children

The Extension is not directed to children under 13, and we do not knowingly collect personal data from children.

12. Changes

We may update this policy when the Extension's behavior or legal requirements change. The "Last updated" date will identify the current version. Material changes will be disclosed through the Extension or its store listing where required.

13. Contact

For privacy questions or requests, contact Athinin at contact@athinin.com.