Frequently asked questions

Each customer database gets transaction log backups every 30 minutes, daily differential backups, and weekly full backups, all written to Azure Blob Storage separate from the database server. That means point-in-time recovery with at most the last half hour of activity at risk. Backups are kept for 90 days, with monthly copies kept two years and yearly copies five years. Read the full Data Protection & Backup overview.

On Microsoft Azure in the US East region. Every customer's data lives in its own dedicated SQL Server database.

Yes. All data is encrypted at rest with AES-256 encryption managed by Microsoft Azure, and encrypted in transit using TLS.

No. Each customer's data is held in a separate, isolated database rather than commingled in shared tables, so no customer's records are accessible from another customer's session.

Yes, within 30 days. Documents, photos, and attachments are stored with soft delete enabled, so a file removed in error, by a user or an administrator, can be restored.

No. Card details are sent directly to our payment processing partners (NMI and Celero) for authorization. XtremeCRM does not store full card numbers on the device or on our servers.

We keep your data for as long as your subscription is active. When a subscription is terminated, the associated data is deleted within 30 days. See our Privacy Policy for details.

Any modern browser at beta.xtremecrm.com, plus native apps for Windows 10/11, macOS (Apple Silicon), Linux, and Android. An iPhone app is on its way. See downloads.

No. The desktop apps keep themselves up to date, and the web app is always current.

Yes. Start from a spreadsheet and have real customer records in XtremeCRM the same day.

Yes. Invoices and payments taken in XtremeCRM can sync to QuickBooks, so the office doesn't re-key them.

Only when you turn it on. Location sharing is off by default, shows a visible indicator while it's active, stops automatically when you clock out, and can be turned off at any time.

One credit is one 160-character text. Longer texts are split by the phone carriers and every part drops to 153 characters, so the two-part ceiling is 306 characters rather than 320. A typical appointment reminder with an address and a booking link runs about 350 characters, which is three credits. See how credits work, with a live counter.

Because of its length. Anything over 160 characters is billed as more than one message, and merge fields make that vary by recipient — a long name and address can push part of a send onto an extra credit while the rest stay put. Check a message against the counter.

We email you at 80% of your plan's credits so you can add more yourself. Sending carries on past your plan's credits and pauses once you are 10% over, then starts again by itself as soon as you add credits. Plans and additional-credit prices.

No. Plan credits and any additional credits you buy end with the month, so buy additional credits for the sending you are about to do rather than as a reserve.

Yes. Every text uses a credit whether you send it or receive it. Replies are usually short, so they are usually one credit each.