Privacy, explained clearly

Rentra provides property management tools for hotels, short stays and apartments. Account and support information is used to operate the service. Property operators manage the guest and tenant information they enter and decide who in their workspace can access it.

For a request about a stay or tenancy, contact the property operator. For account or platform privacy questions, use Rentra support or hello@rentra-app.com.

Account information includes your name, email, optional phone number, password hash, language and settings. Workspace records include properties, rooms or units, guests or tenants, stays, leases, tasks, notes and recorded financial movements.

Property, room and unit photos and their descriptions are stored in your workspace. Uploaded photos are resized and stripped of embedded location and camera metadata; originals are not retained. Team access follows property permissions. An active guest arrival link also shows the relevant room or property cover photo.

A guest arrival form asks for name and email. Phone number and expected arrival time are optional. Private staff notes are kept separate from the information shown through the arrival form.

Support requests include the message and contact email you submit. A screenshot and the displayed device details are included only if you choose them and confirm the request.

Information is used to provide the account and workspace services requested, manage access, maintain booking and rent records, and respond to support or data requests. Authentication and abuse-prevention records help protect the service.

Account and service processing supports the requested service and contractual relationship. Security and abuse prevention support legitimate operational interests. Optional product analytics is based on your consent. A property operator is responsible for identifying the appropriate basis for the guest and tenant records they manage.

Hosting and database services store and serve Rentra’s records. When transactional email is configured, Resend processes information needed to send those messages. When optional analytics is configured and you accept it, PostHog receives the limited analytics events described below.

Team members can access records according to their role and assigned properties. Private calendar exports, arrival links and support links grant access to the information covered by that link, so share them only with the intended recipient. Payment tracking records money movements; it does not collect card details or transfer money.

Optional analytics remains off until you accept it on this browser. Accepting and rejecting are equally available, and you can withdraw consent using the controls below without losing access to core features.

Analytics uses permitted screen names and limited device information. Private links, record identifiers in URLs, query strings, guest details and support conversations are excluded. Automatic click capture, session recordings and identified user profiles are disabled. Analytics identifiers are held in memory for the current page session.

Essential browser storage supports sign-in, security, language and interface preferences. Your analytics choice is stored for 180 days, after which the app asks again.

Workspace records remain available while the account is active, subject to the actions taken by its operator. Removing a guest with booking history anonymizes the contact rather than deleting the associated bookings.

Closing an account disables access. Submit a data request for deletion or anonymization; records subject to applicable retention obligations may need to be kept. Closing the account and submitting a data-erasure request are separate actions.

Workspace export downloads require owner access and expire after 24 hours. Expired files are removed during cleanup. Attached tenant documents are downloaded separately from tenant profiles.

Photo details are included in workspace exports. Download processed photos separately from each gallery. Removing a photo, or its property, room or unit, removes it from the active database.

Private support links expire after 30 days. Requests created while signed in remain available to the account that created them. This access period is not a promise that support content is erased on the same date.

Depending on applicable law and the circumstances, you may request access, correction, erasure, restriction or portability, object to processing, and withdraw consent where consent is used. You can also raise a concern with your data protection authority.

Use the Privacy or data request topic in support. Describe the account or records involved without sending a password or private access token. Identity or authority may need to be verified before records are disclosed or changed. Requests involving records managed by a property operator may need that operator’s involvement.

Optional two-step sign-in uses an encrypted authenticator secret and one-use recovery codes stored as hashes. Security settings show browser and desktop session labels and recent activity, and let you revoke sessions. Device labels are inferred from the browser, not verified location or device identity.

Passwords are stored as hashes. Server-side checks control access to workspace records. Use a unique password and review who can access your properties. Public forms do not grant access to the rest of a workspace.

A private support link allows its holder to read and reply to that request until it expires. Avoid including passwords, card details, or private links in support messages and screenshots.

This page describes the current service and privacy controls. Review the update date when checking for changes. Consent choices can be changed at any time below.

Contact Rentra through Support or hello@rentra-app.com for questions about this page.