Access to the Rocket Driver CRM may be made available to a Client as an optional part of a broader Rocket Driver service relationship — including the Rocket Driver White Label Partnership — in some cases without a separate charge for the CRM, or as otherwise agreed. Use of the Rocket Driver CRM is optional; a Client is not required to use it, and choosing not to use it does not affect the remainder of the Client’s relationship with Rocket Driver.

These CRM Service Terms apply in addition to the Rocket Driver Terms of Service when an authorized representative of a Client — for the Rocket Driver CRM as currently offered, the Client’s organization owner — activates the Rocket Driver CRM on the Client’s behalf through the electronic activation acceptance presented in the CRM, or when the Client otherwise elects to access or use the Rocket Driver CRM. Once the Client’s organization has been activated, individuals who use the Rocket Driver CRM under the Client’s organization do so under the Client’s Agreement and are not asked to accept these CRM Service Terms separately. No separate CRM purchase, order, or signature is required under the current model. Capitalized terms have the meanings given in the Terms of Service. Where these CRM Service Terms conflict with the Terms of Service, these CRM Service Terms control for the Rocket Driver CRM. Where the Rocket Driver CRM Data Processing Agreement conflicts with either, the Data Processing Agreement controls with respect to the processing of personal information.

1. Access and provisioning

Rocket Driver provisions Rocket Driver CRM organizations for Clients. Public self-registration is not available: Rocket Driver creates your organization and your initial organization owner account, and you administer users from there.

Access to the Rocket Driver CRM is an optional part of your Rocket Driver service relationship. It is not a separate purchase, and you are not required to use it. If your organization does not use the Rocket Driver CRM, nothing in these CRM Service Terms is triggered and no acceptance is asked of you.

Before your organization uses the Rocket Driver CRM with real information about people, your organization owner completes a single activation acceptance inside the Rocket Driver CRM, at which these CRM Service Terms and the Rocket Driver CRM Data Processing Agreement are presented and linked. That acceptance is given once, for your organization as a whole, and it is what brings these CRM Service Terms into your Agreement. Until it is given, other users of your organization are told that your organization owner must activate the Rocket Driver CRM first.

2. Your organization and your users

You administer your own organization: you invite users, assign roles, and remove access. Section 34A of the Terms of Service sets out your responsibilities for doing so. Roles available in the Rocket Driver CRM determine what each user can see and do; you are responsible for the roles you assign.

Your organization’s activation acceptance covers every user you authorize. Individual users — managers, sales representatives, other staff, and users of your own clients — are not asked to accept these CRM Service Terms, are not asked to accept them at first login, and cannot accept them on your organization’s behalf. The authority to bind your organization rests with your organization owner.

If you enable access for your own clients, those client users receive access scoped to the client account or accounts you assign them, and you are responsible for their access as if they were your own users.

3. Multi-factor authentication

Rocket Driver requires authenticator-application multi-factor authentication for organization owner accounts and for Rocket Driver administrative accounts. You must complete enrollment to obtain full access, and you must keep your authenticator device and your recovery codes secure. Recovery codes are stored hashed, and each recovery code can be used once.

No account subject to this requirement can sign in without completing multi-factor authentication. If a user loses access to their authenticator, an authorized Rocket Driver administrator can reset that user’s multi-factor enrollment — for example, where the authenticator device has been lost. A reset clears that user’s existing enrollment and recovery codes and ends that user’s active sessions, and the user must complete a new enrollment before signing in again. A reset does not disclose existing authentication secrets and does not allow anyone to sign in without multi-factor authentication. Ask for a reset at team@rocketdriver.com.

4. Data you may not store in the Rocket Driver CRM

The Rocket Driver CRM is a general business tool. It is not designed, configured, or offered for the storage of information subject to special legal protection. You must not store in the Rocket Driver CRM, and must not permit your users or your clients to store in it:

1. protected health information or other health, medical, or clinical information;
2. biometric or genetic information;
3. government-issued identification numbers, including Social Security numbers, driver’s license numbers, and passport numbers;
4. financial account numbers, payment card numbers, or credentials to financial accounts;
5. precise geolocation information;
6. information about children, or information collected from children;
7. information revealing racial or ethnic origin, religious or philosophical beliefs, political opinions, union membership, sexual orientation or sex life, criminal history, or immigration status;
8. information subject to sector-specific regulation that imposes obligations Rocket Driver has not agreed in writing to meet, including information regulated under HIPAA, the Gramm-Leach-Bliley Act, FERPA, or similar laws; or
9. any information whose storage would place Rocket Driver under a legal or contractual obligation it has not expressly accepted in writing.

The Rocket Driver CRM includes free-text fields, including notes, task descriptions, custom fields, and message content. Rocket Driver does not inspect, filter, or monitor what is entered into them, and cannot prevent prohibited information from being entered. Compliance with this section is your responsibility.

If you become aware that prohibited information has been stored in the Rocket Driver CRM, you must remove it promptly and tell us at team@rocketdriver.com.

5. Files and attachments

The Rocket Driver CRM does not provide general file or document storage. The only upload function is an organization logo uploaded by an owner for branding purposes. Do not attempt to use the Rocket Driver CRM as a document repository.

6. Email, integrations, and outbound messages

