FileMira
Privacy Policy

Your files stay in your browser. Period.

Effective date: 2026-07-27

Local Processing

Files are processed in your browser, not uploaded to a server

No Tracking

Document content is never included in analytics or advertising

No File Storage

Document contents are never stored — only encrypted references and minimal metadata for optional Drive history

Minimal Storage

Only UI preferences like theme are saved locally

No Notifications

We don't track your activity or send unsolicited messages

Transparent

Clear policies about what data is and isn't collected

Account Optional

No sign-up needed to view files. An account is required only to purchase and restore Pro

Ephemeral

Content is cleared when you close or refresh the page

Effective date: 27 July 2026

1. Introduction

This policy explains how FileMira handles information when the website and browser-based file tools are used.

Contact:

2. Files opened in FileMira

When FileMira works as designed:

  • Files are processed in the browser.
  • Files are not intentionally uploaded to a FileMira server.
  • File content is not stored in a FileMira database.
  • File content is not included in analytics or advertising events.
  • File content is cleared when replaced, cleared, the page is refreshed, or the session ends.

3. Remote content

Markdown remote images must not load automatically. When explicitly enabled, the browser may contact the remote host.

4. Technical information

Hosting, analytics, security, consent, or advertising services may process limited technical information such as browser type, device type, page visited, approximate region, and consent status.

They must not receive document content, file names, parsed values, source keys, or log lines.

5. Account, subscription, and optional Drive-history metadata

FileMira stores the minimal account, subscription, and entitlement information needed to operate the service:

  • A verified FileMira account (email) is required only to purchase a Pro subscription and restore it on another device.
  • Payment records (PayPal order and capture references, amount, currency, status) are stored to maintain an active subscription and reconcile access.
  • FileMira may process product code, subscription status, billing interval, current period dates, cancellation state, provider transaction identifiers, refund/reversal/dispute state, and entitlement audit metadata.
  • Premium workspace preferences (theme, font, viewer defaults) may be stored for active Pro subscribers.
  • For Pro subscribers who enable Google Drive history, FileMira stores encrypted file references and limited metadata such as filename, file type, last-opened time, and last-known modification time.

FileMira does not store the contents of those Google Drive files.

FileMira does not store full card or PayPal credentials. When subscription checkout is made available, payment processing is performed through the identified payment provider; FileMira receives only the provider identifiers and payment-state metadata needed to reconcile access.

Users can disable history, remove individual entries, clear all history, disconnect Google Drive, or delete their FileMira account.

6. Configuration metadata versus file content

Configuration metadata (schemas, recipes, preferences, version metadata, and safe run summaries) is distinct from file content (records, cell values, document text, exported file bytes).

File content is not stored by FileMira merely because a configuration is saved. Claims that saved schemas or recipes are currently active apply only once those supporting packages ship.

7. Cookies and local storage

Local storage may contain UI preferences such as theme, wrapping, table density, and consent choices.

Uploaded or pasted documents must not be stored locally.

8. Advertising

FileMira may display advertising. Advertising providers must not receive document-derived information.

Before production launch, replace generic statements with disclosures for providers actually used.

9. Analytics and diagnostics

Allowed events include coarse feature and error information only. Raw documents and document-derived values are prohibited.

10. Use of limited information

Limited technical information may be used to operate, secure, measure, and improve the website and respond to messages.

11. Providers

List only services actually enabled in production.

12. Retention

FileMira does not intentionally retain opened document content. Actual technical-log and consent retention must match provider configuration.

Where a specific retention period has not been approved, information is retained only as long as reasonably necessary for the stated purpose, legal obligations, dispute handling, security, and account recovery.

13. Choices

Users may manage consent and clear browser preferences where supported.

14. Children

FileMira is a general utility and does not require an account.

15. Security

FileMira uses reasonable measures intended to keep document processing local. No browser environment can be guaranteed completely secure.

16. Changes

Display an updated effective date when the policy changes.

17. Contact