Privacy policy

How moss handles your data

Effective 15 November 2026.

Controller: Moss LLC. Our registered office and company registration details will be published here before moss is generally available.

This policy explains what data moss collects, why, and what we do with it. The short version: we collect the minimum needed to run the product, we do not sell data, we do not run advertising on moss, and you can request a copy of your data or its deletion at any time by emailing privacy@mossfold.com.

1. Who we are

moss is operated by Moss LLC, a limited liability company. For the purposes of GDPR and UK GDPR, Moss LLC is the controller of the personal data held in moss accounts. Our registered office and company registration details will be published on this page before moss is generally available.

When you use moss as part of a workspace owned by your employer, that employer is the controller of the workspace data, and Moss LLC is the processor acting on their instructions. We sign a Data Processing Addendum on request.

Reach our data protection contact at privacy@mossfold.com. We aim to reply within two working days.

2. What data we collect

We collect the minimum needed to run your account. The categories are:

  • Account data. Your email address, the display name you choose, and an optional avatar image.
  • Authentication data. Signing in is passwordless. We send a 6-digit one-time code to your email. The code is stored hashed, expires 10 minutes after it is issued, and is invalidated on first use. We do not store passwords because moss does not use them.
  • Workspace data. The tools, people, processes, work maps, and finance records you enter, along with their relationships. Work Maps are drawn in moss's own canvas editor and stored as document snapshots in our database.
  • Session data. A signed session cookie, the IP address and user agent of the request that created the session, and the time of last activity. Sessions are stored server-side and can be revoked.
  • Technical data. Request and error records our hosting provider keeps to run the service, which can include the URL path, the browser type, and a stack trace. We do not attach the contents of forms or workspace records to them.
  • Email logs. The fact that we sent you a one-time code or an account notice, the recipient address, the timestamp, and the delivery result. We do not log the code itself.

The product sets three first-party cookies: the session cookie, a short-lived challenge cookie during passkey sign-in, and a cookie that remembers which workspace you last had open. Small preferences such as your theme live in localStorage. None of them are used for tracking. The cookie policy lists every value.

3. What we do not collect

Stated affirmatively, so there is no ambiguity:

  • No advertising identifiers. moss does not run advertising and is not part of an ad network.
  • No cross-site tracking. We do not place pixels, beacons, or third-party cookies on the product.
  • No third-party analytics SDKs. No Google Analytics, no Mixpanel, no Segment, no equivalent.
  • No purchased data. We do not buy data about you from data brokers.
  • No enrichment. We do not enrich your account with data from people-search, contact-enrichment, or social-graph services.

4. Why we collect it

Our lawful bases under Article 6 of GDPR are as follows.

  • Contract (Article 6(1)(b)). Running the account you signed up for: authenticating you, storing your workspace, sending the emails the product needs to function.
  • Legitimate interest (Article 6(1)(f)). Keeping the service secure, detecting fraud and abuse, and measuring basic service health (uptime, error rates, slow endpoints). We have weighed this against your rights and limited the scope to what the operation of the service requires.
  • Consent (Article 6(1)(a)). Anything optional that needs your permission, such as connecting your Google Calendar or Google Drive account to a workspace. We ask explicitly before the connection is made, and you can disconnect and withdraw consent at any time.
  • Legal obligation (Article 6(1)(c)). Retaining invoices and tax records for as long as the bookkeeping and tax law that applies to us requires, once paid plans exist.

5. Who we share it with

We use a small set of trusted subprocessors to run moss. Each has a data processing agreement with us and processes data only on our instructions.

ProviderWhat it handlesRegion
VercelApplication hosting and edge deliveryEU and US regions
NeonPostgres database and backupsEU region (Frankfurt)
ResendTransactional email (one-time codes, account notices)United States for stored email data
CloudflareTimer that starts moss's scheduled jobs; it holds no company dataGlobal network

We do not sell personal data, we do not share it with advertisers, and we do not transfer it to partners for their own marketing. If we add or change a subprocessor, we update this page and email account owners in advance.

Optional integrations are different from subprocessors. If you choose to connect Google Calendar or Google Drive to a workspace, moss exchanges data with Google on your instruction: calendar events and synced files flow between your Google account and your workspace. Google acts as an independent controller of your Google account under its own privacy policy, and you can revoke moss's access at any time, either in moss or from your Google account settings.

