Skip to content
Fetcher

Privacy Policy

Fetcher LLC Privacy Policy

Effective Date: June 14, 2026

1. Introduction

Fetcher LLC (“Fetcher,” “we,” “us,” or “our”) respects your privacy. This Privacy Policy describes how we collect, use, disclose, and protect information when you use our website at https://getfetcher.app (the “Site”) and our Software-as-a-Service platform (the “Service”). It also describes the two security modes in which the Service operates and what they mean for your data.

Our Address:
Fetcher LLC
30 N Gould St
Ste R
Sheridan, WY 82801

Contact: privacy@getfetcher.app

2. Information We Collect

A. Information You Provide

  • Account & Contact Data: name, email address, phone number, physical address, company name, job title, and workspace passphrase or recovery code reminders (if you choose to store them). Note: we do not store your workspace passphrase or recovery code in encrypted workspaces.
  • Billing Data: payment card or bank account details. Payment card numbers are collected and processed directly by our third-party payment processors; we do not store full payment card numbers.
  • User Content (“Your Data”): files, documents, text, and other materials you upload. The form in which we receive this data depends on your workspace mode (see Section 2.D).
  • Communications: contents of emails, support tickets, or other correspondence.

B. Automatically Collected Information

  • Usage & Log Data: IP address, browser type, operating system, device identifiers, pages viewed, clicks, features used, timestamps of access.
  • Cookies & Similar Technologies: essential cookies for operation; analytics cookies to understand usage. You may control cookies through your browser. Some features may not work without essential cookies.
  • Analytics Data: provided by third-party analytics vendors to evaluate trends.

C. Information from Third Parties

Third-party integrations or partner referrals may provide data in accordance with your settings with those services.

D. Workspace Mode Determines What We Receive

Every workspace runs in one of two modes.

Standard Workspaces (default). Your files are stored in a private object-storage bucket (Cloudflare R2) and transmitted over TLS. The server can read them to provide features such as review, ZIP export, and search. We have technical access to file contents as needed to operate the Service.

Encrypted Workspaces (opt-in, per team). When enabled, documents are encrypted in your browser before upload using your workspace’s public key, and our servers receive only ciphertext. We hold no key that can decrypt your file contents. Your workspace’s private key is generated in your browser and never transmitted to us; it is stored only as copies locked by your workspace passphrase and a one-time recovery code, neither of which we possess.

3. How We Use Your Information

We use personal information:

  • To provide, operate, maintain, improve, and secure the Service;
  • To authenticate and authorize access, including issuing short-lived signed links for downloads;
  • To communicate about your account, updates, security alerts, and support;
  • For billing and administration;
  • To detect, prevent, and address fraud, abuse, and technical issues;
  • To comply with legal obligations and enforce our Terms of Service;
  • For marketing communications (where permitted and subject to your opt-out preferences).

Important distinction based on workspace mode:

  • In standard workspaces, we process file contents to provide features.
  • In encrypted workspaces, we cannot process file contents because we do not have the decryption keys. We process only ciphertext and unencrypted metadata (see Section 10) needed to route, store, and display the Service interface.

4. How We Share Your Information

We do not sell your personal information. We may share information:

A. Service Providers & Subprocessors
With cloud hosting, payment processing, email delivery, customer support, and analytics providers. Our object storage is provided by Cloudflare R2. A current list of Subprocessors is at https://getfetcher.app/subprocessors.

B. Business Transfers
In a merger, acquisition, or sale of assets, your information may be transferred, subject to confidentiality obligations.

C. Legal & Safety
When required by law, subpoena, legal process, or to protect rights, safety, and security.
Note for encrypted workspaces: because we hold no decryption keys, we cannot produce readable copies of your encrypted file contents in response to legal process; we can only produce ciphertext.

D. With Your Consent
When you direct us to do so.

5. Cookies and Tracking Technologies

We use cookies and similar technologies for operation and analytics. Essential cookies are required for the Service. You may refuse analytics cookies without losing core functionality.

6. Your Privacy Rights

A. California Residents (CCPA/CPRA)
You may request disclosure, deletion, or correction of personal information; opt out of sale/sharing (we do not sell or share for cross-context behavioral advertising); and request limiting use of sensitive personal information. To exercise rights, contact privacy@getfetcher.app, We verify identity before responding.

B. EEA, UK, or Switzerland (GDPR)
You may access, rectify, erase, restrict processing, request portability, and object to processing. You may lodge a complaint with a supervisory authority.

C. Other U.S. State Rights
State-specific rights to access, delete, correct, and obtain copies may apply. Contact privacy@getfetcher.app to exercise them.

