Policy for privacy

Wetin e cover

Dis policy cover Openable website, tools for recovering files inside browser, accounts, purchases, support requests and social platform connections wey you authorize. Na Bee Software LLC for New Mexico dey operate Openable.

How we dey process file

Openable dey process files wey you select inside your browser. File contents, filenames, folder paths, checksums, and previews remain for your device unless you deliberately choose to share file with support.

Scanning and recovery dey happen for your device. If you choose clearly to share file for support request, dat file go leave your device and Openable go store am privately to investigate dat case. Sharing na your choice and e no guarantee recovery. You fit share one file up to 2 GB for each request. Na only authorized support staff fit access am; dem no dey serve shared files publicly, send dem to analytics, publish dem as examples, use dem for AI training or add dem to test fixtures without separate permission. Dem keep shared files for 30 days before scheduling deletion; you fit delete your shared file earlier from Your account. Scheduled cleanup dey also remove uploads wey no complete. Support request and e message still remain separate account records when dem delete shared file.

Choose one or more originals wey dis problem affect. Dem go send plenty files together as one ZIP, up to 2 GB total. Archive entries go use anonymous example numbers.

If you save scan inside di local library, your browser go store im manifest. E fit still store di originals wey you select and copies wey you recover inside IndexedDB.

We no duplicate large source selections into browser storage. Na you control dis library, and you fit delete saved scans any time.

Information wey Openable receive

Data for service and security

Web requests fit include IP address, browser information, di page wey person request, referral information and time wey dem access am.

Di server dey use DB-IP country database wey dem install for di server itself to find country code as language fallback, after your saved preference and browser language. Dem no dey send your IP address to DB-IP for dis lookup. Dis one different from scan allowance and diagnostic counting, wey no dey use IP addresses. Hosting and analytics providers fit receive your IP address as part of network requests; Openable no dey claim say visiting di website hide your IP address.

How people dey use di product

Openable dey use PostHog EU Cloud for limited analytics.

E fit include pseudonymous browser identifier, page paths, where visitors come from, performance measurements, errors wey we sanitize, and clicks for links or buttons wey we mark.

Session recording dey off. We dey respect Do Not Track settings for your browser.

If you allow am, Openable go use Google Analytics 4 measure page views, sessions, where visitors come from, and their rough location. Google go receive network information, including your IP address, and e fit save analytics cookies. We dey send only known public page paths, without query strings, account details or file details. Google Analytics go stay off until you allow am, and e go respect Do Not Track plus owner/test exclusions. You fit change your choice for Google Analytics settings for di bottom of di page.

How Google dey use information from sites wey use e services

Openable dey also send copies wey no get content 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 no dey inside these copies. Private server records still be di correct record for accounts and payments; copied events no prove say person pay or save downloaded file.

Numbers wey show recovery activity

Analytics fit include scan mode, number of files, format categories, size and duration groups, result categories, recovery results, and number of downloads.

File content and details wey fit identify di file no enter analytics.

To count different files wey people try and recover, Openable keep private random key inside dis browser and use am to turn complete file fingerprint into identifier wey no reveal identity. Na only dat hidden identifier, format, fixed problem category and recovery outcome, if e dey available, dem send to Openable own reporting store. Di raw fingerprint and private key remain for your device. Dis one distinguish retries for di same browser without uploading filenames or file contents. If you clear browser storage or switch browser, di distinction go reset. Separate browser identifier dey help exclude internal tests. Do Not Track dey stop dis reporting.

Optional first-party product measurements dey keep fixed, common extension categories for unsupported file selections, and group extensions wey no dey listed as other instead of sending any suffix wey person type. Dem assign random references to scan batches and individual file selections so scan results, recovery requests, and downloads fit link without sending filenames or contents. Records for fixed categories wey never send fit wait inside dis browser for up to 24 hours for another try, with storage limit. These optional first-party measurements dey use private browser identifier to connect recorded visits, scans, when recovery start and im results, views of recovered-photo previews, download actions, allowance interruptions, and checkout activity. Dem include approximate country code wey server derive from im local country database when reports arrive, without storing IP address inside these records. Dem also include fixed categories for page, referral, browser, operating system and device, page-performance measurements, number of unhandled errors without their messages, and release reference. When you sign in, server fit connect these records to your account, show confirmed purchase history beside batch, and match opaque order reference with confirmed purchase. These measurements no dey upload files, filenames, raw fingerprints, full URLs, or error messages. Do Not Track and registered exclusions for internal tests dey stop dis optional reporting.

