manyloomPrivacy & terms
PrivacyTermsSecurity← Home
Privacy & terms

Privacy, written to be read.

You are handing Manyloom real work: projects, clients, invoices, and the keys to your other apps. So this page is honest and plain, a real policy you can act on. If a line matters to you, it’s written so you can actually understand it.

Last updated: November 15, 2026Maker: BUTENKO ART STUDIOBased in: Burnaby, BC, CanadaContact: privacy@manyloom.com

01 · What this is, and who we are

Manyloom is the workspace for small service businesses. An assistant we call Loomy sorts your work into clients, projects and tasks, builds small tools for you, syncs Google Calendar and imports from Notion, runs invoicing and books, and can act on your behalf when you ask it to.

Manyloom is made by BUTENKO ART STUDIO, a studio based in Burnaby, British Columbia, Canada. Here, “we”, “us”, and “Manyloom” mean the same thing. “You” means the person or business using the product.

This policy explains what data we hold, why, who else touches it, and the control you have over it.

02 · What we collect

We collect only what the product needs to work for you.

Account data

  • Your name, email, and password (stored hashed, never in plain text).
  • Your plan and billing status. Card details go straight to Stripe, and we never see or store them.

The work you put in

  • Projects, tasks, notes, and plans you create or that Loomy drafts for you.
  • Personal information inside that work, like client names, contacts, invoice figures, and anything else you include.

Content from connected apps

  • When you connect an app (Google Calendar, Notion), we read only the content described for that app. What we do with data from Google is set out in “Google user data” below.
  • We request the narrowest access a feature needs. We do not scrape your whole account.

Usage data

  • Basic, privacy-first analytics: which features are used and where errors happen, so we can fix and improve them.
  • No ad-tracking, no third-party trackers, no advertising cookies.

If you try the demo

  • When you open the demo we store the email you enter, plus which parts of the demo you viewed and for how long, so we can improve it and occasionally email you about Manyloom.
  • Every marketing email has a one-click unsubscribe, and you can have your demo record deleted anytime by writing to privacy@manyloom.com.

03 · How we use it

We use your data to run Manyloom and to let Loomy do the work you ask of it:

  • To sort your work into tasks and plans, build tools, and connect your apps.
  • To let Loomy draft, organise, and propose actions on your behalf.
  • To run the invoicing and money layer you set up.
  • To bill your subscription, support you, and keep the service secure and reliable.

We do not sell your data. We do not use it for advertising. We don’t share it except with the sub-processors named below, all of whom act only to run the service for you.

Support access to your workspace

We do not access the contents of your workspace unless you grant support access, or where strictly necessary to comply with the law or protect the security of the Service and its users. When you grant support access (in Settings > Security), authorized staff may view your workspace in read-only mode for the window you set. We record who accessed it, which workspace, and when; we email you when each access begins; and staff are bound by confidentiality. We do not use your workspace contents to train models. Authorised Manyloom staff may access your workspace remotely from Canada or from another country, only through the support access you grant and under the controls described above.

Operational and audit records

To run the service, keep it secure, and support you, we keep an internal record of account-level events: subscription and payment changes, support actions we take on your account (like a comped month or a support-access session), and technical errors. These records are tied to your account, are used only to operate, secure, bill, and support the Service, and are never sold or used for advertising. We keep them for as long as needed to run and secure the Service and to meet our legal, tax, and accounting obligations.

04 · AI and your data

Loomy is powered by AI, and this is the part people worry about, so we keep it plain.

  • We do not train AI models on your data, and we never permit a provider to. Your work is not used to teach any model, ours or anyone else’s.
  • We keep your content inside Manyloom’s own infrastructure wherever we can, and we minimise any exposure to outside AI providers. Where a feature relies on a third-party AI provider, that provider acts only as a processor bound by contract, is not permitted to train on your content, and is named in the sub-processors list below.
  • You stay in control of what AI touches: mark any item Private so it stays on Manyloom’s own infrastructure and is never sent to any outside AI provider, or Sealed so no AI reads it at all.
  • Your work is used only to produce the result you asked for, and it is never carried into anyone else’s account.

05 · Connected apps and permissions

  • Connections use OAuth, the standard way to link apps without sharing your password.
  • We ask for least-privilege scopes: the smallest permission a feature needs, and no more.
  • You can see every connection you’ve granted on the Connections page and revoke any of them in one click, and Loomy loses access immediately.
  • Your access tokens are held in an encrypted secrets vault, never in plain text.
  • Private calendar link. You can make a read-only link to your Manyloom calendar for Apple Calendar, Outlook or another calendar app. It carries your visits, bookings, meetings and due dates (never a Sealed project and never events copied from Google), and that app fetches it from us on its own schedule. Anyone with the link can see those events, so we keep only a fingerprint of it; a new link or Turn off on the Connections page stops the old one at once.

