Certified foundations
Our database, authentication, payments and storage run on providers with independent audits. Their reports cover their platform, not Rentesy.
Trust Center
Rentesy holds identity documents, leases, payment history and deposit records. This page shows where that data lives, who can reach it, what we do to protect it and how you can get it back.
Security questions: hello@rentesy.com
Overview
We would rather show you how the system works than ask you to trust a logo. The controls below are in place today. Where a certification belongs to a provider, we say so.
Our database, authentication, payments and storage run on providers with independent audits. Their reports cover their platform, not Rentesy.
Every organisation route checks a permission and an organisation scope. A missing permission is a refusal, not a default yes.
You can ask for a copy of your records, correct them or request deletion. AI actions wait for your approval.
Documents and contacts
The policies behind this page, plus the fastest way to reach us.
Compliance
These certifications belong to the named provider. They cover the provider's platform, not Rentesy. We do not present a provider's report as our own.
SOC 2 Type II
Database, authentication and managed Postgres
ISO/IEC 27001
Information security management
PCI DSS Level 1
Card and payment processing in India
PCI DSS Level 1
International card payments and AutoPay
Our own status
We do not present a provider's certification as our own. The controls we operate are described on this page, and we will publish our own report here when we have one.
Controls
Each group lists controls Rentesy operates, or controls a listed provider applies to our environment.
The platform our records and requests run on.
Who can see and change a record.
How sensitive fields and credentials are handled.
How requests and changes are checked.
How we see problems and record sensitive changes.
How the assistant stays inside your permissions.
This page lists controls, not a certification. If your team needs a control matrix or a vendor questionnaire, email hello@rentesy.com.
Subprocessors
These are the service providers that process data for Rentesy. We list the purpose, the data involved and the safeguard we rely on.
| Provider | Purpose | Data | Safeguard |
|---|---|---|---|
| Core platform | |||
| Supabase | Database, authentication and managed Postgres | Account, tenancy, lease, payment and document metadata | SOC 2 Type II and ISO/IEC 27001 |
| Vercel | Application hosting, serverless compute and AI Gateway | Request data needed to serve the app; prompts routed to the selected model | Encryption in transit; app functions in Mumbai |
| Cloudflare | R2 object storage for public assets and private documents | Property photos, avatars, portal branding, documents and personal files | Public bucket for display assets; private bucket has no public domain and is read through short-lived signed URLs |
| Payments and identity | |||
| Razorpay | Rent payments, merchant onboarding and AutoPay | Payment, payout and onboarding data | PCI DSS Level 1 |
| Stripe | International rent payments, AutoPay and manager subscriptions | Payment, payout and subscription data | PCI DSS Level 1 |
| Setu | PAN verification | PAN and the name returned by the verification API | Server-side only; identity results masked in the API |
| Zoho Sign | Lease e-signatures | Signer name, email, document and signature events | Hosted signing; tokens held server-side |
| Communications | |||
| Resend | Transactional email | Name, email address and message content | Server-side API only |
| MSG91 | SMS one-time codes and notifications | Phone number and OTP message | Server-side API only |
| Meta WhatsApp Cloud API | Tenant messaging over WhatsApp | Phone number and message content | Webhook signature verification |
| Analytics and AI | |||
| PostHog | Product analytics | Pseudonymous product usage events | EU cloud |
| Marketing site analytics, Ads and reCAPTCHA | Site usage and form challenge signals | Standard Google terms | |
| Cal.com | Demo booking | Name, email and booking slot | Booking data only |
| Better Stack | Uptime monitoring and status page | Check results and status page data | Status data only |
| OpenAI, Google, Alibaba | Super and tenant assistant inference, routed through Vercel AI Gateway | Prompt content and the records a tool returns for the requested task | No training on customer data; task-scoped records within the user's permissions |
Last reviewed 22 November 2026. If we add a provider that handles personal data, we update this page. Some providers process data outside India; our primary database is in Mumbai. Ask us for the current list before you sign.
Your data
You do not need a formal request to see most of your data. Managers can view it in the workspace and tenants can view it in the portal. For a copy, correction or deletion, email us.
Managers can open the workspace record. Tenants can see their lease, payments, documents and requests in the tenant portal.
Edit the record in the product, or email us if a field is locked. We may verify your identity before changing sensitive details.
Email hello@rentesy.com with the subject Data request. We provide a structured copy of the records we hold for you.
The account owner can email us to delete an account. We remove or anonymise records, except where tax, accounting, fraud prevention or other law requires retention.
If you are a tenant, your property manager is the primary controller of your tenancy record. Ask them first; we support their export and deletion requests.
If you manage a team, only the account owner can request deletion of the organisation.
Email a data requestAI privacy
Super answers from your records and proposes changes. It does not execute them on its own.
Super uses the same role and organisation checks as the rest of the app. It cannot see a record you cannot see.
Emails, work orders, lease changes and imports wait for a person to approve them.
Rentesy does not use customer data to train AI models. Requests are processed under the model provider's API terms.
Super can use Alibaba Qwen, OpenAI or Google Gemini models routed through Vercel AI Gateway. The tenant assistant uses OpenAI.
How a Super action happens
You ask
A question about a property, lease, tenant or task.
Super reads
Only records your role is allowed to see, returned by permission-checked tools.
Super proposes
A change appears as a card. Nothing is written yet.
You approve
Approval re-checks permissions, executes the action and writes an audit entry.
The model sees the records a permission-checked tool returns for the task you asked for, not your whole database. AI proposals and approvals are kept in an append-only audit log.
FAQ
Short answers first. Email hello@rentesy.com if you need the detail behind them.
The primary database is Supabase Postgres in Mumbai. Public display assets are stored in a public Cloudflare R2 bucket. Documents and personal files are stored in a separate private R2 bucket with no public domain. Some service providers process data outside India, and they are listed in the subprocessor section above.
No. Documents are stored in a private bucket with no public domain. Access is authorised per request and delivered through a short-lived signed URL. Public buckets are used only for display assets such as property photos and portal branding.
Inside your organisation, access follows the roles and record scopes your owner sets. Every route checks both a permission and your organisation, and fails closed when a grant is missing. Document downloads are checked and signed only after that. Rentesy engineers can access production systems to operate and support the service, but we do not sell your data or use it for advertising.
Manager document links open through the app and require a valid session and permission. The final object URL is short-lived. To share a document outside Rentesy, download it and send the file.
Only with the service providers listed on this page, with payment providers when you pay, and with authorities when the law requires it. We do not sell personal data.
Traffic is encrypted with TLS. Postgres and R2 encrypt data at rest. Card numbers are handled by Razorpay or Stripe, which are PCI DSS Level 1 providers, and Rentesy does not store card numbers. Payment proofs and other documents are stored in the private bucket and served through short-lived signed links.
The account owner can email hello@rentesy.com. We verify the request, delete or anonymise the data, and confirm when it is done. Some records may be retained where tax, accounting, fraud prevention or other law requires it.
We do not provide a support console for browsing tenant documents, and documents are not reachable from a public link. Production access is limited to the engineers who operate the service, and is used to run and troubleshoot it, not for marketing.
No. Rentesy does not use customer data to train AI models. Super reads records through permission-checked tools to answer a specific request, and write actions require your approval.
Email hello@rentesy.com with the subject Data request. We verify your identity and send a structured copy of the records we hold for you. Managers can already see most records in the workspace, and tenants can see their tenancy in the portal.
Not today. Supabase, which provides our database and authentication, reports SOC 2 Type II compliance and holds ISO/IEC 27001 certification. Those reports cover Supabase's platform. We do not present them as Rentesy certifications.
Email hello@rentesy.com with the subject Security report. Include the affected URL, a short description and the steps to reproduce it. Please do not test against another customer's data.
We can discuss a DPA or vendor questionnaire for your organisation. Email hello@rentesy.com with your requirements and the regions you operate in.
Security review
If your team needs a security review, a DPA or answers to a vendor questionnaire, email us. We will reply with what we can substantiate, including what we do not have yet.