moss's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the calendar and file features you see in your workspace: it is never used for advertising, never sold, and never read by humans except with your permission for support, for security, or where the law requires it.

6. Where data is stored and for how long

The primary database is hosted in the EU (Frankfurt). Our database provider keeps a rolling 6-hour history of it for point-in-time recovery. Before each planned change to the database we also take a copy by hand, which we keep until we delete it. Specific retention windows:

  • Account and workspace data. Kept while your account is active. When you ask us to delete it, we delete it from the live database. The provider's 6-hour history then ages out on its own, and we delete it from our manual copies too.
  • Session data. A session ends after 30 days without use, and at the latest 90 days after sign-in. Expired and revoked session records are deleted in a weekly clean-up.
  • Request and error logs. Kept by our hosting provider for the short period its plan sets, then deleted.
  • Emails and send logs in Resend. Kept for 30 days on our current Resend plan, stored in the United States, then deleted. Stored emails include sign-in codes, which stop working 10 minutes after they are sent.
  • Invoices and tax records. Once paid plans exist, retained for the period required by the bookkeeping and tax law that applies to us.

7. Your rights under GDPR

Under GDPR and UK GDPR you have the right to:

  • Access the personal data we hold about you, and receive a copy of it.
  • Rectify data that is inaccurate or incomplete.
  • Erase your data (the right to be forgotten), subject to legal retention duties.
  • Restrict processing while a dispute is being resolved.
  • Receive your data in a portable, machine-readable format, and have it sent to another controller where technically feasible.
  • Object to processing based on legitimate interest.
  • Withdraw consent at any time, where consent is the basis of processing.

To exercise any of these rights, email privacy@mossfold.com. We respond within 30 days, the period set by GDPR. You also have the right to lodge a complaint with the data protection supervisory authority of the country where you live or work. In the EEA, any of the national authorities listed by the European Data Protection Board can take your complaint.

8. International transfers

Primary storage of your data is in the EU. Some processing happens outside the EEA, for example when a Vercel edge function serves a request from a US region, or when Resend routes a transactional email through US infrastructure.

Where data leaves the EEA, we rely on the European Commission's Standard Contractual Clauses, and on the EU-US Data Privacy Framework where the recipient is certified under it. Each subprocessor agreement names the applicable safeguard.

9. If you are in the United States

We apply the standard described in this policy to everyone, wherever you live. You can request access to, correction of, or deletion of your personal data by emailing privacy@mossfold.com, and we will never treat you differently for exercising a privacy right.

In the terms used by US state privacy laws such as the California Consumer Privacy Act: we do not sell personal information, we do not share it for cross-context behavioural advertising, and we do not use it for targeted advertising or for profiling that produces legal or similarly significant effects. There is therefore nothing to opt out of. We honour the Global Privacy Control signal. If a US state privacy law applies to you and grants rights beyond those listed above, email us and we will honour them.

10. Security

  • All traffic is encrypted in transit with TLS 1.2 or above.
  • Data is encrypted at rest at the database layer.
  • Signing in is passwordless. There is no password store to breach.
  • Session cookies are HttpOnly, Secure, and SameSite=Lax.
  • A session ends after 30 days without use, and at the latest 90 days after sign-in. You can review and end your sessions in Settings at any time.
  • Only the owner of Moss LLC has access to the production systems. The application itself connects to the database with its own restricted login, which cannot change the database structure or delete audit history.
  • Every change is released only after local checks pass: lint, type checks, tests and an automated test that one company's data cannot reach another. There is no automated build pipeline yet. We check dependencies for known vulnerabilities by hand.

11. Children

moss is built for adult professional use. We do not knowingly collect data from anyone under the age of 16. If you believe a child has created an account, email privacy@mossfold.com and we will remove the account and any related data.

12. Changes to this policy

We update this policy when the product changes, when a subprocessor is added or replaced, or when a law that applies to us changes. Material changes are announced in-product and by email to account owners at least 14 days before they take effect. Minor edits (typos, clearer wording) take effect when the effective date at the top of this page is updated.

13. Contact

Privacy questions, data requests, and DPA requests: privacy@mossfold.com.

Our registered postal address will be published here, together with our company registration details, before moss is generally available. Until then, email is the fastest route and a valid channel for any privacy request.

This page is not a substitute for legal advice. If you operate moss on behalf of a company that processes personal data in the product, sign a Data Processing Addendum with us before going live by emailing privacy@mossfold.com.