Loam Privacy Policy — Data, Providers, Retention, and Deletion

1. Who we are

Toast2 IT, LLC, a Florida limited liability company (Florida document L21000139665), operates Loam and is the data controller where applicable (“Loam,” “we,” or “us”). This policy covers loam.team, the Loam service and API, and the Loam VS Code extension — including our legacy domain docpro.cloud, which still serves existing installations. Loam is built on Anthropic's Claude and is not affiliated with Anthropic. Toast2 IT, LLC's earlier website, toastnotification.com, now leads here.

2. What we collect

Loam stores session records in its database and some generated media as server files. The main categories are:

Account basics — your email, name, and phone number. Your phone is used for sign-in verification and for the team's voice calls.
Session content — the transcripts of your work with the team, including what you type to the team in VS Code (the team also draws on it when it decides what to call you about and writes your songs), and the documents, code, and audio produced in those sessions. You can stop Loam keeping what you type in Settings, under “What you type in VS Code.”
Team memory & project context — the preferences, decisions, and project details the team records so it can recall them later.
Calls — conversation transcripts (stored for memory synthesis), and, for calls that connect, audio recordings where fetched. Authorized Loam administrators can access cross-account call logs and transcripts for service operation and support; organizational customer-admin access is not shipped today.
Phone and email orders — your request, the agreed delivery, revisions, order history, email messages and attachments, and photos you send during a call. The team also keeps a record of what it could see in each photo so it can discuss the photo with you.
Public contact submissions — the name, email, optional company, inquiry category, message, and request metadata you submit through the Contact form. The form sends that material through Mailjet to Loam’s contact mailbox; it is not added to product memory by the form.
Credentials you connect — API keys, connected-service tokens (such as GitHub), and any cloud-provisioning credentials you provide. These are encrypted (see below).
Technical logs — standard web-server and security logs (such as IP address and request metadata) used to operate and protect the service.

We do not sell your data, use it for advertising, or use your content to train Loam-owned models.

By default, Loam does not scan or upload your source code. Your code is only read when you paste it, attach it, start a workflow that needs it, or turn on Workspace Indexing (which is off by default).

3. How we use it

To provide the service — run your sessions, remember your work across them, produce code and documents, and (when you ask) provision infrastructure.
To reach you — the team's voice calls, meeting invites, and follow-ups, and sign-in verification codes, all sent to the phone or email on your account.
To keep it secure — detect and prevent abuse, debug problems, and protect the platform and your account.

Text messages

Toast2 IT, LLC sends text messages under the Loam name only to the mobile number on your own account. Sign-in codes are texted each time you log in, because that is how you sign in. Other texts — links you ask for during a call, such as a link to send the team a photo, and notices about work you asked us to do — are sent only after you agree to them, which is optional, when you set up your account (see how), in Phone Settings, or on a recorded call. How often depends on how you use Loam. Message and data rates may apply. You can withdraw consent at any time in Phone Settings.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Texts are sent by Toast2 IT, LLC, which operates Loam. Reply STOP to a text from a Loam number to stop all texts, or HELP for help; for support, email info@loam.team.

4. How it's protected

Encrypted at rest. Your credentials, conversation content, team memory, and project context are field-encrypted at rest with Fernet (AES-based) symmetric encryption. The encryption key is held outside the database, and rotating it is a supported operation.
Passwords hashed, never stored. Passwords are hashed with bcrypt and a per-password salt. We cannot read your password and never store it in the clear.
Encrypted in transit. All traffic to Loam is served over TLS (HTTPS).
Isolated per account. Your data is scoped to your account with strict per-account isolation.

Where the line sits, honestly. Four categories are kept in plaintext, and we'd rather tell you exactly where than imply more than we do:

Recall metadata — display names, the phone number we match a return call against, and the keyword tags and short summaries the memory index searches. Encrypting these would break search and recall, so they stay queryable behind strict per-account isolation.
Call transcripts — stored as plaintext (not field-encrypted like session content) so the team can synthesize them into memory.
What a call or session audio starts from — before most calls the team places to you, it writes a brief, and the brief is stored as plaintext with that call’s record. That covers every call about an order (confirming it, delivering it, saying it couldn’t be done, or a call you ordered), a call about a Board note, a call back after a call where something broke or a request may have been missed, a Build Mode call about a blocked milestone, Diana’s design reviews, and a call or session audio made from your VS Code session. Depending on the call, the brief can carry what an order asks for and what you were told “done” would mean, the conversation on the call where you asked for it, up to 16,000 characters of a delivered codebase review or 40,000 of a dev-meeting report, the team’s note on what it checked before delivering, the Board note, what you asked for on the earlier call, the project, milestone and blocker, Diana’s review and her earlier one, the team’s replies and summaries from your VS Code session and the transcripts of calls made from it, and some of what the team remembers about you. Several of these are kept encrypted where they normally live; the copy in the brief is not. What you type to the team in VS Code is not copied, and neither is anything you write in “Send the Team Something”. For a scheduled meeting, the brief keeps only the meeting’s title, time and teammate. Each record’s title is plaintext too. On a call about an order it carries the first words of that order’s request, except the call that checks a request you emailed in. Other titles say what kind of call it is and, depending on the call, your first name, when the earlier call was, the milestone, the meeting, the site reviewed or your VS Code workspace’s name. While a call is live, two more things sit in plaintext on its record: its instructions, including why the team is calling and, on your own calls, how you like to be talked with, if you have answered “How you like to work”; and, when you call in or Meg calls about a request you emailed, what the team remembers about you and that emailed request, held back until you prove who you are. Both are cleared when the call ends. Every call the team places also keeps, in plaintext after it ends, the opening line written for it and a short summary the team writes before dialing for the teammate to refer to. That summary can draw on the brief and title, why the team is calling, what the team remembers about you and, for a scheduled meeting, the meeting’s own brief, such as its agenda, the request behind it and the team’s preparation. These records are deleted with your account.
Session audio and Build Mode runs on our server — session audio you make keeps its script and recording with the episode, and the script retells the session, including what you typed. A Build Mode project the team runs on Loam’s server, rather than in your VS Code, keeps the project files it works from, the team’s output and the documents it makes. They are deleted with your account; deleting the project alone keeps them.
Reception work orders and delivered reports — your request, acceptance terms, revision requests, notes about the order, the delivery receipt, your words in intake and backlog records, the context attached to the order, and the body and sender address of an email request are field-encrypted. Delivered report files, and the photos and attachments you send with a request, are stored as encrypted files using AES-256-GCM. Order status and routing metadata, and the descriptions recorded from photos, are not field-encrypted. A call brief can carry copies of some of these in plaintext, as described above.

