FolioL2Legal
As at
Sun 22 Nov 2026
Entries
13
Not yet
33
Page seal 2903, 285°19′. Drawn from the SHA 256 of this page’s source text2903
Page seal2903, 285°19′

Privacy notice

What Marsadel collects, where it is kept, how long, who processes it for us, and what the sealed record holds: salted hashes only.

Draft of 22 Nov 2026. Version 0.1. 1

This page says what we collect, why, where it is kept, for how long and who else touches it. It also says what we do not do.

Status today, 22 Nov 2026. Nothing is on sale. Marsadel takes no orders yet and holds no client data. The only data we hold today is about domains the founder owns and written test fixtures. The domain marsadel.com is registered (22 Nov 2026), and this site has been live on it since 22 Nov 2026, in English, served by Cloudflare Pages. Its mail and parking DNS records are not applied yet, and no mailbox exists there.2, 3

Who is responsible. Not yet: legal name and registered address of the company4, trading as Marsadel. Privacy questions go to privacy contact address; no mailbox exists on marsadel.com yet5. For clients, we act as a processor on your behalf; our data processing agreement covers that (summary on /dpa).

1. On this website

  • No tracking. This site is built to set no analytics cookies, no advertising pixels and no third party trackers. We do not use a tag manager.6
  • What our host sees. This site is served by Cloudflare Pages. Like any web host, it receives your IP address and browser details when you load a page.7
  • No forms that store data before an order. Pages are static. You reach us in writing.

2. If you come from the free domain check

Marsadel's own free domain check is part of the Domain Passport, a Marsadel unit in design, and it is not live. As designed, a button on the check leads to our intake page with a signed token holding the domain, the flags found and the time, and nothing is stored on our side until you start an order.8

3. When you write to us

We keep your email address, your name if you give it, and the messages. AI agents draft replies; a person approves each reply before it is sent. Enquiries that do not become orders are deleted after retention period for enquiries9.

4. When you order

WhatWhyWhere it is kept
Business name, contact name, emailTo deliver the unit and send recordsDeletable store
The domains and systems in scopeThey are the workDeletable store; only salted hashes in the Register
Your typed name on the authorisationProof that you authorised the workA hash in the Register; the text in the deletable store
Payment referenceTo match payment to orderDeletable store. Card numbers are held by Stripe, not by us
USDC wallet address, if you pay in USDCTo match paymentDeletable store; the payment itself is public on its blockchain
Sanctions screening resultRequired before workA private chain kept apart from the public Register10

5. During the work

  • Public DNS records of your domain. These are public already.
  • Registrar and DNS host exports you send for proof of control.
  • DMARC aggregate reports. These list the servers that sent mail as your domain, with counts and results. They can include IP addresses of sending servers. We use them to move your policy only when the data is clean.
  • Microsoft 365 sign in and sending logs, for Unit 3 only, exported by your IT firm and sent to us. These include user names and device names. We use them to list every device that sends with a password.
  • Approvals and messages in the Unit Room.

We read only what the unit needs. At launch every unit runs in runbook mode: you or your agency apply each change, and we do not log in to your systems. Agents that read outside content (reports, sites, logs) can call only an approved list of addresses, and can change nothing without an approval event.11

6. What the sealed record holds: hashes only

Our record log (the Register) is a chained, signed log of every event in a unit. It holds no domain names and no personal data in readable form. The software runs today on our own machines; no client record is in it yet.12

  • Every identifier is salted with a secret value for your account before it is hashed. We do not hash domains plain, because a plain hash of a domain can be reversed by hashing every domain in a public zone list.
  • Contents sit in a separate store that we can delete, outside the chain.
  • While your salt exists, we can still match a hash against a zone list. That is why we destroy it.

Deletion. Your order files are deleted 12 months after your order, or at exit if that comes first, and your account's salt is destroyed at the same time.13 We seal the date the salt was destroyed. After that, a hash of your order and its signed record remain, and they can no longer be read back to your domain.

7. What we do not do

  • Do we train AI models on your data? No, unless you tick the separate consent box that allows it.14 The other boxes, bench, lab_env and survival_monitoring, are each separate, optional and off by default (described in our terms, section 4).
  • We do not sell data. We do not share it for advertising.
  • We do not publish any client's name, domain or result without that client's written opt in.

8. Who processes data for us

This is the full list we plan to use. A line marked Not yet is not chosen or not contracted yet. We will publish each change here before it takes effect.

