Skip to content
Start free trial

FAQ: Data Security and Privacy

FAQ: Data Security and Privacy

Common questions about how HARi CRM protects your data.

Your data is stored on secure servers with enterprise-grade infrastructure. Data residency options are available for organizations with specific geographic requirements.

Yes. All data is encrypted in transit using TLS 1.3 (the same encryption used by banks). Data at rest is also encrypted using AES-256 encryption.

Only people in your workspace with a valid login. Inside the workspace, access follows teams and roles: a record belongs to a team, and a role says who can view, edit, or export it. Open the record and click Who can see this? for the named list — who can see what. HARi support can only access your data with your explicit permission for troubleshooting. We never sell, share, or use your data for advertising.

Yes. Automated backups run daily with a tiered retention schedule (recent dailies + weekly + monthly snapshots). In the event of data loss, we can restore your data to a recent backup point.

When you close your workspace from Settings → Billing, it enters a 30-day grace period. During those 30 days the workspace becomes read-only — nobody can create or modify records — but you can cancel the closure at any time from the same Billing page and pick up where you left off. After the grace period ends, every record, message, file, and user account is permanently deleted, including from backups. We plan to email an automatic data export before deletion in a future update; until then, please export your workspace yourself during the grace period (see Can I export all my data? below). See How do I close my workspace? for the full flow.

Who in my team can see a contact I just added?

Section titled “Who in my team can see a contact I just added?”

The team that holds it — usually your default working team — plus anyone whose role reaches that business unit or the whole workspace, and administrators. Owner is the person who follows up; changing Owner does not hide the row. Verizon’s 2024 DBIR found the human element in 68% of breaches (Verizon 2024 DBIR); keeping reach on the team, not on “everyone is an admin,” is the control that actually matches that number. Teams and roles and private records cover the rest.

Yes, at any time, in two ways. To export a single entity (Contacts, Companies, Leads, etc.) as a CSV, open that entity’s list view and use the Import button on the toolbar — the same screen handles export. To get a complete copy of your entire workspace — including records, attachments, audit log, and email history — go to Settings → Data Privacy and click Request export. You’ll receive a download link by email within about 15 minutes. See Full workspace export for details. You always own your data and can take it with you.

Passwords are hashed using industry-standard algorithms (bcrypt). We never store passwords in plain text. Even HARi administrators cannot see user passwords.

Do you support two-factor authentication (2FA)?

Section titled “Do you support two-factor authentication (2FA)?”

2FA is on the roadmap. Today, account access is protected by bcrypt-hashed passwords, JWT access + refresh tokens, rate-limited login attempts, and per-tenant database isolation. Contact us if mandatory 2FA is a requirement for your rollout.

HARi is designed with privacy by design. You can delete individual records, export all personal data, and manage consent — the core capabilities needed for GDPR compliance. We also offer a Data Processing Agreement (DPA) for organizations that require one.

If you discover a potential security vulnerability, please contact us immediately. We take all security reports seriously and respond within 24 hours.

Yes. All uploaded files (photos, documents) are stored in a private S3-compatible bucket. They are never publicly accessible — every file request requires a valid authentication token. Files are served with strict security headers (X-Content-Type-Options: nosniff, Content-Security-Policy: default-src 'none') to prevent content injection.

Each tenant’s files are stored in a separate directory and can only be accessed by authenticated users of that tenant. Even if someone guesses a file URL, they cannot access it without a valid session.

Contact our team for detailed security documentation or to discuss specific compliance requirements for your organization.