Privacy Policy — Metadata Cleaner for Firefox

Effective October 22, 2026

This Privacy Policy describes how Myworkingmemory LLC (the “Company,” “we,” “us,” or “our”) handles information for Metadata Cleaner for Firefox, its account verification, processing, downloads, and support (the “Services”). This Firefox edition uses the Company’s separate hosted document-processing service. Its data handling differs from the native Apple apps’ on-device processing.

1. What this hosted service does

You select one ordinary Word .docx or PDF in the Firefox extension. After you confirm the document scope and choose inspection or cleaning, the extension uploads that selected file directly to the Company’s existing Vercel-hosted Node service. This is an upload and server-processing service. It is not the native apps’ on-device processing. The extension does not read your browsing history or the contents of other web pages, and it does not send the selected file’s original filename.

Inputs are limited to 2 MiB per file. The hosted engine limits cleaned outputs to 3 MiB. The original is not modified. The service reports generic finding categories rather than raw author names, comments, filenames, or metadata values. It returns a temporary link to a separate cleaned copy when supported processing and verification finish.

Visible text, form answers, and metadata inside embedded images may remain. This is not redaction or anonymization. Unsupported, malformed, encrypted, or incompletely verified documents are refused.

The Firefox edition is for ordinary documents. Do not submit personal health records, payment-card or security details, government-ID numbers, passwords, API keys, or other authentication secrets. Before processing each file, you must acknowledge that input scope. This acknowledgement does not mean the service detects those contents or establishes regulatory compliance.

2. Documents, reports, and temporary downloads

The application downloads the selected original into memory for processing and does not write the original to application disk storage. Document contents and metadata are handled in memory to inspect the file and create the separate output. The application does not send documents to an AI model or use them for analytics or AI training.

Cleaned copies are stored as AES-256-GCM encrypted data in Neon. The temporary download capability contains the secret needed to decrypt its copy. Anyone who has that link can download the copy while the link remains valid. Keep the link private. The link expires after ten minutes and permits up to five fetches; it may stop earlier when access is disabled or the account grant expires.

Expired downloads become inaccessible under the application’s access checks. Later successful server cleanup clears expired encrypted outputs and result receipts, and deletes expired verification challenges and rate-limit counters. Account, weekly-allowance, and job-history records may remain. This is not a promise that stored data is physically erased at the exact download-expiry time. Provider logs and backups may retain information longer.

The Firefox extension sends the file directly to Myworkingmemory; a ChatGPT upload is not part of the Firefox workflow. Saving or sharing a cleaned copy creates a copy controlled by you or the destination you choose. If you separately use the Company’s ChatGPT or Claude connections, those connections and their providers handle information separately.

3. Account and connection information

Firefox free access requires a verified email address and a high-entropy Firefox access key. An email verification code works once and expires after 15 minutes. Only its hash, the destination email, and its expiry are stored for verification. The code is delivered through Resend. Successful verification creates or replaces the Firefox free-account key. The database stores the email, a hash of that key, verification time, and disabled status. Replacing a Firefox key invalidates temporary outputs authorized by the prior key; it does not replace a paid hosted-service key or add purchased credits. Full Firefox keys are not stored in plaintext in the application database. Before requesting the free-access code, you choose separate, initially unchecked controls agreeing to the Firefox Terms and acknowledging this Privacy Policy. The server retains the accepted versions, page-content hashes, acceptance time and method with the verification record and verified Firefox account.

Free Firefox identities and paid hosted-service identities are separate. Existing paid customers can connect with their hosted-service email and access key. An Apple app purchase or ChatGPT plan does not automatically include paid hosted access. The website purchase flow uses Stripe. The application stores minimal order and payment references, amount, currency, payment/refund/dispute state, pack credits and counters, and purchase/expiry times. It does not receive card numbers or card security codes. A purchase record also retains the accepted Terms and Privacy versions, document hashes, acceptance timestamp, and method. Browser-bound encrypted purchase receipts and existing hosted account recovery remain governed by the hosted-service Privacy Policy.

The extension holds its connected email and access key in memory and Firefox session storage so access can continue during the browser session. It does not save verification codes, selected files, or finding reports in extension storage. Disconnect clears the extension’s connected key, selected document, report, and output link; it does not delete server account or usage records. The extension uses no browsing-history permission, web-page content script, remote executable code, or advertising code.

The server uses an email-derived hash for the weekly allowance and request counters, together with account, job, credential, expiry, and download records, to enforce access and usage limits. One verified successful free cleaning starts a rolling seven-day wait for that verified email address. Reinstalling the extension does not reset the server record. This is email-based allowance enforcement, not proof that separate email addresses belong to different people.

Firefox free access can be re-established by requesting and verifying another email code. This replaces only the Firefox free-account credential. Existing paid hosted-account recovery uses its own separate recovery process and does not restore expired or refunded entitlement.

