Legal
Privacy Policy
This policy explains what information ContactRoll holds, why, who else handles it, how long we keep it, and the choices you have. It covers this website (contactroll.com), ContactRoll’s app (app.contactroll.com) and the help centers we host for our customers.
ContactRoll is run by Steven Foster, a sole proprietor doing business as ContactRoll (“ContactRoll”, “we”, “us”). For anything about privacy, write to privacy@contactroll.com.
The short version
- This website sets no cookies, runs no analytics and loads nothing from another site.
- In the app, the information our customers put in belongs to them. We use it only to run ContactRoll for them.
- We do not sell personal information, use it for advertising, or use it to train artificial intelligence models.
- An organization can export its data while its account is open and for 30 days after closure. We delete data under our control, including files and backup copies, within a further 30 days. This does not delete copies held by third-party services or copies previously exported or sent by the customer to another service.
1. Two kinds of information, and our role in each
Information about our customers. When a business signs up, we hold information about the organization and the people who use ContactRoll for it: their names, email addresses and billing details. For this information we decide how it is used, and we are its controller.
Information our customers put into ContactRoll. Our customers use ContactRoll to work with their own customers and contacts, so the app holds people’s names, email addresses, phone numbers, messages, notes and files. For this information our customer is the controller and we are their processor: we handle it only on their instructions, to provide the service. If you are one of our customer’s contacts and want to ask about your information, please contact that business first (section 13).
2. This website
Every page on contactroll.com is a static file. It sets no cookies, runs no analytics, has no chat widget or tracking pixel, and loads no fonts or scripts from anyone else. It runs one small script of our own, which sends nothing anywhere: it copies our email address when you press Copy, and runs the free tools, which work in your browser. A file you give the CSV contact cleaner is read on your computer and never leaves it.
- Videos. A video on this site is a picture of ours until you press play. Then your browser loads the player from YouTube’s privacy-enhanced address (youtube-nocookie.com), and YouTube receives your request under its own privacy policy.
- Hosting. Cloudflare serves this website and the app. Like any web host, it keeps request logs, which include your network (IP) address.
- Emailing us. If you write to hello@contactroll.com or privacy@contactroll.com, we have your message and your address, and we use them only to answer you. Writing to us does not put you on any mailing list. Mail to those addresses reaches us through Cloudflare, which forwards it to the inbox we read. To have your message deleted, ask at the same address.
3. What we hold about our customers and their team members
- Account information: the organization’s name, each member’s email address, name and role, their notification choices, and invitations (the address invited, the role offered and when the invitation expires).
- Sign-in: passwords and sign-in sessions are held by our infrastructure provider’s authentication service. We cannot read passwords. If you turn on two-factor sign-in, the code that sets it up is held the same way.
- Billing: the plan, its status, the billing contact and invoice history. Payments are handled by Stripe. We never receive or store your full card number.
- Use of the service: the date your organization was last used (recorded at most once a day, without saying who or what), records of sign-ins and of important changes made in your organization (its audit log), and reports of errors in the app (where an error happened and in which version, never the content of your data).
- Security checks: on the app’s sign-in and sign-up pages, Cloudflare Turnstile may check that you are a person and not a program. Cloudflare receives information such as your IP address and browser details for that check. We keep none of it.
- Your messages to us: if you contact us for support, we keep the conversation so we can help you.
The app keeps your sign-in session in your browser’s storage. It uses no advertising or analytics cookies.
4. What our customers put into ContactRoll
What follows is held for our customer, and only our customer’s own team can see it.
- Contacts and companies: names, email addresses, phone numbers, and the details and notes a team records about them.
- Support conversations: every email in a case, in both directions, files people attach, internal notes, and questions sent through a help center the customer publishes.
- Calls: records of calls (which number, when, how long and how it ended) and the team’s notes about them. Where a customer switches recording on, the recording stays in the customer’s own Twilio account; we keep only the fact that it exists and who listened to it. Every recorded call is announced before it connects. Where a customer also switches transcripts on, the transcript is made by the customer’s Twilio account and we keep a copy of the text so the team can read and search it.
- Marketing email: a record of each person’s consent (what they did, when, and the evidence), unsubscribes, bounces and complaints, who each message was sent to, which version of a tested message they were sent, and the links they followed. We do not track whether an email was opened. A customer can switch link tracking off, and a person can ask for the links they followed to be forgotten while staying on the list. We never keep the network address of a person who follows a link, only a scrambled form of it used to stop abuse.
- Sign-up forms: the name, email address and company a person enters, the words they agreed to, and, as evidence of their consent, when and from which network address they signed up and confirmed. A sign-up never confirmed is deleted after seven days.
- Events and billing from a customer’s own systems: a customer’s own app may tell ContactRoll what a person did (for example, started a trial), limited to fixed fields with no free text. A customer may connect its own Stripe account so its team can see a person’s plan and payments; this is read live and not stored, apart from the person’s Stripe customer ID and the events Stripe reports. No card number is ever stored.
- Bug reports: a customer may report bugs from a case to its own issue tracker. Before a report is sent, ContactRoll checks it for the person’s email address, name, company name and words they wrote, and refuses to send it if they are there.
- Email and meetings from a member’s Microsoft account, accounting figures from QuickBooks, where the customer uses those features (sections 8 and 10).
Some of these features are only available on some plans.
5. How we use information
We use information to:
- provide ContactRoll, as each customer has set it up;
- keep accounts and data secure, and prevent spam, fraud and abuse;
- bill for paid plans;
- send service emails, such as sign-in links, invitations, notifications a member has chosen, and messages about billing, trials and the account (these are not marketing);
- answer questions and requests;
- meet our legal obligations.
We use account information and service-usage information to operate, secure, maintain, analyze, and improve ContactRoll. We may also use information that has been aggregated or de-identified so that it does not identify an organization or individual. We do not use customer content, including contacts, messages, cases, notes, or files, for product development, advertising, or artificial intelligence model training. We may process customer content as necessary to provide features the customer enables, including AI features, and to secure, operate, or support ContactRoll.
We do not sell personal information or share it for advertising, we do not use it for advertising, and we do not use our customers’ data to train any artificial intelligence model. Nobody at ContactRoll looks at an organization’s data except to run or fix the service, to investigate abuse or a security problem, when the customer asks us to, or when the law requires it.
6. Who else handles information
ContactRoll subprocessors. Subprocessors are service providers that ContactRoll engages to process customer personal data on ContactRoll’s behalf. Our current subprocessors are:
| Provider | What it does for ContactRoll | Where |
|---|---|---|
| Supabase (on Amazon Web Services) | Hosts the database, attached files and sign-in | United States (Northern Virginia) |
| Cloudflare | Hosts this website and the app, forwards our email addresses and runs sign-in security checks | Global network |
| Resend (on Amazon Web Services) | Sends and receives email, and keeps its own copy of each message for up to 30 days | United States (Northern Virginia) |
| Stripe | Takes payment for ContactRoll’s paid plans | United States |
| Anthropic, PBC | Writes the AI assistant’s answers, for an organization that has switched the assistant on (section 9) | United States |
We maintain a current list of our subprocessors in this policy and the DPA. We will update the list when our subprocessors change and provide notice where required by applicable law.
Customer-connected services. A service that a customer connects using its own account and under its own agreement is a customer-connected service, not a ContactRoll subprocessor for that processing. The customer directs any information sent to that service, and its use of it is governed by that service’s own terms and privacy policy. These include Twilio (calls, recordings and transcripts, in the customer’s own Twilio account), Google (YouTube publishing, and calendar and email sending, for members who connect a Google account: section 7), Microsoft (sign-in, and Outlook mail and calendar for members who connect them: section 8), Intuit’s QuickBooks Online (section 10), services reached through the customer’s API keys, webhooks or Zapier (section 10), Google’s Gemini, HeyGen, the customer’s own Stripe account and its own GitHub repository. ContactRoll sends each only what a team member asks it to make, publish, look up or send.
We may also disclose information if the law requires it, to protect people’s safety, or to someone who acquires ContactRoll, who will be bound by this policy. We will tell our customers by email if ContactRoll is sold.
7. Information from your Google account
ContactRoll’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. The use of information received from Google Workspace scopes will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
In practice:
- ContactRoll asks Google only for what a feature you switch on needs: to publish videos to your YouTube channel and read their view counts, and, where offered, to add events to your calendar and send the emails you write.
- ContactRoll never reads your email. Of your calendar, it keeps only the ID and link of each event it adds.
- No person at ContactRoll reads information from your Google account, unless you ask us to for support, it is needed for security, or the law requires it.
- It is never used for advertising, never sold, and never used to create, train or improve any artificial intelligence model.
- When you disconnect your Google account, ContactRoll deletes its access tokens and revokes them at Google.
8. Information from your Microsoft account
Sign in with Microsoft. If you sign in with a Microsoft account, ContactRoll asks Microsoft only to sign you in and for your email address. An account that signs in with Microsoft can accept an invitation to an organization, or ask to join one, only when Microsoft confirms that its email address is verified.
Outlook mail and calendar. Where an organization offers it, a member may connect their own Microsoft 365 or Outlook account. ContactRoll then asks Microsoft for permission to read basic details of the member’s mail (not what a message says), to read and write their calendar, and to read their contacts.
- Mail. For each message in the member’s Inbox and Sent Items, from 30 days before connecting onward, ContactRoll reads its subject, sender, recipients, times and a link to it in Outlook. It never asks for a message’s text or its attachments. It saves a message only when it is to or from a contact in the organization, and then saves its subject, which way it went, when, and the link, on that contact. For any other message it saves nothing.
- Calendar. ContactRoll reads the member’s events from 30 days back to 180 days ahead. Microsoft sends each whole event, including its description. For an event with a contact, ContactRoll saves only its subject, its time, whether it is online or canceled, and its link, never its description; for any other event it saves nothing. When a member books a meeting from ContactRoll, ContactRoll adds the event to their calendar with the details they give.
- Contacts. ContactRoll reads the member’s Outlook contacts only when the member chooses to import them.
- Who sees it. What is saved appears on the contact’s record, and every member of the organization who can see that contact can see it. Where the organization uses the AI assistant, a saved subject can be part of what a summary of that contact sends (section 9).
- How long. It is kept as part of the contact’s history until the contact is deleted or the organization’s data is deleted (section 12). It stays when the member disconnects or leaves the organization.
- Disconnecting. ContactRoll deletes the access Microsoft gave it and stops reading. It does not ask Microsoft to revoke that access; to remove it at Microsoft, use the app permissions page of your Microsoft account.
- It is never used for advertising and never sold.
9. The AI assistant
On the Plus plan, a member with permission (by default an Owner or Administrator) can switch on an AI assistant for their organization. It is off until they do. When it is on, a member can ask it, one request at a time, to:
- Summarize a contact, company, deal or case. ContactRoll sends that record’s details and custom fields and its recent history (up to 60 entries), which can include notes, internal notes, replies, tasks and call notes.
- Draft a reply on a case. ContactRoll sends the case, as above, and up to five of the organization’s help articles.
- Ask a question on the Reports page. ContactRoll sends the question as typed and the names of the record types and fields that member may use, with their listed choices and the organization’s pipeline, stage, product and team names. It sends no records. Whatever a member types into the question is sent, including any personal information they type.
ContactRoll sends only what the member asking can see, to Anthropic, which writes the answer as our subprocessor (section 6). The answer is shown to that member. A draft goes into the reply box and is not sent unless a member sends it. ContactRoll keeps no copy of the request or the answer. It keeps a record of each use (who asked, when, about which record, its size and its cost) and an entry in the organization’s audit log.
10. QuickBooks, API keys, webhooks and Zapier
QuickBooks Online. On the Plus plan, a member with permission (by default an Owner or Administrator) may connect the organization’s QuickBooks company. ContactRoll asks Intuit only for access to its accounting data.
- To suggest which QuickBooks customer matches a company, ContactRoll searches QuickBooks by up to three email addresses of that company’s contacts, the company’s name and its web domain.
- For a company linked to a QuickBooks customer, ContactRoll reads and saves the customer’s name and email address, the number and total of open and of overdue invoices, and the date and amount of the latest payment, and reads them again to keep them current. Anyone in the organization who can see that company can see them.
- ContactRoll creates an invoice in QuickBooks only when a member asks for one on a won deal, at once, with the deal’s name and amount. It creates a customer there only when a member asks, with the company’s name.
- Disconnecting asks Intuit to revoke ContactRoll’s access, and deletes from ContactRoll the connection, its links, the saved figures and the record of invoices made. Customers and invoices created in QuickBooks stay in QuickBooks.
API keys, webhooks and Zapier. An organization may create API keys, set up webhooks or connect Zapier to send its data to services it chooses. An API key can read and change only what the member who made it may see and do. A webhook or a Zapier connection sends the details of a record that changed, which can include a person’s name and email address and a case’s subject and description, to the address the organization chose.
11. Where information is kept
ContactRoll’s database and files are in the United States. ContactRoll is designed for US-based business customers. Cloudflare’s network may handle information outside the United States. ContactRoll does not currently provide EU or UK international data transfer terms as part of its standard service.
12. How long we keep information
- While an organization’s account is open, we keep its data for as long as the account exists, because a support history is what the product is for. A customer can delete contacts, cases and files at any time, and deleting a contact deletes their cases, messages, notes, calls and files with them. A record of an unsubscribe is kept for as long as the organization exists, so that importing a person again cannot undo it.
- When an account is closed, access stops at once. The account can be reopened, and everything exported, for 30 days. After that, data under our control is deleted within a further 30 days, including files and backup copies. All that remains is a record that an organization was deleted, with no name or content.
- Unpaid accounts become read-only after notice, and are closed after 30 days read-only, then deleted as above.
- Free plan accounts are never closed or deleted for being unused; they become read-only after 90 days without use.
- Copies we do not control: Resend keeps its own copy of each email for up to 30 days. Recordings and transcripts in a customer’s own Twilio account stay there until the customer deletes them; the customer’s export lists each one. Records created in a connected service, such as events in a member’s calendar or customers and invoices in QuickBooks, stay there. Anything a customer exported or sent to a service it connected is outside our deletion.
- Information about the website: we keep emails to hello@ and privacy@ for as long as needed to answer them and keep a record of the answer, unless you ask us to delete them.
13. Your choices and requests
- Export: an organization’s Owners and Administrators can download everything it holds, and everything it holds about one person, from within the app.
- Correction and deletion: team members can correct or delete what they have entered. An Owner can close the account.
- Unsubscribing: every marketing email sent through ContactRoll has a one-click unsubscribe link.
- California residents: we do not sell or share personal information, as those words are defined in California law, and we do not use sensitive personal information to infer anything about you.
Information about your ContactRoll account. ContactRoll acts as the controller of account, billing, and service information about its customers and their team members. Requests about this information should be sent to privacy@contactroll.com. We will respond as required by applicable law.
Information in a customer’s CRM. The business using ContactRoll decides how it uses information about its customers and contacts. Requests about that information should be sent to that business. If we receive such a request, we will forward it to the business and provide reasonable assistance as required by applicable law.
14. Security
We protect information with measures including:
- each organization’s data kept apart by the database itself, and checked by automated tests on every change;
- private file storage, with download links that expire after 60 seconds;
- encryption of data in transit, and of stored access keys for services our customers connect;
- two-factor sign-in, and roles that limit what each member can see and do;
- email authenticated with SPF, DKIM and DMARC.
No system is perfectly secure. If we learn of a security breach that affects personal information, we will tell the affected customers by email without undue delay, and notify authorities where the law requires.
15. Children
ContactRoll is a business service and is not directed to children. Account holders must be at least 18 years old. Customers are responsible for ensuring that information about minors they submit to or collect through ContactRoll is collected and used lawfully, including providing any notices or obtaining any consents required by law.
16. Changes to this policy
We post changes to this policy here, and the date at the top shows when it was last updated. For a material change, we will also tell our customers’ Owners by email, where appropriate or required by law.
17. Contact
Write to privacy@contactroll.com about privacy and your information, and to hello@contactroll.com about anything else. We do not take requests by post.