Sub processorWhat it does for usWhat it can seeStatus
Anthropic (Claude API and Managed Agents)Runs the AI agents that build each unitUnit data the agent reads during a runNot yet: account on the company; zero retention lane confirmed for clients who ask for it15
Second model vendorRuns the second model that checks each changeThe raw change and its testsNot yet: vendor chosen and connected16
Supabase (Postgres)Holds the deletable store and the Register tablesOrder data and payloadsNot yet: plan chosen and contracted17
Amazon Web ServicesHolds the signing key (KMS); later the locked copy of daily rootsKeys and daily roots only, no client contentsNot yet: account moved to the company18
GitHubHolds the public commit of each day's rootOne hash a day, no client dataNot yet: anchor account moved to the company; no root anchored outside the firm yet19
OpenTimestamps calendarsTimestamp each day's rootOne hash a day, no client dataFree public service, no contract.20
StripeTakes card paymentsCard and billing detailsNot yet: account live on the company21
FiverrEscrow for buyers who order thereWhat you share on FiverrNot yet: gigs live22
InngestRuns scheduled jobsJob names and payload referencesNot yet: chosen and contracted23
LangfuseRecords agent traces for quality reviewAgent inputs and outputs during a runNot yet: chosen; trace retention set to match the client file deletion rule24
Cloudflare Pages (website host)Serves marsadel.comVisitor IP and browser detailsIn use since 22 Nov 2026. 25
Mail provider for marsadel.comSends and receives our mailMessages to and from usNot yet: chosen; no mailbox exists on marsadel.com yet26
Second cloud for nightly exportsKeeps a copy for continuityEncrypted exportsNot yet: chosen27

9. Where data is kept and moved

  • Not yet: hosting regions for each sub processor, read and listed28
  • EU personal data moves under the standard contractual clauses.29
  • Gulf clients can ask for their data to be hosted in the Gulf on a self hosted lane.30

10. Your rights

You can ask in writing to see, correct, export or delete what we hold about you. We answer in writing within response period31. Our EU and UK representatives are named here.32

11. If something goes wrong

If personal data we hold is exposed, we tell affected clients in writing within a fixed deadline written into every contract.33 Every confirmed bad unit gets a public post mortem on /postmortems, with no client named unless the client agrees.

12. Children

Our services are for businesses. We do not knowingly collect data about children.

13. Changes

Each version of this notice has a number, a date and a sealed hash. Changes to the sub processor list are posted here before they take effect.


Source: Marsadel master plan v2, sections 4.4, 8.1, 8.2 and 8.3. The 12 month deletion and the salt rule are DESIGN figures from plan sections 4.4 and 8.2. Sub processor names come from the plan's rented stack (plan sources S7 and S131); none is contracted on the company yet.

Not yet in place33
  1. 1lawyer review returned, text hash sealed, version 1.0 published
  2. 2contracting company formed; first order taken
  3. 3mail and parking DNS records applied
  4. 4legal name and registered address of the company
  5. 5privacy contact address; no mailbox exists on marsadel.com yet
  6. 6confirm in a real browser that the host injects no analytics beacon; Cloudflare Web Analytics and any automatic beacon turned off for marsadel.com and checked
  7. 7its edge log contents and retention read and recorded with the date
  8. 8Marsadel's free check built; signed token and intake page live, plan week 2
  9. 9retention period for enquiries
  10. 10private chain live, planned after 14 Dec 2026; until then the result is sealed as a hash in the Register and kept in the deletable store
  11. 11these controls built and their planted instruction test passed, plan week 2
  12. 12record log in use for client records, with per client salts
  13. 13retention rule checked against the 365 day recheck, which falls after 12 months; rule confirmed before the first paid order
  14. 14training consent box worded in our terms
  15. 15account on the company; zero retention lane confirmed for clients who ask for it
  16. 16vendor chosen and connected
  17. 17plan chosen and contracted
  18. 18account moved to the company
  19. 19anchor account moved to the company; no root anchored outside the firm yet
  20. 20no root anchored outside the firm yet
  21. 21account live on the company
  22. 22gigs live
  23. 23chosen and contracted
  24. 24chosen; trace retention set to match the client file deletion rule
  25. 25account on the company once the company is formed
  26. 26chosen; no mailbox exists on marsadel.com yet
  27. 27chosen
  28. 28hosting regions for each sub processor, read and listed
  29. 29clauses signed in the DPA
  30. 30Gulf hosting route available
  31. 31response period
  32. 32EU Article 27 and UK representatives appointed and named
  33. 33breach notice deadline set in the DPA

Each item is also marked where it stands on this page.