Privacy Notice

• Visitors to rltr.homes, including people who send us a message or a "Get started" request.
• Members of an agency who sign in to the RLTR application: owners, admins, agents and assistants.
• End customers: the leads, clients, signers and callers whose details members keep in RLTR. For that information RLTR acts on the agency's instructions; the agency decides what is collected and why. Section 11 explains what that means for you.

rltr is operated by One Two Spark, Co., a Delaware corporation. Contact us at hello@rltr.homes. Capitalized terms have the meaning given in the Terms of Service.

From visitors

Whatever you type into the contact form or the "Get started" dialog (name, email, phone, agency, message), the page you sent it from, and standard server logs (IP address, browser, time). The marketing site sets no analytics or advertising cookies.

From members

• Account details: name, work email, password (stored only as a salted hash), role, agency, profile photo, time zone and notification preferences.
• Billing details: billing contact and payment records if you enter a paid agreement with us. Automated subscription billing is not currently enabled. We do not ask you to store payment card numbers in rltr.
• Connected services: when you connect a mailbox, calendar or phone number we store the credentials or tokens needed to use it, encrypted, together with the emails, calendar events and call details that the connection brings in.
• Usage: sign-ins and sessions, actions taken in the app (who changed a record and when), calling activity, errors and performance data.

About end customers (Customer Data)

Contact details (name, phone numbers, email, address), lead source and status, contact tags, notes, the timeline of calls, emails and appointments, deals and property interests, tasks, documents uploaded for a transaction and electronic signatures, call outcomes and, where an agency enables it, call recordings and voicemail messages. Agencies agree not to put Social Security numbers, payment card numbers, health, biometric or children's data into RLTR.

• Directly from you, when you register, invite someone, type a note or fill in a form.
• From files members import, such as CSV lead lists.
• From services members connect: their mail provider (Google, Microsoft or an IMAP/SMTP server), calendar feeds.
• From the telephone carrier that connects calls: numbers dialled, call status and duration, and recordings where enabled.
• Automatically, from your browser and our servers, as described under cookies and usage.

• To provide the Services: show your records to the right members, send and receive the emails, calls, documents and reminders you ask for, route leads, keep timelines and reports accurate.
• To run your account: verification and password-reset emails, invitations, billing, receipts and notices about changes.
• To support you: answer questions, investigate problems you report and, with your permission, look at the records involved.
• To keep RLTR safe: detect abuse, fraud and unauthorized access, enforce our terms and the calling safeguards, and comply with carrier requirements.
• To improve RLTR: understand which features are used and where the app fails, using usage data and information that does not identify an agency or end customer.
• To comply with law and to protect our rights and yours.

We do not use Customer Data to market to your clients, we do not sell personal information, and we do not use your clients' data to train machine-learning models.

• Your agency. Agency access follows the server-enforced permissions and assignment rules. A private mailbox is visible only to its owner. A mailbox owner may explicitly share an email thread with a contact; that shared copy is visible to members permitted to access the contact.
• Service providers who process data for us under contract and only on our instructions: our hosting provider (Render, with our configured application and database region in Frankfurt, Germany) for the application, database, file storage and backups; our telephone carrier for calling; our email delivery service for account emails; and font files loaded from Google Fonts when you visit the site.
• Services you connect. When you connect a mailbox or calendar, data flows between RLTR and that service as the connection requires.
• Recipients you choose. The people you call, email or send documents to receive what you send them.
• Law and safety. When required by law, subpoena or court order, or when we believe in good faith it is necessary to protect someone's safety or to protect RLTR against fraud or abuse. Where allowed, we tell the agency first.
• A change of ownership. If RLTR is acquired or merges, data may transfer to the new owner under this notice; we will tell you before any materially different use.

We do not sell or rent personal information and we do not share it with third parties for their own marketing.

Connecting Google is optional. With your authorization, rltr accesses your verified email address, mailbox folders and messages, including senders, recipients, subjects, message bodies and attachments. It stores synchronized email data and encrypted authorization tokens on its backend to display your inbox, search your messages, manage drafts and read state, send email, and perform message actions you request. Gmail access uses IMAP/SMTP and requires the full-mail scope https://mail.google.com/. We do not ask for your Google password.

Calendar access is requested separately when you choose to connect a calendar. We use event details, such as titles, descriptions, times and attendees, to display and synchronize calendar events and the changes you request. Gmail access alone does not authorize calendar access.

Private email is not automatically shared with your agency. Only email threads you explicitly share with a contact become available to members authorized to access that contact. We transfer Google data only to provide the features you authorize, for security, to comply with law, or as part of a business transfer with your explicit prior consent. We do not sell Google data, use it for advertising, credit decisions or training general-purpose AI models, or use it for unrelated analytics.