Necessary website cookies protect hosted checkout receipts, account connection and recovery forms. The Firefox API uses its access key instead of sending website cookies. The service uses server-derived hashes of the platform-reported requester address for signup rate limits; it does not persist the raw address for that application counter. An encrypted receipt for a completed cleaning retains a temporary download capability and generic report for up to ten minutes, so an identical request with the same credential and content-change choice can recover a confirmed result without another cleaning credit.

4. Logs, analytics, and service providers

We use Vercel Web Analytics for page visits and a display of Buy, payment, and first-cleaning milestones. First-party database records provide the underlying conversion counts. A secure, HttpOnly journey cookie lasts up to 90 days. Its hash links browser activity to orders and first verified cleaned copies in our database. Test activity is kept separate. Journey and milestone records remain until removed; no automatic retention deadline is configured. Our tracking code does not send document contents, filenames, email addresses, access keys, OAuth parameters, or temporary download links as analytics event data. Hosting providers still process technical request data as described below.

The hosted service uses no document-model calls, targeted advertising, cross-app tracking, or PostHog product events. It does not write document contents, author values, or filenames to application logs.

Vercel processes the service’s network requests and runtime operations; Neon stores account, verification, usage, and encrypted-output records. Stripe processes checkout and payment information. Resend processes the destination email and Firefox verification message, including its secret verification code, to deliver that message; separate hosted recovery uses Resend as described in the hosted-service policy. Provider records and logs may remain longer than application-token expiry. Hosting providers may process IP addresses, request timing, request paths, errors, and other operational records. A request path can include the secret temporary download capability. We do not promise that provider logs contain no download URLs or that provider logs and backups are immediately or permanently erased.

We use information to operate authorized processing and downloads, enforce limits, maintain security and reliability, answer support requests, comply with law, and establish or defend legal claims. We do not use document contents for advertising, AI training, or product development.

We disclose information reasonably necessary to the service providers described here; to recipients when reasonably necessary to comply with valid process, protect rights or safety, investigate abuse, or establish or defend claims; and in a financing, reorganization, merger, acquisition, or sale subject to appropriate protections. Your use of Firefox, a separate ChatGPT connection, or another file destination is also handled by that independent provider.

5. Support and retention

If you email us, we receive your email address, message, and anything attached. Do not email sensitive documents, access keys, access tokens, signed input URLs, or cleaned-copy download links. Remove private information from screenshots.

Account records remain available for administration and support until removed. Expired grants may remain as records but do not authorize use. Support correspondence is retained as reasonably needed to respond, maintain business records, resolve disputes, and meet legal obligations. No fixed support-record deletion period is promised.

Disconnecting the extension clears its local session data; it does not itself delete server account records, weekly-use records, support email, provider logs, backups, or copies already downloaded. You may request account deletion or access revocation at dean@myworkingmemory.ai. We may need to verify the request. Purchase and refund records may be retained for transaction administration, accounting, disputes and support. Recovering or deleting account access does not itself reverse a purchase. The Terms describe the refund process.

6. Sale, advertising, and tracking

We do not sell personal information, use targeted advertising, share information for cross-context behavioral advertising, or track you across other companies’ apps or websites. The necessary connection cookie is not an advertising cookie. These pages themselves contain no tracking code.

7. Security and your choices

The service uses HTTPS, hashed access credentials, verified-email access, entitlement checks, encrypted temporary outputs, separate copies, and processing limits. The website’s separate account-connection mechanisms remain scoped and expiring. No storage or transmission method is completely secure. Keep independent backups, protect access keys and temporary links, inspect first, and review every cleaned copy before sharing it.

You choose which file to select and whether to upload it for inspection or request a cleaned copy. Removing tracked changes, hidden text, or custom XML requires explicit content-change confirmation. You may disconnect the extension or request revocation from support. You control copies you download or share and must remove those separately.

Depending on your location and applicable law, you may request access, correction, deletion, or a copy of covered personal information, object to or restrict certain processing, or appeal a denied request. We do not discriminate for exercising applicable rights. Email dean@myworkingmemory.ai. We may need to verify the request.

We do not sell personal information or use targeted advertising, so there is no sale or targeted-advertising opt-out to exercise. Authorized agents may submit requests where applicable law permits. We will explain any lawful denial and available appeal process.

8. Children

The Services are general-audience tools and are not directed to children under 13. We do not knowingly collect personal information from a child under 13. If you believe a child supplied personal information through the Services or support, contact us so we can evaluate and delete it as required.

9. International users

Hosting, database, or support systems may process information in the United States or other locations where providers operate. Those locations may have different data-protection laws. Where required, we use lawful transfer and contractual safeguards appropriate to the information and provider relationship.

10. Changes and contact

We may update this policy when the product, providers, law, or practices change. The effective date above identifies this version.

Privacy questions, requests, or complaints: Myworkingmemory LLC, dean@myworkingmemory.ai.