Real estate CRM security that holds up when something goes wrong.
Your clients trust you with their details. Here is how Uplevel protects them when a password leaks, a laptop goes missing, an agent leaves or a server fails.
What if…
Breached passwords are refused
New and changed passwords are checked against known breaches. If yours shows up in one later, your next sign-in can only change it.
A second factor stands in the way
With an authenticator app turned on, the password alone is not enough to sign in.
You can see the attempt
Sign-ins and failed sign-ins are listed in your security activity.
With two-factor on, a leaked password opens nothing.
How sign-in works
Big changes ask who you are
Changing the password, turning off two-factor or removing a passkey needs your password, a code or a passkey first.
Sign it out from anywhere
Your sessions list shows every signed-in browser. End the one you lost.
A new password clears the rest
Changing your password signs out every other session.
You can cut that laptop off from any other device.
How sign-in works
Nothing until you allow it
Support can open your workspace only after someone with access to support settings turns access on.
Access ends by itself
You choose 1, 7 or 30 days. Turning it off ends any open visit right away.
Every grant is on the record
Turning support access on or off is written to your security activity.
Support has no standing access to your workspace.
Who can see your data
Your directory switches them off
With SCIM, deactivating someone in Okta, Entra ID, OneLogin or JumpCloud suspends them in your brokerage.
Single sign-on can be the only way in
Require SSO for your domain, and password, email code, Google and passkey sign-ins are refused for those addresses.
Brokerage leads can stay
Choose to keep the contacts your brokerage gave them. They move to the person or pond you pick.
Off in your directory means out of Uplevel.
SSO and SCIM
A continuous archive
Changes are archived as they happen, so the database can be restored to a point in time.
A sealed nightly copy
Every night a full copy is encrypted to a key we keep offline, off the platform.
Locked against deletion
Nightly copies can’t be deleted for 29 days, even with the key that writes them.
Restores rehearsed
We restore from backup on a schedule to prove the copies work.
There is always a recent copy to come back to.
How backups work
The specifics.
For whoever checks software before your brokerage signs. Each line is how Uplevel runs today.
- Connections
- TLS everywhere, including your websites
- Database connections
- TLS with the server certificate verified
- Stored data and files
- Encrypted at rest
- Tokens, provider keys, two-factor secrets
- AES-256-GCM, rotatable keys
- Passwords
- Argon2id hashes, checked against known breaches
- API tokens
- Kept only as SHA-256 digests
- Nightly backups
- Encrypted to an offline key, locked for 29 days
- Security activity
- Kept 400 days
- Private file links
- Expire after 60 seconds
- Support access
- 1, 7 or 30 days, only when you grant it
- Where data lives
- United States
Encrypted on the wire and on disk.
Every page, sign-in and API call travels over TLS, and so does every website you publish with us. Inside our platform, connections to the database check the server’s certificate and refuse anything unencrypted.
Everything we store is encrypted at rest. Connected-account tokens, provider keys and two-factor secrets are encrypted a second time with AES-256-GCM, using keys we keep in a secrets manager and can rotate. Passwords are kept only as Argon2id hashes, and API tokens only as SHA-256 digests.
Uplevel isn’t end-to-end encrypted. Our servers read your data to search it, send your email and let Jan help, so the rest of this page is about who can reach it.
Backups nobody can quietly delete.
The database is archived continuously, so we can restore it to a point in time. Every night we also take a full copy, encrypt it to a key we keep offline, and lock it against deletion. A backup only counts if it restores, so we rehearse restores on a schedule.
- Point-in-time recovery from a continuous archive
- A full copy every night, encrypted to an offline key
- Nightly copies locked against deletion for 29 days
- Restores rehearsed on a schedule
Sign-in for one agent or a whole brokerage.
Sign in with a password, an emailed code, Google or a passkey. Add an authenticator app for two-factor, with backup codes for the day your phone isn’t with you. Passwords found in known breaches are refused, and changing anything sensitive asks you to confirm it’s you. Your sessions list shows every signed-in browser, and you can end any of them.
Brokerages can connect Okta, OneLogin, Auth0, JumpCloud or any OpenID Connect provider, or a SAML 2.0 app such as Microsoft Entra ID, AD FS or PingFederate. Require single sign-on for your verified domain. SCIM adds and deactivates people as your directory changes, with a dry run to try it first, and directory groups can set each agent’s access profile.
Running a brokerage? Bring your directory and your questions.
Get early accessWho can see your data.
Encryption protects data on the way and at rest. Access rules decide who reads it once it’s there.
- You and your team
- Roles and access profiles decide what each person can open and change, and they are checked on every request. Contacts can be private to their owner or shared with the team.
- Uplevel support
- Only after you grant access, for 1, 7 or 30 days. Each grant appears in your security activity, and turning access off ends any visit in progress.
- Uplevel staff tools
- Behind an allowlist, a private network and a second factor of their own. Every staff action is written to a log that can’t be edited or deleted.
- Our own services
- Each one signs in to the database with its own narrow permissions. Database connections and permission changes are logged.
- AI providers
- Only the context a request needs, to answer it, and never for training. They are named on our sub-processors page.
An audit trail you can read.
Your security activity lists sign-ins and failed sign-ins, two-factor, passkey and session changes, API keys, members and roles, integrations and webhooks, support access, exports and contact erasures.
It’s kept for 400 days. Find it in Settings → Security, or ask Jan who signed in this week.
Files and connections, checked.
Uploads are scanned for malware before they're accepted, and anything infected is refused. Private files open through links that expire after 60 seconds.
Webhooks go only to public HTTPS addresses you have verified, and every delivery is signed. Messages from our phone provider are signature-checked, and lead emails are checked for SPF, DKIM and DMARC.
Your data stays yours.
Your workspace data is stored in the United States. We don’t train AI on it, and Google data is handled under Google’s Limited Use requirements.
Export your data whenever you like and erase a contact on request. You choose how long call transcripts, summaries and voicemail are kept, from 30 days to until you delete them.
Where we stand on assurance.
- CASA Tier 2In progress
- Google’s security assessment for apps that read Gmail, built on OWASP ASVS Level 2. We are working through it now.
- Payments
- Card payments are handled by Stripe, a PCI DSS Level 1 service provider.
- Vulnerability reports
- Our disclosure policy says what is in scope and how we respond. Our security.txt says how to reach us.
Questions buyers ask.
Something we didn’t cover? Write to hello@uplevelre.com.
Can Uplevel staff read my contacts?
Not by default. Our support team can open your workspace only when you grant access, for 1, 7 or 30 days, and every grant is recorded in your security activity. Outside that, production data is reachable only through an emergency procedure a few engineers can use during an incident, and every database connection is logged.
Where is my data stored?
Your workspace data is stored in the United States, encrypted at rest. The companies that process data for us, including the AI providers behind Jan, are named on our sub-processors page.
Do you train AI on my data?
No. When you ask Jan for help, the context that request needs goes to our AI providers to produce the answer. It is never used to train models. Google data is handled under Google’s Limited Use requirements.
Can I require SSO for my brokerage?
Yes. Connect Okta, OneLogin, Auth0, JumpCloud or any OpenID Connect provider, or a SAML 2.0 app such as Microsoft Entra ID, then require single sign-on for your verified domain. SCIM can add and deactivate people as your directory changes, and you can try it as a dry run first.
How do backups work?
The database is archived continuously, so it can be restored to a point in time. Every night a full copy is encrypted to a key we keep offline and locked against deletion for 29 days. We rehearse restores on a schedule.
Is Uplevel end-to-end encrypted?
No. Everything is encrypted in transit and at rest, and credentials are encrypted a second time. Our servers can read your workspace data, because search, sending and Jan need it. That is why access to it is limited and logged.
Bring your questions. Bring your business.
Apply for early access. If this page left a question open, ask it before you decide.