Privacy
Last updated October 8, 2026.
Fulcrum runs the console at app.fulcrumrevenue.com and this site. This policy covers both. It does not cover Close, or the database host you choose. Those have their own terms. Questions go to danny@fulcrumrevenue.com.
Two kinds of data
Account data is what we need to run a workspace: name, email, role, and how you signed in. We decide how that is handled. It lives on our control plane, hosted on Railway.
Source data is the Close records that pass through a sync: contacts, emails, calls, transcripts, notes. You decide how that is handled. We process it only to write and keep the replica in your Postgres, schema fulcrum. A short queue on our side holds a delivery until it is applied. We do not keep your CRM as our own warehouse.
Account data we collect
- Name and work email. An invited admin also has a password. Close sign-in does not use a password.
- Role and workspace. An invited admin can manage the connection. A person already in that Close organization can receive a member seat on first Close sign-in.
- From Close sign-in: the Close user id and email, and an encrypted refresh token so we can recognize that person again. That token is for sign-in. It is not the grant used to read Close for sync.
- From Connect with Close: the organization id, the person who clicked Allow, and an encrypted refresh token. Sync, export, and webhooks use that grant.
- The database host name, and the database URL encrypted before it is stored. We cannot show a stored secret back in full.
- On this site, the interest form stores name, email, and any company, phone, or message you add, so we can reply. The form does not send mail by itself.
We do not ask for payment card numbers. We do not build marketing profiles, and we do not sell personal information.
Source data we process
When a connection runs, Close payloads pass through our workers so we can write rows into your database. Those payloads can include names, emails, phone numbers, message bodies, and call transcripts, because that is what Close sends.
We use them to apply and retry the sync, to show a sync error to a workspace admin, and to protect the service. If you turn a lever on, Fulcrum reads the replica in your database for that job. Call scoring reads the transcript already stored there and can write the score back to Close. We do not send that transcript to a separate model provider.
We do not use source data to market to the people in your Close organization, and we do not use it to train general models. You are responsible for having a lawful basis to move that data, and for the notice those people receive.
Cookies
The console uses a session cookie so you stay signed in. It lasts 14 days, and it is not an advertising cookie. Close sign-in also sets a cookie that remembers that Close user. We do not use marketing pixels or cross-site ad profiles. We do not respond to browser Do Not Track signals. The session cookie is required to use the console.
Who we share with
- Your database, which you choose. The replica is written there.
- Close, with the grant you authorized.
- Slack, if you connect it, for the alerts you turn on.
- Railway, which hosts the app and the control-plane database.
- A successor of this business, under the same limits.
- Law and safety, if required by law or to prevent fraud, abuse, or a security incident.
Service providers may process data only to perform their piece of the service.
Security
Connector secrets and refresh tokens are encrypted before they are stored. Access to production is limited to the people who operate the service. No method of transmission or storage is perfectly secure.
How long we keep it
- Account and connector records last for the life of the workspace.
- Encrypted credentials last until you disconnect that connection, or the workspace ends.
- The webhook queue is not the replica. We aim to keep a delivery about 30 days, including a failure waiting on retry.
- The replica in your database is yours. Disconnecting Close does not delete it. Drop the
fulcrumschema if you want it gone.
Your choices
You can ask us to correct an account name or email, or to delete a user. A workspace admin can disconnect Close, which tells Close to drop the install grant, deletes the stored credential, and stops new sync.
People in the CRM should contact the customer, not Fulcrum, for access, correction, or deletion of source records. Those records live in the customer’s database. If a copy is still only in the queue, we will delete it on a verified request from the customer, or when the queue expires.
We do not use account data for a mailing list. Depending on where you live, you may have rights to access, correct, delete, or export personal information, or to appeal a denial. Email danny@fulcrumrevenue.com. We will verify the request. We will not treat you differently for making one. If we deny it, you may appeal by replying to that denial.
Children
The service is for businesses. We do not knowingly create accounts for anyone under 16. A source system can still contain data about minors if a customer put it there. Do not connect a source for the purpose of processing children’s data with us.
International
We are based in the United States. Account data and the queue are processed in the United States on Railway. If you connect from elsewhere, you send data to the United States to use the service.
Changes
We will post changes on this page. Continued use after the update means the new policy applies to account data. Source data stays under the processor role described in the terms.