Org Loom

Terms of Service

By signing up or signing in, you agree to these terms.

Effective date: 2026-07-23

1. Overview

Org Loom is a web application for managing Salesforce data: loading records, editing them on a visual canvas, generating sample data, and uploading changes back to Salesforce. You connect your own Salesforce org via OAuth and Org Loom acts on the data through that connection. You are the data controller for everything in your Salesforce org; Org Loom is a data processor.

2. Eligibility and accounts

  • You may only use the service if you are of legal age to enter into these terms in your jurisdiction.
  • You are responsible for your account. Keep your sign-in email secure and do not share access with anyone who should not have it.
  • You are responsible for the Salesforce credentials you authorize. You can revoke Org Loom's OAuth access at any time from your workspace settings.

3. License and intellectual property

  • We grant you a limited, non-exclusive, non-transferable right to access and use the hosted service at orgloom.com for the term of your subscription, subject to these terms.
  • Org Loom retains all rights in the service, its software, and its branding, except as granted by the source-available license described in Section 9.
  • The data you load from Salesforce, edit on the canvas, and upload back belongs to you or to the entity that owns the Salesforce org. Org Loom claims no ownership of it, and we do not use it to train AI models.
  • If you send us feedback or suggestions, we may use them without obligation to you.

4. Acceptable use

You agree not to:

  • Use Org Loom to violate any law, regulation, or third-party right, including your own Salesforce contract.
  • Use Org Loom against a Salesforce org you are not authorized to act on.
  • Attempt to circumvent capability gates, rate limits, Activity History, billing checks, or security features. Org Loom records workspace Activity History (sign-ins, org connections, uploads), described in the Privacy Policy. Salesforce data-activity delivery is best-effort and is not a compliance-grade audit control.
  • Interfere with the service: denial-of-service attempts, scraping beyond reasonable use, or probing for vulnerabilities without an authorized engagement.
  • Use the AI or scripting features to evade Salesforce governor limits or any other applicable cap.
  • Use Org Loom to send unsolicited messages, host malware, or harm anyone.

Security research is welcome. Email security@orgloom.com before testing anything intrusive.

5. Restricted data

Org Loom is not a HIPAA Business Associate, is not PCI DSS certified, and is not designed for classified or export-controlled data. You agree not to use Org Loom to upload, store, view, or transmit:

  • Protected Health Information (PHI) as defined under HIPAA, including data subject to a Business Associate Agreement.
  • Cardholder data subject to PCI DSS (full PANs, CVVs, track data).
  • Government-classified, export-controlled, or ITAR/EAR-regulated data.
  • Personal information of children under 13, or under the age of digital consent in your jurisdiction, that would subject Org Loom to COPPA or equivalent regulation.

Org Loom authenticates to Salesforce as the user who signs in, so its access mirrors that user's Salesforce permissions: it can view and modify only the records and fields your Salesforce user can. You are responsible for keeping the categories above out of the records and fields you push into Org Loom. Org Loom does not store your Salesforce records, so remediation happens on your side: if we learn that restricted data is being processed through the service, we may require you to stop and, where necessary, suspend the workspace pending remediation.

Customers with regulated data needs can contact sales@orgloom.com to discuss roadmap and contractual options.

6. Workspaces, members, and admins

  • Each account starts with a personal workspace. Team workspaces are paid surfaces owned by an admin; members join by invite code.
  • Workspace admins control plan settings, feature flags, member roles, and approvals. The workspace plan governs which capabilities are available.
  • Joining a workspace does not share your Salesforce connections with other members. Connections are per-account; the workspace governs policy, not credentials.
  • Each person who accesses Salesforce data through Org Loom must use their own appropriately licensed and authorized Salesforce user. You may not share Salesforce credentials or use Org Loom to circumvent Salesforce licensing or contractual usage limits.
  • Any free Viewer, Contributor, or collaboration access refers only to Org Loom fees. It does not include, grant, or replace a Salesforce license. You are responsible for obtaining the Salesforce licenses appropriate for each user's access and activities.
  • Workspace admins can see workspace Activity History: who did what, when, and against which Salesforce org.

7. Plans and billing

  • New workspaces start with a 14-day Pro trial that begins on first Salesforce connect. When the trial ends, the workspace sits in a read-only Inactive state until you subscribe. Pro and Team are paid subscriptions billed through Stripe at the caps published on the pricing page.
  • Subscriptions are billed monthly. Cancel any time from the Billing tab; access continues to the end of the paid period, then the workspace becomes Inactive.
  • Refunds are not offered for partial periods unless required by law.
  • If a payment fails, Stripe retries on its standard dunning schedule. The workspace stays active during the grace period; if payment is not resolved, it is downgraded to Inactive.
  • We will give registered users at least 30 days' notice before implementing changes to capability gates or pricing that would meaningfully impact services.

8. AI and MCP features

  • Pro and Team plans include AI-powered data generation and MCP token issuance for AI clients. The MCP token is a bearer credential: treat it like a password and rotate it if compromised.
  • Some AI features have monthly token caps tied to your plan.
  • AI output is generated, not authored, and may be incorrect. Always review AI-generated records before uploading them to your org.

9. Source-available code

Org Loom's canvas core is source-available at github.com/getorgloom/orgloom-canvas. You may read, study, fork, and self-host the code subject to the license in the repository. These terms govern the hosted service at orgloom.com; a self-hosted instance is governed solely by the repository license.

10. Availability and changes

  • We aim for high availability but do not offer a uptime SLA unless otherwise stated in a separate agreement.
  • We may update, change, or remove features. For breaking changes to paid features we give 30 days' notice.
  • Maintenance may briefly interrupt service. Where possible we schedule it outside business hours for the largest set of users.

11. Termination

  • You can close your account any time from your workspace settings.
  • We may suspend or terminate accounts that violate Section 4 or Section 5, repeatedly fail payment, or pose a security risk to the service or other customers. We will usually warn you first unless an immediate suspension is needed.
  • If we terminate for cause, we refund unused prepaid time on a pro-rata basis.

12. Disclaimers

Org Loom is provided "as is." To the maximum extent allowed by law, we disclaim implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

13. Limitation of liability

Our total liability arising out of or related to Org Loom is limited to the greater of (a) the fees you paid us in the 12 months preceding the claim, or (b) US $100. We are not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data, except where this limitation is not allowed by law.

14. Indemnification

You agree to defend and hold Org Loom harmless from third-party claims arising from your use of the service in violation of these terms or applicable law.

15. Governing law and disputes

These terms are governed by the laws of the State of Arizona, USA, without regard to conflict-of-laws rules. Disputes that cannot be resolved by contacting legal@orgloom.com will be resolved in the state or federal courts located in Maricopa County, Arizona.

16. Changes to these terms

We will email registered users before any material change takes effect and update the effective date above. Continued use after the effective date constitutes acceptance.

17. Contact

Terms: legal@orgloom.com. Security: security@orgloom.com. Privacy: privacy@orgloom.com.

See also: Privacy Policy · Trust & Security.