06 · Google user data

This section covers the data Manyloom receives from Google when you sign in with Google or connect Google Calendar. Manyloom’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace API User Data and Developer Policy.

What we access

  • Sign in with Google: your name, your email address and whether Google has verified that address. We do not store your profile photo or any Google access token from sign-in.
  • Google Calendar, when an owner or admin connects it: events on your main Google calendar from today to 60 days ahead. For each event we receive only its Google event ID, title, start time, end time and whether it was cancelled, and we keep the ID, title, start and end. We do not read descriptions, locations, guests, attachments or video-call links. We also keep the email address of the connected Google account, so you can see which account is connected, and the OAuth tokens that let Manyloom read the calendar.

How we use it

  • Your name and email address: to create your account, sign you in and contact you about your account.
  • Calendar events: to show them on the project calendars you link and on your Calendar page, next to your visits, tasks and invoice due dates, and to let Loomy answer when you ask it about your schedule.
  • Manyloom only reads Google Calendar. It never creates, changes or deletes anything there.
  • We use Google user data only to provide and improve these features, which you can see in the product.

How we store and protect it

  • Copied events and account details are stored in Manyloom’s database on our own servers in the United States. Data travels between Google, our servers and your browser over encrypted connections (TLS).
  • Google OAuth tokens are encrypted at rest with AES-256-GCM, using a key that is kept outside the database, and are decrypted only on our server to run the sync. Off-box backups are encrypted before they leave our server.
  • Only the owner and admins of a workspace can connect or disconnect Google Calendar.

How we share it

  • We do not sell Google user data. We do not use it for advertising, retargeting or interest-based ads, and we do not use it to decide anyone’s creditworthiness or for lending.
  • When you ask Loomy a question that needs your schedule, the titles and times of the relevant events can be sent to Anthropic, our AI processor, to produce the answer. Anthropic processes them only for that purpose and does not use them to train its models.
  • Our hosting provider and our backup storage (Cloudflare R2, which holds only encrypted copies) store data on our behalf.
  • We may also disclose data where the law requires it, to protect the security of the service, or as part of a merger, acquisition or sale of assets, and in that last case only after asking for your explicit consent.

AI and people

  • We do not use Google user data to develop, improve or train generalized AI or machine learning models, and we do not allow any provider to do so.
  • No one at Manyloom reads your Google user data unless you ask us to (for example, by granting support access), it is necessary for security purposes such as investigating abuse, or the law requires it. Aggregated, anonymised figures used to run the service are the only other exception.

How long we keep it and how to delete it

  • Copied events stay only while the project is linked and your Google account is connected. Each sync removes events that you deleted or cancelled in Google.
  • Stop on a project’s Calendar tab deletes the events copied into that project.
  • Disconnect on the Connections page revokes Manyloom’s access at Google, deletes the stored tokens and deletes every event copied from Google.
  • If you remove Manyloom’s access in your Google Account instead, the sync stops at once and the copied events are deleted at the next sync attempt.
  • If you delete your Manyloom account, everything above is deleted and Manyloom’s access at Google is revoked when the 30-day deletion window ends. Encrypted backups age out within 30 days after that.
  • You can also ask us to delete your Google user data at any time by writing to privacy@manyloom.com.

How to revoke access

  • In Manyloom: open Connections and click Disconnect next to Google Calendar (owners and admins).
  • In your Google Account: open myaccount.google.com/connections, select Manyloom and remove its access.

Changes

  • If we ever want to use Google user data in a way this section does not describe, we will tell you first and ask for your consent before doing so.

07 · Who else touches your data

To run Manyloom we rely on a short list of trusted sub-processors. Each handles a specific job and nothing more.

  • Stripe (United States) for payments. Your card data goes directly to Stripe, and we never store or see it.
  • Resend (United States) for the emails the service sends: sign-in links, billing notices, and the messages a business sends its clients. It receives the address and the message content, nothing else.
  • Telnyx (United States) delivers text messages a business sends its clients, when it turns texting on. It receives the phone number and the message.
  • Meta (WhatsApp Business) delivers WhatsApp messages a business sends its clients, when it connects WhatsApp. It receives the phone number and the message.
  • Cloudflare R2 stores our off-box backups. Backups are encrypted before they leave our server, so R2 holds only ciphertext it cannot read.
  • Contabo provides the servers Manyloom runs on, in Seattle, United States. Your data sits on servers we operate there.
  • Anthropic for part of Loomy’s reasoning. Set commands are read on our own servers. When a request needs more than that, your request and a short packet of the items it concerns (for example the open orders it asks about) are sent to Anthropic’s Claude models to produce the answer. This can include the titles and times of events copied from Google Calendar when your request is about your schedule. Anthropic acts as our processor and does not use this content to train its models. Items you mark Private or Sealed, everything that belongs to a Sealed project, the health fields on a client’s card, email addresses, phone numbers, passcodes and sign-in data are never sent.

