Terms
Last updated October 8, 2026.
These terms are between Fulcrum, the service at fulcrumrevenue.com, and the organization that accepts them (“you”). People invited into the workspace, and people who open it from the connected Close organization, are bound by these terms. You accept them by signing in, connecting Close or a database, or using the service. We may post a revised version on this page. Questions go to danny@fulcrumrevenue.com.
What Fulcrum is
Fulcrum connects Close to your Postgres and keeps a typed replica there, in a schema named fulcrum. The console is where you connect and watch sync.
Two places, on purpose. The control plane is ours, on Railway: the workspace, users, encrypted credentials, sync jobs, and a short-lived webhook queue. The data plane is yours: fulcrum.close_* and the related tables in your database. Fulcrum does not keep that copy as its own warehouse. Close stays the CRM. Fulcrum is the pipe and the console.
Access
During the term we grant you a non-exclusive, non-transferable right for your users to use the console and the sync for your own internal business.
A Close admin connects the organization once. An invited admin manages that connection. A person already in the connected Close organization can open Fulcrum and receive a member seat on first sign-in. That sign-in identifies the person. It is a separate Close authorization from the grant used for sync.
You authorize us to call Close with the grant you connect, to receive Close webhooks, and to connect to the database URL you provide. We create and change objects only in the fulcrum schema, so the replica can stay current.
Your responsibilities
- Connect only a Close organization and a database you are allowed to use, and follow those vendors’ terms.
- Keep admin access, the database URL, and user passwords confidential.
- Prefer a database role limited to the
fulcrumschema. - Make sure personal data in Close is collected and shared lawfully, including notice to the people in that CRM.
You are the controller of source data and of the replica in your database. We process that data to provide the sync. See the privacy policy.
Restrictions
- Do not share another workspace’s access, or point one workspace’s Close organization at another workspace’s database.
- Do not probe, scan, or disrupt the service, or bypass sign-in or credential controls.
- Do not resell the service or use it to build a competing sync product from our software.
- Do not use the database credential for anything other than the
fulcrumschema.
How sync works
We apply Close events and exports into your fulcrum tables. Delivery depends on Close, your database, and the network. We retry a failed apply. We do not promise zero lag, a complete history Close never sent, or that a delete in Close is reconstructed if it happened before we subscribed.
We may pause a connection if it threatens the service, your database, or Close’s rate limits, and we will tell a workspace admin when we do.
Ownership
We own the Fulcrum software, the console, and the control-plane schema. You own your Close data, your database, and the rows we write into fulcrum. You may drop that schema. We do not claim a license to use your CRM contents to train models or to market to the people in them.
Sync metadata that does not contain source record contents, such as job status and row counts, is ours to operate and improve the service.
Credentials and security
Connector secrets and OAuth refresh tokens are encrypted at rest. We do not show them back in full. We keep commercially reasonable safeguards for the control plane. You keep reasonable safeguards for your users, your database, and your Close organization.
Webhook payloads sit in the control-plane queue only long enough to acknowledge and apply them. We aim to keep that queue about 30 days, including a failure waiting on retry. The queue can briefly hold email bodies, call transcripts, and similar content. It is not the replica.
A workspace admin can disconnect Close. That tells Close to drop the install grant, deletes the stored credential, and stops new sync. The warehouse, and the replica already in it, stay.
Fees
The service does not charge a subscription fee in the product. Either party may stop, as below.
Term and ending it
The agreement starts when you accept and continues until either party ends it.
When it ends we stop syncing, delete the stored credentials for that workspace, and disable sign-in for that workspace. Queued payloads for that workspace are deleted with it. You are responsible for dropping the fulcrum schema if you want the replica gone. We do not retain a copy of it.
Confidentiality
Each party protects the other’s non-public information, including credentials and source payloads in the queue, with at least reasonable care, uses it only to perform this agreement, and shares it only with people who need it and are bound to protect it. This does not cover information that is public through no fault of the receiver, already lawfully held, independently developed, or required by law.
Personal data
We are the processor of source data in transit. You are the controller. We are the controller of account data: user name, email, and sign-in. A separate data-processing addendum is available on request before another organization’s Close data is connected.
Disclaimers
The service is provided as is. We disclaim implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement, to the extent the law allows. We do not warrant that sync will be uninterrupted or error-free. Close, your database host, and the network can fail. We are not liable for the contents of your source, or for what your own tools do with the replica after we write it.
Liability
Neither party is liable for indirect, incidental, special, consequential, or lost-profit damages, or for lost data, except a failure to delete control-plane credentials and queue data when the agreement ends. These limits do not apply to a party’s fraud, or to misuse of the other party’s credentials. Some laws do not allow these limits. They apply only to the extent they are allowed.
General
These terms and the privacy policy are the whole agreement. A purchase order does not add terms. Email to a workspace admin, and to danny@fulcrumrevenue.com, is sufficient notice. Neither party is the other’s agent. You may not assign this agreement without our consent. We may assign it to a successor of the business. A party is excused for delays caused by events outside its reasonable control. If a provision is unenforceable, the rest remains.