Security and data, in plain words.
Where your data lives, how it is protected and backed up, what Loomy does with it, and how you take it with you.
01 · Where your data lives
Manyloom runs on a server we operate in the United States (US West). Every connection to it is encrypted with HTTPS. Each account is walled off from every other: every read and every change is checked against the account it belongs to.
02 · Backups
The whole service is backed up every hour. Each backup is encrypted on our server before it leaves, then stored with Cloudflare R2 in a separate location, which holds only ciphertext it cannot read. The key to open them never touches our server; it is kept in a founder’s password manager.
Backups are kept for 30 days. Restoring one follows a written, step-by-step procedure.
03 · Loomy and AI
Loomy reads set commands, and the phrases you have used before, on our own servers with no outside model. When a request needs more than that, the request and a short packet of the items it concerns go to Anthropic, our AI processor, named in the privacy policy; Anthropic does not train on it. Health fields on a client’s card, email addresses, phone numbers, passcodes and sign-in data are never sent. Your work never trains a model and is never sold.
You choose per item: mark something Private and it is processed only on Manyloom’s own servers, or Sealed and no AI reads it at all. Anything Loomy would send, publish or charge waits for your OK, and you can undo what it changed.
04 · Payments and sign-in
Card details go straight to Stripe, our payment processor. Manyloom never sees or stores a card number. When your clients pay your invoices, the money goes to your own Stripe account.
You sign in with a one-time link sent to your email, or with Google. Tokens for the apps you connect, such as Google Calendar, are stored encrypted, and you can disconnect them at any time.
05 · Watching over it
The service is monitored around the clock. If it stops answering, the founders get an alert within minutes; a backup that did not run is flagged within 90 minutes. Every deploy takes a backup first and keeps the previous version ready to switch back to.
06 · Taking your data with you
Export your whole account yourself, at any time, from the Export page, in an open format. Closing your account starts a 30-day window in which you can change your mind; after it, your data is deleted from our live systems, and encrypted backups age out within the following 30 days.
The full detail is in the Privacy Policy. Questions about security: privacy@manyloom.com.