D. Encrypted Workspace Limitation
Because we do not hold decryption keys for encrypted workspaces, if you lose your workspace passphrase and recovery code, we cannot decrypt or return your file contents, even in response to an access request. This is an unavoidable limitation of true client-side encryption.

7. Data Retention and Deletion

We retain your information while your account is active or as needed to provide the Service.

Upon termination:

  • Your data remains in our production environment for 30 days to allow export;
  • We then delete live-system data using industry-standard methods;
  • Encrypted backups may persist for up to 90 days before secure deletion per our rotation schedule.

We may retain information longer if required by law or for legal hold. See our Data Processing Addendum and Data Retention Policy for details.
Note: Encrypted workspace contents that you cannot decrypt due to lost credentials are effectively irretrievable and will be deleted according to the same schedule.

8. Data Security

We implement technical and organizational measures designed to protect your information.

A. Standard Workspaces

  • Files are encrypted in transit (TLS 1.2+) and stored in a private Cloudflare R2 bucket with server-side/at-rest encryption.
  • Tenant isolation is enforced in code: one workspace cannot access another’s requests or files.
  • Downloads are served only through authenticated, capability-checked, short-lived signed links.
  • Operator access is limited and disclosed; we access file contents only as needed to operate the Service.

B. Encrypted Workspaces

  • Per-workspace OpenPGP key pair (Curve25519) generated in the browser.
  • Private key is never transmitted to us; it is stored only as two copies, each wrapped with OpenPGP’s iterated, salted string-to-key at maximum strength, locked by your workspace passphrase and a recovery code.
  • Client-side encryption and decryption are performed via OpenPGP.js. Ciphertext is uploaded and stored; decrypted files travel only to your browser, never back to our servers.
  • The server independently rejects any upload to an encrypted workspace that is not valid OpenPGP, so plaintext is never stored at rest under an encrypted request.

C. What Encrypted Mode Protects Against

  • A breach of our storage bucket (holds only ciphertext);
  • A breach of our database (holds only public keys and passphrase-locked blobs we cannot open);
  • Interception in transit (files are encrypted before upload, over TLS);
  • Operator access (we hold no key, so we cannot read your file contents, and we cannot be compelled to hand over readable copies we do not possess).

D. What Encrypted Mode Does NOT Protect Against (Stated Plainly)

  • Maliciously modified operator. Your clients upload through a web page we serve. A hostile or compromised operator could, in principle, serve a substituted page that captures a document before it is encrypted. This is inherent to browser-based upload flows without installed client software. The protection is against infrastructure breaches and legal compulsion—not against the operator deliberately attacking its own users. We do not offer encryption verifiability or out-of-band public-key checking.
  • Compromised member devices. If a teammate’s unlocked session or device is hijacked, that device can read documents. Encryption protects data at rest and on our servers, not an already-compromised endpoint.
  • Lost credentials. If every member forgets the workspace passphrase and the recovery code is lost, the encrypted files cannot be recovered by anyone, including us. This is the unavoidable cost of zero-knowledge architecture.

E. Tenant Isolation (Both Modes)

Workspace isolation is enforced in code independently of encryption: object keys are namespaced per workspace, and every read passes a capability and ownership check scoped to the viewing member’s workspace. In standard mode, the operator is not isolated from tenant file contents; in encrypted mode, no party but the workspace can read the files.

9. What Is Never Encrypted (Metadata)

Regardless of workspace mode, the following are stored and processed unencrypted so the product functions:

  • Request titles;
  • Client names and email addresses;
  • Checklist labels and statuses;
  • Timestamps;
  • Reminder history;
  • Reporting counts;
  • File names and sizes.

Do not place sensitive content in these fields if it must be protected at the same level as encrypted file contents.

10. International Data Transfers

We process data in the United States. If you are outside the U.S., you consent to this transfer. For personal data from the EEA, UK, or Switzerland, we rely on Standard Contractual Clauses (SCCs) and supplementary measures. You may request our SCCs at privacy@getfetcher.app

11. Third-Party Links

The Service may link to third-party sites. We are not responsible for their privacy practices.

12. Children’s Privacy

The Service is not directed to individuals under 13 (or 16 where applicable). We do not knowingly collect their personal information.

13. Changes to This Policy

We may update this Privacy Policy. Material changes will be posted with a new effective date and, where required, additional notice. Continued use constitutes acceptance.

14. Contact Us

Fetcher LLC
30 N Gould St
Ste R
Sheridan, WY 82801
Email: privacy@getfetcher.app