Privacy Policy
November 18, 2026Files stay local
Scanning, repair, and verification happen inside your browser.
Analytics stay limited
Openable receives aggregate usage and recovery outcomes.
You control your account
Account and payment records support your balance and purchases.
Scope
This policy covers the Openable website, browser-based file recovery tools, accounts, purchases, support requests, and authorized social platform connections. Openable is operated by Bee Software LLC in New Mexico.
File processing
Openable processes selected files inside your browser. File contents, filenames, folder paths, checksums, and previews stay on your device unless you explicitly choose to share a file with support.
Scanning and recovery stay local. If you explicitly choose to share a file for a support request, that file leaves your device and is stored privately by Openable for investigating that case. Sharing is optional and does not guarantee recovery. One file up to 5 GB can be shared per request. Access is restricted to authorized support staff; shared files are not served publicly, sent to analytics, published as examples, used for AI training, or added to test fixtures without separate permission. Shared files are kept for 30 days and then scheduled for deletion; you can delete your shared file sooner from Your account. Scheduled cleanup also removes incomplete uploads. A support request and its message remain separate account records when a shared file is deleted.
Choose one or more affected originals. Multiple files are sent together as one ZIP, up to 2 GB total. Archive entries use anonymous example numbers.
If you save a scan to the local library, your browser stores its manifest. It may also store selected originals and recovered copies in IndexedDB.
Large source selections are not duplicated into browser storage. You control this library and can delete saved scans at any time.
Information Openable receives
Service and security data
Web requests may include an IP address, browser information, the requested page, referral information, and time of access.
The server uses a locally installed DB-IP country database to derive a country code as a language fallback, after your saved preference and browser language. Your IP address is not sent to DB-IP for this lookup. This is separate from scan allowance and diagnostic counting, which do not use IP addresses. Hosting and analytics providers can receive your IP address as part of network requests; Openable does not claim that visiting the website hides your IP address.
Product analytics
Openable uses PostHog EU Cloud for limited analytics.
It may include a pseudonymous browser identifier, page paths, referral origins, performance measurements, sanitized errors, and clicks on marked links or buttons.
Session recording is disabled. Browser Do Not Track settings are respected.
Google Analytics 4 measures page views, sessions, referral sources and approximate location. In the United States, measurement is on by default. Elsewhere, including when the country is unknown, Google Analytics waits for you to select Allow. Openable estimates your country using the local country database described above. You can turn Google Analytics off at any time under Google Analytics settings in the footer. Do Not Track and Global Privacy Control also turn it off.
Google receives network information, including your IP address, and may store analytics cookies. We send known public page paths and referral origins. File names, file contents, recovery details and account identities stay outside Google Analytics.
How Google uses information from sites that use its services
Openable also sends content-free copies of product-event types and fixed format/result categories to PostHog. Detailed inspection snapshots, raw errors, file identifiers, exact file sizes, support text, account identifiers and emails stay out of these copies. Private server records remain authoritative for accounts and payments; copied events do not prove a payment or a saved download.
Recovery statistics
Analytics may include scan mode, file counts, format categories, size and duration buckets, result categories, recovery outcomes, and download counts.
File contents and identifying file details stay outside analytics.
To count distinct attempted and recovered files, Openable keeps a private random key in this browser and uses it to transform a complete file fingerprint into an opaque identifier. Only the opaque identifier, format, fixed problem category and recovery outcome, when available, are sent to Openable’s first-party reporting store. The raw fingerprint and private key stay on your device. This distinguishes retries in the same browser without uploading filenames or file contents. Clearing browser storage or switching browsers resets this distinction. A separate browser identifier supports internal-test exclusions. Do Not Track suppresses this reporting.
Optional first-party product measurements retain fixed, common extension categories for unsupported selections, grouping unlisted extensions as other rather than sending arbitrary suffixes. They assign random references to scan batches and individual file selections to link scan results, recovery requests and downloads without sending file names or contents. Unsent fixed-category records may be queued in this browser for up to 24 hours for retry, with a bounded storage limit. Optional first-party product measurements use a private browser identifier to link recorded visits, scans, recovery starts and results, recovered-photo preview views, download actions, allowance interruptions, and checkout activity. They include an approximate country code derived by the server from its local country database when reports arrive, without storing an IP address in these records, and fixed page, referral, browser, operating system and device categories, page-performance measurements, counts of unhandled errors without their messages, and a release reference. When you are signed in, the server may link those records to your account, show confirmed purchase history alongside a batch, and match an opaque order reference to a confirmed purchase. These measurements do not upload files, filenames, raw fingerprints, full URLs, or error messages. Do Not Track and registered internal-test exclusions suppress this optional reporting.
Optional first-party analytics also record each selected file’s exact size in bytes to investigate reliability and storage failures. File contents and filenames are not included.
Recovery edge-case reports
When recovery unexpectedly fails for a supported format, Openable may send fixed technical categories to its own server.
These are the format, container type, recovery stage, diagnostic code, coarse size bucket, scan result, detection method and confidence, and decoder state.
The server derives a case ID from those categories and increments an aggregate count.
It does not receive or store the file, filename, path, checksum, file fingerprint, preview, file contents, or raw error text.
File type suggestions
If you choose to suggest a future file type, Openable stores your selected type or typed extension, language, the form entry point, a random submission reference to prevent duplicate retries, and the time of submission. No file is uploaded. Do not enter a filename or personal information. Suggestions are separate from automatic analytics and recovery outcomes; Do Not Track does not prevent an explicit submission. The signed browser cookie may be used for short-lived, in-memory throttling but its identifier is not stored with your suggestion. Suggestions are excluded from PostHog capture and session recording.
Optional file-identification diagnostics record only fixed categories: the selected format, a coarse size bucket, read completion or bounded-read status, a broad header family, the format-check stage and its outcome. These observations are calculated during normal processing without additional file reads. File bytes, raw signatures, names, paths, document metadata and exception messages are not sent in these diagnostics. Earlier failures cannot be reconstructed from them, and a missing signature does not prove why identification failed.
Purchases
Stripe collects payment details, billing location, and information needed to process payment and calculate applicable tax. Openable stores account-linked purchase references, checkout and payment identifiers, price and currency, payment status, capacity grants, and refund or dispute events. Openable does not store full payment-card numbers or security codes.
Purchased capacity is linked to your account so it can be used across devices. Sandbox purchases and live purchases have separate balances. Our Purchase Terms explain capacity and support commitments.
Device preferences
A language cookie can remember your choice for one year. PostHog stores its pseudonymous analytics identifier in local storage.
Account-free scan allowance
Openable assigns a random, pseudonymous browser identifier in an HttpOnly cookie.
It records only the number of bytes reserved and scanned against the free allowance.
Filenames, paths, checksums, formats, and file contents are not included.
Diagnostic submissions are throttled per browser token in a short in-memory window. Cookie-less visitors receive a reusable signed browser token so their reports can be counted without an account; quota enforcement never reconnects a deleted cookie or a separate browser, and some allowance bypassing is accepted.
Accounts and sign-in
You can sign in by email or, when configured, through Google or Facebook. Email sign-in uses a single-use code that expires after 15 minutes and stops working after a few wrong attempts. Google can create a new account when it confirms a verified email address. Connecting a social identity to an existing account, and creating an account through Facebook, require a single-use email code; matching email text alone never links accounts. Provider secrets and access tokens stay on the server, and access tokens are discarded after the identity lookup.
Signing in stores a random session identifier in an HttpOnly cookie for up to one year. Signing out ends that session on the server and clears the cookie.
With explicit sign-in to continue a paused scan, this browser's used allowance is counted once toward the account's lifetime total, and unfinished sources continue under the account balance. Completed sources are never charged again. Earlier anonymous feedback and diagnostic history are not attached to the account.
Your account activity records sign-ins, sign-outs, confirmed byte usage and support-request receipt, without file names, paths, hashes or file contents. The account page shows the latest 100 activity entries and 50 support requests.
If you explicitly request personalized support, Openable stores your message, recovery format and outcome, an opaque operation reference, and your account identity. Files are uploaded only when you explicitly choose to share one for support. The request is separate from anonymous feedback and automatic analytics; its message is excluded from analytics and session recording. A receipt is emailed to your verified account address. An email notification containing the request reference and account plan is sent to the owner’s Gmail inbox; it links to the protected dashboard rather than including your message or file. Owner review notes, statuses, and their history are stored to manage the request. Free-account support is offered as capacity allows, without a guaranteed response. Paid accounts are guaranteed a personalized response, a review, and an effort toward a solution, but not a fix or successful recovery. Account activity and support records persist while the account is active and are included in account-related privacy requests.
The account balance records only byte totals against opaque browser and account identifiers. It never includes filenames, paths, formats, checksums, file contents, comments, or diagnostic links.
To request deletion of the Facebook-specific information Openable holds, remove Openable from Facebook Settings under Apps and websites, open the removed app's details, then select Send Request. Removing the app disconnects Facebook access but does not by itself confirm that a deletion request reached Openable. When Meta sends its signed request, Openable removes the Facebook identity, pending Facebook email proofs, and related sign-in challenges, then returns a status link and confirmation reference. This does not delete your separate Openable account email, cumulative allowance, account activity, or any support request you submitted. To request access, correction, or deletion of Openable account records, contact Openable through its listed privacy channels.
How information is used
Openable uses service data to provide and secure the website and to remember your language preference, manage account balances and purchases, and respond to support requests.
It also uses service data to understand aggregate performance, improve recovery workflows, diagnose errors, and run authorized social publishing.
Openable displays advertisements for our own projects. These placements do not load a third-party ad network or use your files to choose an ad. Your account balance determines whether an ad is shown: ads are hidden while purchased capacity remains. Following an ad opens the project’s website, which has its own privacy policy.
Where applicable, processing relies on providing the requested service, legitimate interests in operating and improving Openable, consent, and compliance with legal obligations.
LinkedIn connection
When a LinkedIn Page admin authorizes Openable, the integration may receive the admin and Page identifiers, Page roles, and authorization tokens.
It may also receive Page content, publishing results, analytics, and social interactions needed to publish and measure Openable Page activity.
LinkedIn data is used only to manage the authorized Page.
Member profile data is refreshed or deleted within 24 hours, and member social activity within 48 hours, unless LinkedIn permits a longer period.
Authorization credentials are retained until the connection is revoked, expires, or is deleted.
AI-assisted content uses materials supplied by Openable. LinkedIn member data is excluded from AI training and content generation.
Service providers and disclosure
Openable uses Hetzner for hosting, PostHog EU Cloud for analytics, Resend for transactional email, and Stripe for checkout and payment processing. Google and Facebook process sign-in information when you choose their sign-in options; LinkedIn is used when an administrator enables its publishing integration. Owner support notifications are delivered to Gmail. Providers may process data in countries other than your own, subject to their applicable data-protection terms and safeguards.
These providers process information to deliver their services under their own terms and data protection commitments.
Openable never sells personal information or uses it for targeted advertising.
Information may be disclosed when required by law or needed to protect users, Openable, or the public.
Retention and control
Device-local files remain until you delete them or clear browser storage. Language preferences expire after one year.
The anonymous scan cookie lasts up to 400 days. Quota records are removed after two years without quota activity. Diagnostic throttling uses a short in-memory per-browser window and stores no network-address keys.
Account sessions last up to one year and end on sign-out. Sign-in codes expire after 15 minutes; expired code records are removed in bounded batches during later sign-in requests. Account byte totals persist while the account is active so the lifetime allowance stays accurate.
Purchase, payment, tax, and support records are retained as needed to provide the service, resolve disputes, prevent misuse, and meet legal recordkeeping obligations. Some records may need to be retained after an account-deletion request. Owner notification emails may remain in the owner’s mailbox; privacy requests also cover those messages. Analytics are kept while useful for product and security analysis, then deleted or aggregated.
LinkedIn data follows the periods described above and LinkedIn's current requirements.
You can clear browser data, enable Do Not Track, or revoke LinkedIn authorization.
You can also request access, correction, or deletion of information associated with you. Openable honors applicable privacy rights and verifies requests when needed.
Security and changes
Openable uses encrypted connections, limited access, and data minimization to protect information.
This policy may change as the service develops. The effective date above will reflect material updates.
Contact
For privacy questions or requests concerning Bee Software LLC’s Openable service, email support@openable.fyi. Where applicable, you can also complain to your local data-protection authority.