How AutoSync protects your shop's data

Everything between your browser, the AutoSync phone apps and our servers travels over HTTPS (TLS). In production the site also sends HSTS, so browsers refuse to connect without encryption.

• Passwords are never stored — only a one-way Argon2id hash.
• API keys, payment and accounting connections, and two-factor secrets are encrypted at rest (XSalsa20-Poly1305).
• Card numbers go straight to the payment processor and never touch AutoSync servers.
• Backups are encrypted with AES-256-GCM before they leave the server.

The database is backed up automatically every night, and uploaded photos and documents every week. Each backup is encrypted and copied to separate storage away from the main server, so losing a server never means losing your shop's history.

• Daily off-site copies kept for 30 days, plus one copy a month for 12 months.
• Every month a backup is downloaded, its checksum verified, decrypted and read end to end — a real restore test.
• A missed or failed backup alerts our on-call team right away.
• The recovery key is kept separately from the backups themselves.

Your team sees what their role allows, and nothing more — you set the roles. AutoSync staff only reach shop data when they need to help you, and the strongest controls apply to them.

• Two-factor sign-in is required for every AutoSync staff member and administrator. Shop users can turn it on for their own accounts.
• Two-person approval for 17 sensitive actions — for example deleting a shop's account, issuing large refunds, changing administrator access. One person asks, a second person approves.
• Every quarter we review everyone with staff or admin access and remove what is no longer needed.
• After 5 wrong passwords an account locks for 15 minutes, and sign-ins are recorded.
• When support signs in to your shop to help, they must give a reason, and every action they take is written to your audit log.
• Staff accounts are role-based — billing, support and engineering each see only their own tools.

Important actions — sign-ins, permission changes, refunds, deletions, exports — are written to an audit log with the person, time, IP address and what changed. Shop owners can read and export their own audit log in Settings, on plans that include it.

• Security events such as repeated failed sign-ins and 2FA changes are recorded and reviewed.
• Health checks run every five minutes, and an outside monitor raises the alarm if the servers stop answering.
• Errors are grouped and tracked until they are fixed.
• Critical problems page our on-call team by email, text and phone app.

Your shop's data belongs to your shop. We do not sell it, and we only use it to run AutoSync for you.

• Owners can export everything — customers, vehicles, repair orders, invoices, payments — as spreadsheets any time from Settings → Export your data.
• Ask us to delete your shop's data and we will, after confirming the request with the account owner.
• Each shop's records are kept separate from every other shop's.
• Questions about privacy: support@autosyncshopmanager.com.

If something goes wrong, our on-call team is alerted automatically and works the problem until it is fixed. Live service status, past incidents and planned maintenance are on our status page.

• A written incident process: detect, contain, fix, then review what to change so it does not happen again.
• If your shop's data is affected by a security incident, we tell the account owner directly and promptly.

View system status

AutoSync uses 13 outside services to do things like process card payments, send text messages and keep encrypted backups. Each one receives only the data it needs. The full list shows what each service does, what it receives and where.

See the subprocessor list