BlogFeature Guide

Deelo Security: How We Protect Your Business Data

A public, plain-language account of how Deelo protects your business data: authentication, authorization, encryption, operational controls, healthcare-grade handling for PHI, our SOC 2 path, and the gaps we are still closing.

Davaughn White·Founder
12 min read

If you run a small business on Deelo, you are trusting us with the keys to it. Your customer list. Your invoices and unpaid balances. Your contracts. Your support tickets. Your patient records, in some cases. A breach for a 200-person enterprise is a bad quarter. A breach for a 10-person business is existential.

We take that seriously, and we think the right way to take it seriously is to tell you exactly what we do, exactly what is in progress, and exactly what is not done yet. This page is the public version of the security walkthrough we do with customers on enterprise calls. It is not marketing copy. It names the controls, the technologies underneath them, and the gaps we are still closing in 2026.

If you would rather skip to specifics: authentication uses bcrypt-hashed passwords and TOTP-based 2FA, authorization is enforced at the database query level on every request with team-scoped multi-tenancy, every connection uses HTTPS, and healthcare apps that handle PHI encrypt sensitive fields with AES-256-GCM before they are stored. SOC 2 is on our roadmap: no audit has started and there is no report. There is no bug bounty yet.

Why security matters more for small businesses, not less

The conventional framing is that big enterprises need serious security and small businesses can lean on "we are too small to be a target." That framing is wrong, and has been for at least five years. Small businesses are the preferred target precisely because they are assumed not to be hardened. Phishing, credential stuffing, OAuth token theft, and supply-chain compromise through SaaS vendors are now industrialized — there is no manual targeting decision, you are scanned and probed automatically.

The second reason: a small business's SaaS vendor holds a larger share of the business's total operational state. A 5,000-person enterprise has its data spread across hundreds of systems. A 10-person business often has its CRM, helpdesk, billing, contracts, and team comms all running on three or four tools. If one of those tools gets breached, the blast radius is most of the company.

We write security with that in mind. The defenses we build are not aspirational "someday at IPO" controls — they are the floor for someone trusting Deelo with the operational core of their business today.

Layer 1: Authentication — proving you are you

Authentication is the first line of defense and the most common point of failure across the SaaS industry. Most breaches start here, not with sophisticated zero-day exploits. We harden the basics first.

  • Passwords are hashed with bcrypt. We never store plaintext passwords. Bcrypt is intentionally slow and salted per user, which makes offline cracking expensive even if a hash dump were ever stolen.
  • Two-factor authentication via TOTP. Customers can enable 2FA in Settings → Security. We support standard authenticator apps (Google Authenticator, Authy, 1Password, Bitwarden). Backup codes are issued at setup, stored only as hashes, work once, and can be regenerated. We recommend every account enable 2FA.
  • Google OAuth as an SSO option. Customers who sign in with Google never have a Deelo password at all — the credential lives at Google, gated by whatever 2FA Google enforces. This is the most popular sign-in path for small teams already standardized on Google Workspace.
  • Rate-limited login attempts. Repeated failed sign-in attempts are throttled and locked. Automated credential-stuffing attacks against a Deelo account hit a wall quickly.
  • HttpOnly, Secure session cookies. Session tokens are sent over HTTPS only and are not readable by JavaScript, which prevents the most common XSS-based token theft.
  • Passkeys. You can sign in with a passkey (Face ID, Touch ID, Windows Hello or a hardware security key). A passkey sign-in requires the device's PIN or biometric.
  • Idle sessions sign out. Settings → Security → Session Timeout signs a device out after the time you choose with no activity on it (24 hours unless you change it).
  • Sign out other devices. Settings → Security lists your signed-in devices. End any one of them, or log out every device but the one you are using; they are signed out on their next request.

One thing we want to be honest about: 2FA adoption across the customer base is not 100%. We strongly encourage it, but turning it on is each person's choice today; a team owner can't require it yet. If you are reading this and have not turned on 2FA, that is the single highest-leverage thing you can do in the next ten minutes.

