How ECHOPS protects your company’s data

Your data is kept apart

Every company gets its own workspace at yourcompany.echops.com. In the database, each workspace’s rows are protected by row-level security. The app’s own database login can’t bypass it, and a workspace’s pages can only read that workspace’s rows. Automated tests fail if any table is missing row-level security.

Your data is stored in the United States, with the database in the East US region.

Signing in

No passwords. People sign in with a one-time email link or a passkey, so there’s no password to steal or reuse. Sign-in links are only sent to people who already have an account or an invitation.

A second step. Owners and admins always add a second step, a passkey or an authenticator code. An owner can require it for everyone in the workspace.

Sessions stay home. A session belongs to your company’s own address, so it never works on another workspace.

Roles. Owner, admin, member and viewer, plus departments that limit which sections a person sees. Group chats and direct messages are private to the people in them, not even owners can read them.

Support access

When the ECHOPS team needs to look inside your workspace to help, access is opened for 30, 60 or 120 minutes, with a written reason and a fresh second-step check. It ends when the time is up. A support visit can’t change sign-in settings, your team or billing, can’t open your private chats, can’t send anything to your clients and can’t export your data. Every visit shows in your workspace’s activity log.

An activity log you can trust

Changes and support visits go into an activity log that can only be added to: the database refuses edits and deletions. Owners and admins read it in Settings.

Encryption

Every ECHOPS page loads over HTTPS, and browsers are told to use nothing else (HSTS). Connected tools’ keys and tokens, and second-step secrets, are encrypted with AES-256-GCM before they’re stored.

ECHOPS never stores card numbers. When you record a card payment, it keeps the last 4 digits only. Payroll doesn’t keep tax IDs or bank account numbers.

Backups and retention

• Daily backups, with the last 7 days kept. Backups are restored inside our database provider and can’t be downloaded. In the worst case, a restore loses the changes made since the last daily backup, up to 24 hours.
• Raw lead submissions, exactly as they arrived from your forms, webhooks and lead emails, are kept for 90 days for troubleshooting, then deleted. The leads themselves stay.
• Bell notifications are kept for 60 days.
• Uploads that are never attached to anything are deleted every night.

Monitoring without personal data

We watch for errors and downtime. Error reports carry ids only: names, emails, phone numbers, cookies, request bodies and sign-in links are kept out, and any text left is scrubbed of emails and phone numbers before it leaves. Uptime checks never return customer data, and background jobs carry ids, not contact details.