ClosingDay
SECURITY AT CLOSINGDAY
Specific commitments. Not vague claims.
ClosingDay handles the entire deal — listings, private showings, open-house visitor sign-ins, buyer-agent feedback, public offer submissions, seller-portal sharing, and the full contract-to-close transaction record. That covers financial, identity, and contractual data on every side of the deal. You deserve a partner who is precise about how that data is protected — not a privacy policy that says "industry-standard encryption" and leaves it at that. This page documents exactly what we do today, what we don't yet do, and what's on the roadmap.
Last updated: May 2026. Security questions: security@getclosingday.ai.
HOW YOUR DATA IS PROTECTED
The five protections in production today.
These are not aspirational — every claim below is verifiable in our running infrastructure or in the linked provider trust pages further down.
Encryption at rest — AES-256
All customer data stored in our database, plus uploaded contracts and property photos, is encrypted at rest using AES-256 by our infrastructure providers (Render Postgres and Cloudflare R2). Sensitive tokens in our database — Gmail/Outlook OAuth tokens and SMTP passwords — are additionally encrypted with a per-deployment key before storage, so even DB read access cannot recover them.
Encryption in transit — TLS 1.3
Every connection between your browser/app and our servers is protected with TLS 1.3, terminated at Cloudflare. We do not accept plain-HTTP traffic. Internal communication between our backend services and the database runs on a private network — your data never traverses the public internet inside our infrastructure.
Strong authentication
Passwords are hashed with bcrypt (cost 12) — we cannot read your password, and a database breach would not expose them. Sessions use short-lived (15-minute) access tokens with refresh tokens that are themselves bcrypt-hashed at rest. Google Sign-In is fully supported via OAuth 2.0; password resets use single-use tokens that expire in 30 minutes. Every email/password signup goes through email verification — we email a single-use link the user must click to confirm the address; Google sign-ups inherit verification from Google OAuth.
Audit trail on every change
Every meaningful action — task status changes, contact edits, document uploads, draft sends, transaction lifecycle, deadline adjustments — is recorded in an immutable activity log against the user who performed it. Available to you in the Activity tab of every transaction.
Your contracts and documents stay private
Every contract you upload is stored on enterprise-grade private storage (Cloudflare R2) under a random, unguessable filename — never a public URL anyone could stumble onto. When you open a transaction, we generate a fresh, one-time link that only works in your browser and stops working after one hour. So even if you accidentally shared the link, it would be expired by the time anyone tried it. Every contract view and document download is re-checked against your login — there's no way to access a file without being signed in as you. We only accept the file types you'd expect (PDFs for contracts; PDF, JPG, or PNG for other documents and photos), and we verify each file's actual contents — not just its name — so a mis-labeled or unexpected file can't slip through.
AI & PRIVACY
Where your data goes when AI touches it.
The most common question we get from brokerages: what does your AI provider see, and could our data end up training someone else's model? Here's the precise answer.
01
AI provider: Anthropic
All AI features (contract extraction, draft generation, tone analysis, and Scout, our in-app assistant) are powered by Anthropic's Claude. We do not use OpenAI or any other LLM provider for customer data.
02
Your data is not used for AI training
Anthropic does not retain or train on data submitted via their API by default. ClosingDay does not opt into any data-sharing program. Your contracts, emails, and communications are not used to train any model — ours or theirs.
03
Drafts are reviewed before sending
By default, ClosingDay does not send an email on your behalf without your approval — every AI-generated draft sits in Pending Review until you click Approve. Auto-send is an explicit opt-in you enable and control (limited to your own saved templates going to outside parties, with a cancel window).
04
Tone training samples
When you train ClosingDay's tone, the sample emails you paste are stored to refresh the tone profile when you ask. They are not shared, indexed, or used outside your account. You can clear them at any time.
EMAIL INTEGRATION
What we ask for. What we don't.
Sending emails on your behalf is one of ClosingDay's core features. Here's exactly what permissions we request and what we do with them.
01
Send-only Gmail scope
When you connect Gmail, we request only the `gmail.send` scope. We can send messages on your behalf — we cannot read your inbox, search your messages, or access existing threads. The OAuth consent screen will confirm this scope before you authorize.
02
SMTP passwords are encrypted
If you connect via SMTP instead of Gmail, your SMTP password is encrypted with our per-deployment key before being written to the database. We never log SMTP credentials in plaintext.
03
Sent communications are stored
Emails ClosingDay sends on your behalf are recorded in your transaction's communications log so you can see what went out, when, and to whom. Replies that come back to your own inbox are not pulled into ClosingDay.
INFRASTRUCTURE PROVIDERS
Who we trust with what.
Every subprocessor we use carries an independent SOC 2 Type 2 attestation. Each link below points at their public trust page where you can review or download their report.
Provider
What they handle
Certifications
Render
Compute & managed Postgres
SOC 2 Type 2
HIPAA-eligible
Encryption at rest
Cloudflare
CDN, TLS termination, R2 object storage
SOC 2 Type 2
ISO 27001
PCI DSS
Vercel
Web frontend hosting
SOC 2 Type 2
ISO 27001
GDPR
Anthropic
AI provider (Claude API)
SOC 2 Type 2
ISO 27001
No training on API data
Resend
Transactional email (invites, password resets)
SOC 2 Type 2
GDPR
YOUR DATA, YOUR CONTROL
You own it. We just store it.
ClosingDay is a tool — the contracts, contacts, communications, and timelines are yours. Take them with you whenever you want.
Export anytime
Email hello@getclosingday.ai and we will produce a full export of your data — transactions, contacts, documents, communications, and audit log — in machine-readable JSON, within 5 business days.
Delete on request
You can permanently delete your account from Settings → Account. This cascades through your transactions, tasks, contacts, documents, drafts, communications, and shares. Soft-deleted data is purged within 30 days.
Disconnect Gmail/SMTP at any time
Settings → Email Configuration lets you disconnect your email integration in a single click, immediately revoking our send permission and deleting the stored OAuth/SMTP credentials.
No selling, no advertising
We do not sell your data, advertise to your clients, or share your account contents with anyone outside the subprocessors listed above. We are a SaaS product paid by agents and brokerages — not an ad-supported network.
WHAT'S COMING
The honest roadmap.
We won't claim certifications we don't hold. Here's what's already running, what's shipping in the next two quarters, and the longer-term path to SOC 2.
Live
Encryption at rest, TLS in transit, audit logging, granular access control
Already in production today.
Live
Per-transaction permission boundary for Transaction Coordinators
TCs only see the transactions of agents they are explicitly linked with — never the broader brokerage.
Live
Automated dependency vulnerability monitoring
GitHub Dependabot watches every dependency in our backend, frontend, and CI configurations on a weekly cadence. Critical CVEs surface as PRs the moment an upstream advisory publishes, regardless of the schedule.
Q3 2026
Multi-factor authentication (MFA)
TOTP-based MFA for all account types, with backup codes, targeted for Q3 2026.
Q3 2026
Independent penetration test
Engaging an external security firm for a black-box pen test. Summary report shareable with brokerages on request.
Q4 2026 / 2027
SOC 2 Type 1 → Type 2
Engaging a SOC 2 platform partner (Vanta or Drata) in Q3 with the goal of Type 1 attestation by end of Q4 2026 and Type 2 in 2027.
Found a vulnerability?
We treat security reports as the highest-priority class of issue. Email security@getclosingday.ai with the details — including reproduction steps and any proof-of-concept — and you'll get a human reply within one business day. We do not yet run a paid bug-bounty program, but we credit named contributors on this page once issues are remediated.
Talk to us before you commit.
Brokerage IT or compliance team has questions? We're happy to walk through our architecture, share our subprocessor list in DOCX form, or jump on a call with your security reviewer.
ClosingDay
© 2026 CLOSINGDAY · getclosingday.ai. All rights reserved.
Operated by CLOSINGDAY · 3988 Scottfield St, Dublin, CA 94568 · legal@getclosingday.ai