Layer 2: Authorization — what each person can actually see

Authentication proves who you are. Authorization decides what you can do once you are in. This is where multi-tenant SaaS gets dangerous if it is not architected carefully — the worst breaches we have seen in this industry are not break-ins, they are accidental cross-tenant data exposure where the wrong customer sees another customer's records.

We defend against this at the database query layer, not just at the application layer. Every authenticated request carries a team identifier, and our base repository pattern enforces that every query against a tenant-scoped collection includes that team filter.

  • Per-app permissions. Deelo has 50+ apps (CRM, helpdesk, billing, projects, healthcare apps, and more). Each app exposes granular permissions like view, edit, delete, and category-specific actions. A support agent can have helpdesk access without seeing billing. A bookkeeper can see invoices without seeing patient notes.
  • Scoped permissions for own-vs-all access. Some permissions have a `.own` variant — a field technician can have `view.own` on work orders (sees only their assigned work) without `view` (which would show every technician's queue). The data layer enforces the scope.
  • Role-based defaults. Four base roles — owner, admin, member, viewer — set sensible defaults for every app. Most teams never need to touch individual permissions; the defaults are calibrated for typical small-business roles.
  • Custom roles and per-user overrides. When defaults are not enough, you can define custom roles (e.g., "Billing-only contractor") or override permissions for individual users. Resolution order is documented: user overrides win, then custom role, then base role default.
  • Multi-tenant isolation at the query level. Every tenant-scoped database query automatically includes the team filter. Compliance-sensitive queries also carry an audit context that records who asked, when, and why.

Layer 3: Data protection — encryption in transit and at rest

Encryption is table stakes for any SaaS in 2026, but "we use encryption" without specifics is one of the more meaningless claims in the security marketing genre. Here is what we actually do.

  • HTTPS for every connection. Every connection to Deelo — browser, mobile app, API — is served over HTTPS. TLS is terminated at our DigitalOcean Load Balancer.
  • HSTS enforced. Browsers are instructed to refuse plaintext connections to Deelo for a year, which prevents downgrade attacks.
  • Per-field encryption for sensitive collections. The healthcare apps (Practice, Dentistry, Cardiology, Radiology, Ophthalmology, Pathology, DermAI, Disease Analysis) encrypt PHI and PII field by field with AES-256-GCM, using a key derived for each team — patient names, diagnoses, notes, identifiers. Even with database-level access, those fields are unreadable without the application-layer key.
  • Secrets redacted from audit logs. Passwords, tokens, API keys and other known sensitive fields are redacted before an audit entry is written.
  • Session cookies are HttpOnly + Secure + SameSite. Cookies that carry session state cannot be accessed by JavaScript, cannot travel over plaintext, and cannot be sent in unexpected cross-site contexts.

Layer 4: Operational security — the parts you do not see

Most security failures are not failures of cryptography. They are operational — a former employee whose access never got revoked, a vendor with too-broad access, an alert that nobody saw. Operational discipline is the difference between a well-designed system and a secure one.

  • Audit logs. Sign-ins, password and two-factor changes, and access to healthcare records are logged with who did what, and when.

Healthcare apps: HIPAA-grade handling

A subset of Deelo's apps handle protected health information. Practice, Dentistry, Cardiology, Radiology, Ophthalmology, Pathology, DermAI, and Disease Analysis are designed for clinical workflows where the data is regulated under HIPAA in the US (and analogous regimes elsewhere). For those apps, the defense layers are stricter.

  • Per-field encryption for PHI. Patient names, identifiers, diagnoses, clinical notes, and other sensitive fields are encrypted at the application layer before they reach the database.
  • HIPAA middleware on healthcare endpoints. Healthcare app endpoints pass through a HIPAA-aware middleware that records each access to patient data, with the reason given for it.
  • Performed-by and reviewed-by metadata on clinical records. Healthcare app records carry standard workflow metadata (who performed an action, who reviewed it, what the review status is) so audit trails are complete by design, not bolted on after the fact.
  • Business Associate Agreement (BAA) ready terms. Customers using the healthcare apps in a HIPAA-covered capacity can sign a BAA with us. Reach out to security@deelo.ai for the current template.

An honest note on scope: HIPAA safeguards at Deelo are by-app, not company-wide. The healthcare apps carry the safeguards above. The other apps (CRM, marketing, projects, etc.) are not in scope for HIPAA — if you put PHI into a non-healthcare app, you are operating outside the design intent and outside what our BAA covers. We do not recommend it.

SOC 2: where we are honestly

We get this question on most enterprise sales calls, and we believe the honest answer earns more trust than a generic "we are SOC 2 compliant" claim that turns out to mean "we are working on it." Here is exactly where we are.

  • SOC 2 is on our roadmap. No SOC 2 audit has started, and Deelo has no SOC 2 report.
  • We will not claim a certification we do not have. When we have a SOC 2 report, this page will say so and link to the report (available under NDA to prospects and customers). Until then, this page says so.

What you can do as a customer

Security is a shared model. We harden the platform. You harden your team's use of it. The single highest-leverage things a customer can do, in rough order of impact:

  • Turn on 2FA. Today. Settings → Security → Enable two-factor authentication. Generate backup codes and store them somewhere safe. If you administer a team, ask everyone to turn it on — it is the single biggest reduction in account-takeover risk available.
  • Set up SSO (Business and Enterprise plans). SSO through SAML or OpenID Connect lets you centralize authentication in your identity provider (Okta, Azure AD, Google Workspace, JumpCloud). Deprovisioning a departing employee in your IdP stops their SSO sign-ins.
  • Audit user permissions quarterly. Open Settings → Team and review who has access to what. Look for stale accounts, over-broad roles, and people who changed jobs but still hold their old permissions. Ten minutes a quarter prevents most insider-risk incidents.
  • Review your active sessions. Settings → Security → Active Sessions lists the devices signed in to your account. End any session you do not recognize or from a device you no longer own, or log out every other device at once.
  • Use custom roles instead of giving everyone admin. The default "give them admin so it works" pattern is the single most common cause of accidental access in small businesses. Build a custom role that grants exactly what the role needs and assign it.
  • Watch the security@deelo.ai inbox. If you ever need to report a vulnerability, suspected breach, or security concern, write to security@deelo.ai.

Subprocessors: the vendors we use

Every SaaS platform sits on top of other vendors. Pretending otherwise is dishonest. Here are the vendors we rely on and what they do.

  • Database: MongoDB. Our production data is stored in MongoDB.
  • Payments: Stripe. Subscriptions and card payments are processed by Stripe.
  • Hosting: DigitalOcean. Deelo runs on DigitalOcean behind a DigitalOcean Load Balancer, and uploaded files are stored in DigitalOcean Spaces.
  • AI: OpenRouter. Some Deelo features call AI models. Those requests go through OpenRouter and carry only the data the request needs.
  • Email delivery: Resend. Transactional and notification email is sent through Resend.

Reporting a security issue

Customers, security researchers, and the general public can report vulnerabilities, suspected breaches, or other security concerns to security@deelo.ai.

  • security@deelo.ai for reporting. Customers, security researchers, and the general public can report issues to security@deelo.ai.

The honest gaps

Every security page should have this section. We owe customers a clear list of what we have not done yet, so they can decide whether the gap is a dealbreaker for their use case.

  • No SOC 2 report. SOC 2 is on our roadmap; no audit has started.
  • HIPAA scope is by-app, not company-wide. Healthcare apps carry the safeguards described above and are covered by the BAA. Non-healthcare apps are not in HIPAA scope. Do not put PHI into a non-healthcare app.
  • No bug bounty program yet. A formal bounty program is planned but not yet live. In the meantime, we welcome responsible disclosure to security@deelo.ai and will acknowledge researchers who report valid issues.
  • No regional data residency option. Customers with EU or other data residency requirements should reach out.
  • No third-party penetration test yet. A third-party penetration test with a publishable report is on our roadmap.
  • Bring-your-own-key (BYOK) encryption is not yet supported. Per-field encryption uses Deelo-managed keys. Customers with regulatory requirements for customer-managed keys should contact us — this is a tracked roadmap item.

Harden your Deelo workspace in ten minutes

Turn on 2FA, review your active sessions, and audit who has access to what. These three steps reduce the most common account-takeover risk by an order of magnitude. Settings → Security is where every one of those lives. For questions about security, BAA terms, SOC 2 timeline, or subprocessor details, email security@deelo.ai — we answer.

Start Free — No Credit Card

Frequently asked questions

Does Deelo encrypt customer data?
Yes. All traffic to Deelo uses HTTPS (TLS is terminated at our DigitalOcean Load Balancer, and HSTS is on). Sensitive fields in healthcare apps (Practice, Dentistry, Cardiology, Radiology, Ophthalmology, Pathology, DermAI, Disease Analysis) are also encrypted at the application layer with AES-256-GCM, using a key derived for each team, so PHI remains unreadable even with database-level access.
Is Deelo SOC 2 compliant?
No. Deelo does not have a SOC 2 report, and no SOC 2 audit has started. SOC 2 is on our roadmap. We will not claim a certification we do not have; when we have a report, this page will say so.
Is Deelo HIPAA compliant?
Deelo's healthcare apps — Practice, Dentistry, Cardiology, Radiology, Ophthalmology, Pathology, DermAI, and Disease Analysis — include per-field encryption of PHI, HIPAA-specific middleware that logs access to patient data, and a Business Associate Agreement (BAA). HIPAA scope is by-app, not company-wide. Non-healthcare apps (CRM, marketing, etc.) are not in HIPAA scope and should not be used to store PHI.
How does Deelo handle two-factor authentication?
Two-factor authentication is available to every account via Settings → Security. Deelo supports TOTP-based 2FA, which works with standard authenticator apps including Google Authenticator, Authy, 1Password, and Bitwarden. Backup codes are issued at setup and can be regenerated. You can also sign in with a passkey. We strongly recommend every account turn it on.
What does Deelo do to prevent cross-tenant data leakage?
Multi-tenant isolation is enforced at the database query layer, not just at the application layer. Every authenticated request carries a team identifier, and our base repository pattern automatically scopes every tenant-relevant query to that team.
Does Deelo's AI training use customer data?
No. Deelo does not train AI models on customer data. AI features send only the data a request needs, through OpenRouter, to the model that answers it.
How do I report a security vulnerability to Deelo?
Email security@deelo.ai. We do not yet have a formal bug bounty program (it is planned), but we welcome responsible disclosure. Please give us a reasonable window to investigate and fix before public disclosure.
What happens if Deelo has a security incident?
Report suspected incidents to security@deelo.ai. If a security incident affects your data, we will notify you as required by law.
Where is Deelo customer data stored?
Deelo runs on DigitalOcean, and uploaded files are stored in DigitalOcean Spaces. There is no regional data residency option today; customers with EU or other residency requirements should contact security@deelo.ai.
Who has access to my data inside Deelo the company?
Access to production systems is limited to the people who operate Deelo.

The thing we keep coming back to internally: small-business security is not a marketing problem, it is a craft problem. The right defenses are not exotic — bcrypt for passwords, TOTP and passkeys for sign-in, HTTPS everywhere, field-level encryption for sensitive data, query-level tenant isolation, audit logs, honest disclosure of gaps. The hard part is doing all of them, consistently, without shortcuts, and telling customers the truth about where you are. That is what this page is. If you find something missing, email security@deelo.ai and we will fix it.

Explore More

Related Articles