Optional analytics from our own system dey also record di exact size in bytes for each file wey you select, to investigate reliability and storage failures. Dem no include file contents or filenames.

Reports about unusual recovery cases

When recovery unexpectedly fail for format wey system support, Openable fit send fixed technical categories to e own server.

Dese na format, container type, recovery stage, diagnostic code, rough size group, scan result, detection method and confidence, plus decoder state.

Di server dey derive case ID from dose categories and add one to di total count.

E no dey receive or store di file, filename, path, checksum, file fingerprint, preview, file content, or raw error text.

File types wey we suggest

If you deliberately suggest file type wey we fit support later, Openable go store di type wey you choose or extension wey you type, your language, di form entry point, random submission reference to stop duplicate retries, and di time you submit am. We no upload any file. No enter filename or personal information. Suggestions dey separate from automatic analytics and recovery results; Do Not Track no dey stop submission wey you deliberately make. We fit use di signed browser cookie to limit repeated submissions inside memory for short time, but we no store im identifier with your suggestion. We exclude suggestions from PostHog capture and session recording.

Optional diagnostics for identifying files dey record only fixed categories: di format wey you select, rough size group, whether reading finish or stop at di read limit, broad header family, di stage where format check reach, and im outcome. We calculate dis information during normal processing without reading di file extra. We no send file bytes, raw signatures, names, paths, document metadata, or exception messages inside these diagnostics. We no fit use dem to rebuild earlier failures, and missing signature no prove why identification fail.

Purchases

Stripe dey collect payment details, billing location and information wey e need to process payment and calculate tax wey apply. Openable dey store purchase references wey link to account, checkout and payment identifiers, price and currency, payment status, capacity wey dem grant, and refund or dispute events. Openable no dey store complete payment-card numbers or security codes.

We link capacity wey you buy to your account so you fit use am across devices. Sandbox purchases and live purchases get separate balances. Our Terms for Purchase explain di capacity and wetin support promise.

Choices for your device

Language cookie fit remember your choice for one year. PostHog dey keep im pseudonymous analytics identifier inside local storage.

Scan allowance wey no need account

Openable dey assign random pseudonymous browser identifier inside HttpOnly cookie.

E record only di number of bytes we reserve and scan against di free allowance.

We no include filenames, paths, checksums, formats, or file contents.

We dey limit how often each browser token fit send diagnostic reports within short time window wey we keep for memory. Visitors wey no get cookie go receive reusable signed browser token so we fit count their reports without account; quota enforcement no dey reconnect cookie wey person delete or another browser, and we accept say some people fit bypass di allowance.

Accounts and how to sign in

You fit sign in with email or, if dem configure am, through Google or Facebook. Email sign-in dey use code wey work once, expire after 15 minutes and stop working after few wrong attempts. Google fit create new account when e confirm verified email address. To connect social identity to existing account, or create account through Facebook, you need email code wey work once; just matching di email text no dey link accounts. Provider secrets and access tokens stay for server, and dem dey discard access tokens after checking identity.

When you sign in, we dey store random session identifier inside HttpOnly cookie for up to one year. When you sign out, di session go end for server and di cookie go clear.

When you sign in yourself to continue scan wey pause, dem go count di allowance wey dis browser don use once for di account lifetime total, and unfinished sources go continue under di account balance. Dem no dey charge completed sources again. Dem no attach earlier anonymous feedback and diagnostic history to di account.

Your account activity dey record sign-ins, sign-outs, confirmed bytes wey you use and receipt of support requests, without filenames, paths, hashes or file contents. Di account page dey show di latest 100 activity entries and 50 support requests.

If you specifically request personalized support, Openable go store your message, recovery format and outcome, opaque reference for di operation, and your account identity. We dey upload files only when you deliberately choose to share one for support. Dis request different from anonymous feedback and automatic analytics; we no put your message inside analytics or session recording. We email receipt to your verified account address. We also send notification email with di request reference and account plan to di owner's Gmail inbox; di email link to protected dashboard, e no include your message or file. We store notes from di owner review, statuses, and their history to manage di request. We offer support for free accounts only as our capacity allow, without guaranteed reply. For accounts wey don pay, we guarantee personalized reply, review, and effort to find solution, but no guarantee of fix or successful recovery. Account activity and support records dey remain as long as di account active, and dem dey included in privacy requests about di account.