The Security page carries the full data table — each data type, whether it's stored, whether it's encrypted at rest, whether it stays searchable, and how you delete it.

5. Service providers & sub-processors

Loam relies on a small set of service providers to operate. When a task needs model reasoning, your content is sent to the AI provider that performs it — it is not sold, used for ads, or used to train Loam-owned models.

Anthropic (Claude) — performs the core AI work.
Google (Gemini) — performs server-side image generation when that feature is enabled.
Amazon Web Services — hosts the platform and stores media assets.
Cloudflare — provides edge delivery, DNS, and request security for public properties and supported infrastructure workflows.
Microsoft (Microsoft 365) — provides the team’s email mailboxes and calendar invitations, including connected Microsoft calendar workflows.
Communications providers — Twilio (telephony), ElevenLabs (voice synthesis), ClickSend (SMS/MMS), and Mailjet (email and public contact-form delivery).

A current, itemized sub-processor list is available to enterprise customers on request via Contact.

Optional local collaboration records

If you enable Codex collaboration, the approved Windows helper stores scoped message text, project and conversation bindings, approved scope, and delivery receipts under %LOCALAPPDATA%\Loam\Collaboration. This local SQLite history is not application-encrypted and does not store provider credentials. The installer restricts directory access to your Windows user and SYSTEM. Task content is supplied to the selected coding agent and its configured provider. Disconnecting retains history; hosted account deletion does not remove it. The helper’s uninstall option can explicitly remove local history.

6. How long we keep it

Session content, team memory, and project context — kept until you delete them or delete your account.
Call audio recordings — cleared automatically about 30 days after the call; the status becomes “expired.”
Full call records (including transcripts) — do not currently auto-expire; removed when you delete your account or when an authorized Loam administrator runs the cleanup control.
Produced audio (such as Morning Read and Studio audio) — stored as server files. Account deletion removes the related database records; file removal requires Loam-operated cleanup.
Reception work orders — deleted when you delete your account, together with intake and backlog records and the report and attachment files stored under the account. Copies already sent to an email inbox or saved into your own repository remain there.
Photos sent during a call — the stored photos and their analysis records are removed after 90 days, or with account deletion. Spent or expired upload-link records are cleared after 30 days.
Public contact submissions — delivered to Loam’s contact mailbox through Mailjet. No product-controlled automatic retention schedule is defined for mailbox copies today; contact us to request deletion.
Backups. Deletion removes data from our live systems immediately, but disaster-recovery snapshots may still contain deleted data until those snapshots expire. Current backup retention window: 7 days.

7. Your choices & rights

Database deletion is in your hands. From your account you can delete a single team member's memory, an individual project, or the live database records tied to your account — confirmed behind a phone code where required. The account transaction removes memories, sessions, projects, settings, stored credentials, and the user record. Server-stored generated audio requires Loam-operated file cleanup; infrastructure teardown follows the applicable plan or order.

Calls, texts, and quiet hours. Agreement to calls and texts is recorded with a timestamp and emailed to you with links to the Terms and this policy. Declining turns outbound calls and texts off. Quiet hours are on by default and only you can change that setting. They hold ordinary calls and texts outside 8 a.m.–9 p.m. in your time zone; a callback or message you explicitly requested can honor that request outside the window. A call the team marks urgent — something went wrong with your work, or a password or key may have leaked — can also come through; a text never does. Turning quiet hours off allows any hour while leaving the consent requirement in place.

Honest limits. A one-click data export isn't built yet. If you need a copy of your data, contact us and we'll help.

Depending on where you live, you may have additional rights — to access, correct, port, or delete your personal data, or to object to certain processing. To make a request, contact us using the details in the Contact section below; we'll verify your identity and respond within the timeframe the applicable law requires.

8. Where your data lives

Loam is hosted on Amazon Web Services in the United States. If you access Loam from outside the United States, your information will be processed in the U.S. and in the regions where our service providers operate.

9. Children

Loam is a professional development tool and is not directed to children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us information, contact us and we'll delete it.

10. Changes to this policy

If we change how we handle your data, we'll update this page and the “Last updated” date above. Material changes will be communicated through the platform.

11. Contact us

Questions about this policy, or a request about your data? Email info@loam.team, use the Contact page, or write to Toast2 IT, LLC, 4121 Shadow Creek Circle, Oviedo, Florida 32765, United States. For the technical detail behind everything here, see Security.