Security

Where the money goes. Where the data lives.

You're about to run your tenants' rent through software you haven't used before. Here is exactly what happens to it, and what we can and cannot see.

We never hold your money.

Every rent charge is created directly on your business's own Stripe account. You're the merchant of record, the payment settles to your Stripe balance, and Stripe pays it out to your bank. It never passes through an account Rentarina holds. We are not a bank, a money transmitter, or an escrow agent, and we are not structured to become one.

On bank transfer, the tenant pays 1.5%, which covers Stripe's cost and ours, and Stripe deducts it from that same charge. On card, the only fee is Stripe's standard processing cost; there is no Rentarina fee. Each payment is recorded with three amounts: Stripe’s processing cost, the total fee taken from the charge (which includes that cost), and the fee the tenant paid.

Stripe runs your business verification through its own onboarding, embedded in Rentarina. Stripe holds your identity and bank details, and we store only the verification status. Payouts run on the schedule Stripe sets for your account; Rentarina doesn’t set, hold, or redirect them.

A lease records the security deposit amount. Rentarina doesn’t collect, hold, or return deposits.

Your data can't reach another landlord.

This is the part we'd want to see if we were buying this.

Every request for your records is limited to your account before it runs. Behind that, the database itself enforces the same boundary on its own, and returns nothing at all when it can't tell whose account is asking. The app doesn't have the permission it would need to switch that off. Two separate safeguards, either of which would stop a leak on its own.

Tenants see their own lease, their own payment history, their own maintenance requests and documents. Not another tenant's, not another landlord's. Document downloads and receipts check that the tenant asking is the one on the record, so a tenant who edits a link to guess at someone else's file gets an error, not the file.

We test this. Our automated tests try to reach another landlord's records directly and confirm they're refused, and confirm the app can't switch off the database's safeguard.

What we don't store.

Social Security numbers. No field exists for one anywhere in the system, and tax forms like a W-9 are turned away at upload. We don't collect them and we have nowhere to put them.

Bank credentials. Stripe holds bank details and gives us a reference in their place. We never see a full account or routing number.

Full card numbers. Tenants type card details into Stripe's own secure form. The numbers never reach us.

Government ID images. There is no ID document type to file one under, and we don't use them for automated identity checks.

The safest place to keep sensitive data is somewhere you aren't. Most of the security work here was deciding what not to hold.

Your data is not training data.

We do not use your data, your tenants' data, your leases, or your payment records to train AI models. Not ours, not a vendor's.

Rentarina AI reads your data to answer your questions and draft your messages. Those requests run under business agreements with our AI provider that don’t allow training on your data. Nothing you put into Rentarina makes a model smarter.

What the AI can touch.

No message Rentarina AI drafts reaches a tenant until you’ve read it and pressed send. In Ask, the only changes it can prepare are resolving a maintenance request and recording an off-platform payment, and neither is written until you confirm.

Two things run without that step. It sorts new maintenance requests by category and priority. And it reads expiry dates off the documents you upload and marks them as they come due.

Anything a tenant writes is treated as something to read, never as an instruction to follow. Every AI request is logged against your account.

Who processes your data.

StripePayments, payouts and identity verificationSOC 2 Type 2, audited annually · public SOC 3
VercelApplication hosting and file storageSOC 2 Type 2 · ISO 27001:2022
NeonDatabase hostingSOC 2 Type 2 · ISO 27001 · ISO 27701
ClerkSign-in and account securitySOC 2 Type 2 since 2022
AnthropicAI-assisted featuresSOC 2 Type 2 · ISO 27001:2022 · ISO 42001:2023 · public SOC 3
ResendEmail deliverySOC 2 Type 2
SentryError monitoringSOC 2 Type 2 · ISO 27001
UpstashRate limiting — receives visitors' IP addresses and account identifiers as short-lived counters—
SignWellLease e-signatures — receives the names and email addresses of the tenant and landlord signers and the lease documents, and records a signing audit trail including IP addresses—

SOC 2 reports are confidential by design — there's no public registry for any vendor, ours included. Each vendor above with an attestation listed publishes a trust center and releases its report under NDA. Stripe and Anthropic also publish public SOC 3 summaries anyone can read.