Our personnel do not read Google data unless you affirmatively agree to access to specific data, access is necessary for security or legal obligations, or the data is aggregated and used for internal operations as permitted by Google's policy. rltr's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. These restrictions take precedence over the general sharing and aggregated-information provisions in our policies and terms.

You can disconnect a mailbox in rltr or revoke access in your Google Account. Disconnecting removes its stored credentials and private synchronized email copies; email threads previously shared with contacts remain agency records until deleted. Disconnecting does not delete mail in Gmail. To request deletion of retained copies or calendar data, contact hello@rltr.homes; agency-owned records may also require the agency's instructions, subject to applicable law.

The application uses browser storage to keep you signed in and to remember interface preferences such as a collapsed sidebar or your calling defaults. These are strictly necessary and stay on your device. The marketing site uses no cookies of its own, no analytics scripts and no advertising pixels. Because we do not track visitors across sites, there is nothing for a "Do Not Track" or "Global Privacy Control" signal to switch off, and we treat such signals as a request not to be tracked in any case.

The configured Render application and database region is Frankfurt, Germany. Each agency's records live in their own isolated database schema; a shared directory holds only the agency list, memberships and invitations. Uploaded files are stored on a persistent disk under agency-specific paths. Connected-service credentials are encrypted with a key kept separately from the database. Connected providers and their service providers may process information in other countries, including the United States. We handle international transfers in accordance with applicable requirements.

• HTTPS everywhere; email and calendar connections require TLS and certificate checks.
• Passwords stored as salted hashes; sign-in tokens that are revoked when a password changes, a member is removed or we detect risk; rate limits on sign-in and public endpoints.
• Agency membership checked on every request; records filtered by role and assignment on the server, not only in the browser.
• Encrypted storage of integration credentials; uploaded files inspected for type before preview; dangerous formats refused.
• Backup availability and retention depend on our hosting configuration. Do not rely on rltr as the only copy of important documents.
• Access to production limited to the people who operate RLTR, with secrets kept out of code and chat.

No service can promise perfect security. If we learn of a breach affecting your information we will notify the agency owner without undue delay and in line with applicable law.

• While your agency is active, we keep Customer Data for as long as your members keep it; owners and admins can delete records at any time, and deleted contacts are scrubbed to a placeholder that keeps only the fact that a record existed.
• After an account closes, contact us to arrange an export and deletion of its records, files and credentials, except where we must keep something for legal, tax or dispute reasons.
• Backups, where available, may retain deleted information until they expire under the hosting retention schedule; retained copies are not used for ordinary service operation.
• Visitor messages are kept for up to 24 months unless a conversation with you continues.
• Account and billing records are kept for as long as required by tax and accounting law.

Members can see and update their profile in the app, change their password, disconnect mailboxes and calendars, and ask their agency owner to change their role or remove them. Owners can use available export and deletion tools or contact us for assistance.

Depending on where you live (for example California under the CCPA/CPRA, or Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states with comprehensive privacy laws), you may have the right to know what personal information we hold about you, to receive a copy, to correct it, to delete it, to opt out of sale, sharing or targeted advertising (we do none of those), and not to be discriminated against for exercising these rights. To exercise a right, email hello@rltr.homes from the address on your account or describe how we can verify you; an authorized agent may act for you with written permission. We respond within 45 days, extendable once where the law allows, and we will tell you if we cannot act on a request and why. If you disagree with our decision you may appeal by replying to our response, and you may contact your state attorney general.

Marketing email from RLTR about RLTR carries an unsubscribe link. Account emails (verification, resets, invitations, billing) are sent regardless because the Services need them.

If a real estate agency keeps your information in RLTR, that agency decides why it was collected, who may see it and how long it is kept, and it is responsible for honouring your requests, including not to be called or emailed. RLTR processes that information for the agency and does not use it for its own purposes. Please direct requests about your information to the agency; if you do not know how to reach them, write to us and we will pass the request on, or act ourselves where the law requires it. Agencies remain responsible for applicable calling and email consent, opt-outs and do-not-call obligations; software safeguards do not replace those obligations.

RLTR is for professionals and is not directed to children. We do not knowingly collect information from anyone under 16, and agencies agree not to store information about minors. If you believe a child's information has reached us, contact us and we will delete it.

We will update this notice when our practices or the law change and will update the effective date at the top. For material changes, we will notify agency owners before the changes take effect, except where urgent legal or security requirements apply. New uses of Google data require the disclosures and consent required by Google's policy.

Privacy questions and requests: hello@rltr.homes · rltr.homes/contact. One Two Spark, Co., a Delaware corporation.