Di account balance dey record only total bytes against browser and account identifiers wey no reveal identity. E never include filenames, paths, formats, checksums, file contents, comments or diagnostic links.

To ask Openable to delete Facebook-specific information wey e hold, remove Openable from Facebook Settings under Apps and websites, open di details of di app wey you remove, then select Send Request. Removing di app disconnect Facebook access but e no confirm by itself say Openable receive deletion request. When Meta send e signed request, Openable go remove di Facebook identity, pending Facebook email proofs and related sign-in challenges, then return status link and confirmation reference. Dis one no delete your separate Openable account email, cumulative allowance, account activity or any support request wey you submit. To request access, correction or deletion of Openable account records, contact Openable through e listed privacy channels.

How we dey use information

Openable dey use service data to operate and secure di website, remember your language choice, manage account balances and purchases, and reply to support requests.

E still dey use service data to understand total performance, improve recovery processes, investigate errors, and run social publishing wey dem authorize.

Openable dey show adverts for our own projects. Dis advert spaces no dey load third-party ad network or use your files to decide which advert to show. Whether advert go show depend on your account balance: adverts no dey show while purchased capacity remain. If you follow advert, e go open di project's website, wey get im own privacy policy.

Where e apply, processing depend on providing di service wey you request, legitimate interests for running and improving Openable, consent and obeying legal obligations.

Connection with LinkedIn

When admin for LinkedIn Page authorize Openable, di integration fit receive di admin and Page identifiers, Page roles and authorization tokens.

E fit still receive Page content, publishing results, analytics, and social interactions wey e need to publish and measure Openable Page activity.

We dey use LinkedIn data only to manage di Page wey dem authorize.

We refresh or delete member profile data within 24 hours, and member social activity within 48 hours, unless LinkedIn allow longer time.

We go keep authorization credentials until you cancel di connection, di credentials expire, or dem get deleted.

AI-assisted content dey use materials wey Openable provide. We no include LinkedIn member data for AI training or content generation.

Service providers and who we dey share data with

Openable dey use Hetzner for hosting, PostHog EU Cloud for analytics, Resend for transactional email, and Stripe for checkout and payment processing. Google and Facebook dey process sign-in information when you choose their sign-in options; LinkedIn dey work when administrator turn on im publishing integration. We dey send support notifications for di owner to Gmail. Providers fit process data for countries outside your own, subject to their applicable data-protection terms and safeguards.

Dese providers dey process information to provide dia services under dia own terms and promises to protect data.

Openable never dey sell personal information or use am for targeted adverts.

We fit disclose information if law require am or if e dey necessary to protect users, Openable, or di public.

How long dem keep data and how you fit control am

Files wey dey on your device remain until you delete dem or clear browser storage. Language preferences go expire after one year.

Anonymous scan cookie dey last up to 400 days. Dem dey remove quota records after two years without quota activity. Diagnostic throttling dey use short per-browser window for memory and e no dey store network-address keys.

Account sessions fit last reach one year, and dem end when you sign out. Sign-in codes dey expire after 15 minutes; when person later try sign in, we dey remove expired code records in batches wey get limit. We keep di account byte totals as long as di account active so di lifetime allowance go remain correct.

We dey keep purchase, payment, tax, and support records as long as necessary to provide di service, settle disputes, stop misuse, and meet legal recordkeeping requirements. Some records fit need remain even after you request account deletion. Notification emails to di owner fit remain inside di owner's mailbox; privacy requests still cover those messages. We keep analytics while dem useful for product and security analysis, then delete or combine dem into aggregate data.

LinkedIn data dey follow di time periods we describe above and di current requirements from LinkedIn.

You fit clear browser data, turn on Do Not Track or remove LinkedIn authorization.

You fit also request to access, correct or delete information about you. Openable dey respect privacy rights wey apply and dey verify requests when e necessary.

Security and wetin fit change

Openable dey use encrypted connections, limited access, and reduced data collection to protect information.

Dis policy fit change as di service dey grow. Di effective date above go show important updates.