Where you configure the Rocket Driver CRM to send email using your own mail service, or to connect to a mailbox, calendar, or other external system, you are responsible for the credentials you provide, for having authority to connect that system, and for the content of messages sent from your organization. Messages you send are subject to Section 33 of the Terms of Service and to applicable law, including laws governing commercial and automated messages.

The Rocket Driver CRM supports connecting a Gmail mailbox or a Microsoft 365 / Outlook mailbox using an application password issued by your mail provider, so that messages can be sent from that mailbox and synchronised into your organization’s records. This connection is available to your organization’s owner and sales-representative users. Whether to connect a mailbox at all is entirely your decision.

A mailbox or mail service you choose to connect is a service you have selected and continue to control. Rocket Driver does not choose it, contract for it, or operate it on your behalf, and your mail provider is not a Rocket Driver subprocessor — the relationship is between you and that provider, on their terms. What you should know before connecting one: message content that synchronises into the Rocket Driver CRM becomes part of your records in the Rocket Driver CRM, and Section 4 of these CRM Service Terms applies to it in full. Mailboxes routinely contain material Section 4 prohibits, and connecting a mailbox does not relax Section 4.

Rocket Driver stores mail-service and connected-mailbox credentials you provide in encrypted form, and uses them only to operate the connection you configured.

7. Features that are not enabled

Some features may be present in the Rocket Driver CRM interface or documentation but not enabled for your organization. A feature is available to you only when Rocket Driver has enabled it for your organization. Rocket Driver may enable, disable, or change features as described in Section 5 of the Terms of Service.

So that you are not left to infer it, this is what is and is not in operation as at the date of this page:

• System email is in operation. Rocket Driver sends service messages — invitations, notifications, password resets and similar — from no-reply@digitalteam.tech using a third-party email sending provider engaged by Rocket Driver. This is Rocket Driver’s own sending path and is separate from any mail service or mailbox you connect under Section 6.
• Text messaging and calling are not configured. The Rocket Driver CRM does not send text messages and does not place calls for your organization. No telephony provider is configured.
• Online Presence reporting is disabled by default. Where Rocket Driver has not enabled it for your organization, the third-party search-data provider it uses is not called for your organization at all. If Rocket Driver enables it for you, that provider receives the search and business-location information the report requires.
• Mailbox connection is available, as described in Section 6. Connections that depend on a provider sign-in authorization Rocket Driver has not yet completed — including Google and Microsoft sign-in (“OAuth”) connections and Microsoft calendar reading — are not currently available.

The providers Rocket Driver engages to process information in the Rocket Driver CRM are listed at https://www.rocketdriver.com/subprocessors/.

8. Availability and support

Rocket Driver does not commit to a specific level of availability, uptime, response time, or recovery time for the Rocket Driver CRM, and does not offer a service level agreement, unless expressly agreed in a signed written agreement. Section 5 and Section 37 of the Terms of Service apply.

9. Rocket Driver access to your organization

Rocket Driver personnel may access your organization and the systems that store your data where necessary to operate, secure, support, back up, restore, or troubleshoot the service, to respond to a request from you, or to comply with law. Access is limited to personnel who need it for those purposes and who are bound by confidentiality obligations. The Rocket Driver CRM Data Processing Agreement applies to any personal information accessed in this way.

Separately from the roles you assign inside your organization, a small number of Rocket Driver administrative functions operate across customer organizations. They are limited to administration of user accounts and multi-factor enrollment — for example, resetting a user’s multi-factor enrollment as described in Section 3 — and they do not give a Rocket Driver administrator access to your organization’s records. Access to your records is governed by the paragraph above and by the Rocket Driver CRM Data Processing Agreement.

10. Export and end of service

Section 29 of the Terms of Service and the Rocket Driver CRM Data Processing Agreement govern what happens to your data when your access ends.

The Rocket Driver CRM provides self-service export of contacts, companies, opportunities, and activities in CSV or JSON format, subject to a per-request row limit. That function is a convenience, not a complete copy. It does not cover message content, the contents of lead submissions, client account structures, tasks, generated reports, or uploaded branding files; some fields are omitted from the file formats it produces; and what it returns depends on the role and record access of the user who runs it.

If you want a copy of your organization’s records that the self-service export does not give you, request it at team@rocketdriver.com before your access ends. Rocket Driver prepares that extract by hand, so allow a reasonable period for it to be produced, and expect to verify your identity as your organization’s owner before it is released. The extract covers your organization’s records held in the Rocket Driver CRM. It does not include authentication or credential material — for example stored password hashes, credentials for services you connected, and invitation, password-reset and sharing tokens — which is withheld for security reasons; whatever is withheld is identified in the extract itself.

Information you delete, and information in an organization that is deleted, does not disappear from copies already written to Rocket Driver’s routine system backups. Rocket Driver does not delete individual records from within an existing backup file and does not restore individual records from a backup in order to preserve them. A backup copy goes away when that backup itself is removed. Backup copies held in off-site object storage are retained for 35 days and are then deleted on a scheduled basis.

11. Reporting a security concern

If you believe there has been unauthorized access to your organization’s Rocket Driver CRM data, or you discover a security vulnerability in the service, tell us at team@rocketdriver.com with “Security” in the subject line. Please include enough detail for us to reproduce or investigate the issue, and do not test against another organization’s data.

12. Changes to these CRM Service Terms

Section 45 of the Terms of Service applies.

13. Contact

team@rocketdriver.com