This is the complete list. Not a sample, not the notable ones. We tell you before it changes.

We never hold your money.

Every rent charge is created directly on your business's own Stripe account. You're the merchant of record, the payment settles to your Stripe balance, and Stripe pays it out to your bank. It never passes through an account Rentarina holds. We are not a bank, a money transmitter, or an escrow agent, and we are not structured to become one.

On bank transfer, the tenant pays 1.5%, which covers Stripe's cost and ours, and Stripe deducts it from that same charge. On card, the only fee is Stripe's standard processing cost; there is no Rentarina fee. Each payment is recorded with three amounts: Stripe’s processing cost, the total fee taken from the charge (which includes that cost), and the fee the tenant paid.

Stripe runs your business verification through its own onboarding, embedded in Rentarina. Stripe holds your identity and bank details, and we store only the verification status. Payouts run on the schedule Stripe sets for your account; Rentarina doesn’t set, hold, or redirect them.

A lease records the security deposit amount. Rentarina doesn’t collect, hold, or return deposits.

Your data can't reach another landlord.

This is the part we'd want to see if we were buying this.

Every request for your records is limited to your account before it runs. Behind that, the database itself enforces the same boundary on its own, and returns nothing at all when it can't tell whose account is asking. The app doesn't have the permission it would need to switch that off. Two separate safeguards, either of which would stop a leak on its own.

Tenants see their own lease, their own payment history, their own maintenance requests and documents. Not another tenant's, not another landlord's. Document downloads and receipts check that the tenant asking is the one on the record, so a tenant who edits a link to guess at someone else's file gets an error, not the file.

We test this. Our automated tests try to reach another landlord's records directly and confirm they're refused, and confirm the app can't switch off the database's safeguard.

What we don't store.

Social Security numbers
No field exists for one anywhere in the system, and tax forms like a W-9 are turned away at upload. We don't collect them and we have nowhere to put them.
Bank credentials
Stripe holds bank details and gives us a reference in their place. We never see a full account or routing number.
Full card numbers
Tenants type card details into Stripe's own secure form. The numbers never reach us.
Government ID images
There is no ID document type to file one under, and we don't use them for automated identity checks.

The safest place to keep sensitive data is somewhere you aren't. Most of the security work here was deciding what not to hold.

Your data is not training data.

We do not use your data, your tenants' data, your leases, or your payment records to train AI models. Not ours, not a vendor's.

Rentarina AI reads your data to answer your questions and draft your messages. Those requests run under business agreements with our AI provider that don’t allow training on your data. Nothing you put into Rentarina makes a model smarter.

What the AI can touch.

No message Rentarina AI drafts reaches a tenant until you’ve read it and pressed send. In Ask, the only changes it can prepare are resolving a maintenance request and recording an off-platform payment, and neither is written until you confirm.

Two things run without that step. It sorts new maintenance requests by category and priority. And it reads expiry dates off the documents you upload and marks them as they come due.

Anything a tenant writes is treated as something to read, never as an instruction to follow. Every AI request is logged against your account.

Who processes your data.

StripePayments, payouts and identity verificationSOC 2 Type 2, audited annually · public SOC 3
VercelApplication hosting and file storageSOC 2 Type 2 · ISO 27001:2022
NeonDatabase hostingSOC 2 Type 2 · ISO 27001 · ISO 27701
ClerkSign-in and account securitySOC 2 Type 2 since 2022
AnthropicAI-assisted featuresSOC 2 Type 2 · ISO 27001:2022 · ISO 42001:2023 · public SOC 3
ResendEmail deliverySOC 2 Type 2
SentryError monitoringSOC 2 Type 2 · ISO 27001
UpstashRate limiting — receives visitors' IP addresses and account identifiers as short-lived counters—
SignWellLease e-signatures — receives the names and email addresses of the tenant and landlord signers and the lease documents, and records a signing audit trail including IP addresses—

SOC 2 reports are confidential by design — there's no public registry for any vendor, ours included. Each vendor above with an attestation listed publishes a trust center and releases its report under NDA. Stripe and Anthropic also publish public SOC 3 summaries anyone can read.

This is the complete list. Not a sample, not the notable ones. We tell you before it changes.

Questions your CPA, attorney, or insurer would ask? legal@rentarina.com