If we add a provider, including any AI provider used by a feature, it appears here first. If this list changes in a way that affects you, we’ll update this page. Questions about our service providers outside Canada, and the countries and purposes for which they handle personal information, go to privacy@manyloom.com.

08 · Where your data lives

Each workspace is stored in one hosting region, set when the workspace is created and shown in Settings. Today that region is the United States (Seattle, Washington). Your workspace data and its files stay in that region; encrypted backups of them are kept with Cloudflare R2.

A few services process limited data outside your region: Stripe for payments (United States), our email and text-message providers to deliver messages, and the AI provider that answers some Loomy requests (see section 04). Each one is named, with its location and purpose, in section 07. Data held in another country may be accessible to the courts, law enforcement and national security authorities of that country.

Your data is encrypted in transit. Your password is stored hashed (never in plain text), and your connected-app tokens and our off-box backups are encrypted at rest.

How AI handles your content, and the Private and Sealed controls you have over it, is covered above in “AI and your data”.

09 · Your data is yours

Under Canadian privacy law (PIPEDA) and the GDPR, you have clear rights over your data. We build them in rather than making you ask.

Export

You can export your whole account at any time, yourself, from the Export page, in one click, in an open format you can read and reuse. You leave with everything, at no extra cost.

You can also download your books at any time, including after you close your workspace: the general ledger and the reports, every invoice, every bill and expense, payments and bank lines, for any period.

Retention while active

While your account is active we keep your data so the product can work. Finished work moves into your Archive and is kept whole. We keep your data for at least 12 months from your last payment so you can always come back to it and export it.

When a subscription ends

Your work stays put when you stop paying, all of it. Active use is paused (you’re taken to a reactivation screen), but you can still export your whole account at any time from there. Resubscribing picks up exactly where you left off, with nothing lost.

Deletion

You can delete your account whenever you want, right from your settings, by yourself. Deletion runs on a 30-day grace window: your account keeps working, and you can undo it any time within those 30 days. After the 30 days we permanently delete your workspace from our live systems, and revoke every access token to your connected apps, except your books: invoices, credit notes, bills and their receipts, payments, bank lines and the journal.

We keep your books locked and read-only for the record-keeping period of your tax country, which we show you before you close (for example, six years in Canada), so you can still sign in and download them; then we delete them. You can delete your books with everything else once you have downloaded a complete copy and confirmed that keeping it is now your responsibility. You can also request deletion by writing to privacy@manyloom.com.

Encrypted backups that were taken before your deletion aren’t edited record-by-record; they age out on a rolling 30-day window,* after which no copy of your data remains anywhere. This is also how we honour a right-to-erasure request under the GDPR and PIPEDA.

* Backups exist only to restore the whole service after data loss. They’re encrypted and are never used to look anyone up individually. Worst case, a copy in a pre-deletion backup is gone within 30 days of the permanent deletion.

10 · Cookies and analytics

  • Manyloom is privacy-first and cookieless for analytics. No advertising cookies, no third-party trackers.
  • Our analytics count usage in aggregate; they don’t follow you across the web.
  • We use essential cookies to keep you signed in and secure, plus a first-party cookie on the public demo to remember your unlock and count demo usage. No advertising cookies, no cross-site tracking.

11 · Children, international users, and changes

Children

Manyloom is for adults and businesses. You must be 16 or older to use it, and we don’t knowingly collect data from anyone under 16.

International users

You can use Manyloom from anywhere, and wherever you are the rights above apply. Your data is stored on our own servers in the United States. If you’re in the EU or UK, your data is transferred to the US under appropriate safeguards (standard contractual clauses), and the GDPR rights described here are honoured.

If a breach happens

If a security breach ever affects your data, we’ll tell you and notify the relevant authority as the law requires. We won’t hide it.

Changes to this policy

If we change this policy in a way that matters, we’ll update the date above and let you know. We won’t quietly weaken your protections.

Made by BUTENKO ART STUDIO · privacy@manyloom.com · Privacy · Terms · manyloom.com