Draft — under legal review. This text is a draft. It is not in effect yet, and parts in [square brackets] are still to be filled in.
Privacy Policy
1. Who this is for
This policy explains how [Radah legal entity name] ("Radah") handles personal information. It covers two groups:
- Our customers and their people: agents, teams and brokerages who use radah.app, and the people they invite.
- Consumers: home buyers, sellers, renters and other people who visit a website Radah hosts for a real estate professional, send an inquiry, create an account there, or exchange email with an agent or the agent's AI assistant.
Two roles. For customer accounts, billing and our own marketing, Radah decides how the information is used. For consumers' information, Radah works on behalf of the agent or brokerage whose website or workspace it is (a "service provider" or "processor"). That professional decides how your information is used and their own privacy notice applies too. If you are a consumer, the fastest way to make a request is to contact that professional; you can also contact us (section 10) and we will pass it on and help them answer.
2. What we collect
| Who | What | From where |
|---|---|---|
| Customers and their people | Name, work email, phone, role, licence number and state, MLS member and office ids, profile photo and bio, sign-in identifiers | You, your broker or office manager, Google sign-in |
| Customers | Billing contact, plan, payment status (card details stay with our payment processor) | You and our payment processor |
| Customers' working data | Contacts and their details, notes and timeline, deals and documents, e-signature records, plans, commissions and expenses entered by the office, messages | You, imports you run (for example CSV), integrations you connect |
| Consumers | Name, email, phone and message when you send an inquiry, request a showing or valuation, or create an account; saved homes and searches; household members you invite | You |
| Consumers | Email you exchange with an agent's conversation address, including replies drafted by the agent's AI assistant | You and the agent |
| Website visitors | A random browser id in a first-party cookie (consumer_vid, 1 year), the agent page you came from (radah_agent), and the homes you view, save, filter and ask about, recorded with facts about the home only (price, type, size, town, approximate location) | Your browser on that website |
| Everyone using our apps | Device and log data (IP address, browser, pages, errors) and, on some pages, a masked session recording used only to fix problems (typed text and sensitive forms are masked) | Your browser |
| Public and licensed sources | MLS listing data (which may include listing agents' names and contact details), public licence records (for example New York Department of State open data), and reviews you or the agent connect from review sites | MLS data providers under licence; public records; review sites |
We do not ask for Social Security numbers, bank or card numbers in the CRM, or protected-class information.
3. How we use it
- To run the Service: sign-in, workspaces, the CRM, websites, email, e-signature, reminders and billing.
- AI features (RADA). We send an AI model only the inputs a feature needs, for example the email thread and the facts about one home to draft a reply. RADA's drafts are checked for fair-housing topics and facts before an agent sees them. RADA does not make decisions that have legal or similarly significant effects on consumers (it does not approve, deny, price or rank people).
- Home suggestions on websites. Your browsing builds a simple taste profile (price range, size, home types, towns) from the last 90 days to show "You might like" homes. It never uses information about who lives in an area.
- To secure the Service, prevent fraud and abuse (including rate limits), fix problems and comply with law.
- To tell customers about the Service. Consumers receive only messages from the professional they contacted.
We do not sell personal information, do not share it for cross-context behavioral advertising, and do not put ad-network trackers on agents' websites.
4. Who we share it with
- The professional you dealt with, and the people in their workspace.
- Service providers that host or process data for us under contract (list in section 5).
- MLSs and data providers only as their licences require (for example usage reports).
- Other brokerages, only with your written consent (Radah Network referrals: the consent says what is shared and with whom, and expires after 90 days).
- Legal and safety: when the law requires, or to protect people, the Service or our rights.
- Business transfer: if Radah is sold or merged, under this policy's protections.
5. Service providers (sub-processors) by category
| Category | What they do | Data location |
|---|---|---|
| [Database and storage provider] | System of record for all workspace data | United States |
| [Application hosting provider] | Runs radah.app, the API and agents' websites | United States [and global edge network] |
| [Sign-in provider] | Google sign-in | [United States] |
| [Email delivery provider] | Sends and receives system email and lead conversations | United States |
| [Payment processor] | Customer subscriptions and payments | United States |
| [AI model provider] | Drafts and parsing for RADA features | United States |
| [E-signature provider] | Document signing | [ ] |
| [Product analytics and error tool] | Staff-only debugging, masked session recordings | [ ] |
| [Maps provider] | Maps on websites and listings | [ ] |
| [MLS data providers] | Listing data feeds (they send us data; we report usage as licences require) | United States |
| [Review platforms] | Reviews an agent connects | [ ] |
6. How long we keep it
- Workspace data: while the customer's workspace is active, then for the export and deletion periods in the Terms ([30] days to export, deleted within [60] days, backups within [35] days after). A brokerage may tell us to keep records longer to meet its own record-keeping duties.
- A consumer's email conversation with an agent: as long as the agent keeps the contact; deleted with it.
- Website browsing events: count toward suggestions for 90 days; [deleted after ___].
- Review text from some review sites: refreshed or removed within the period the site requires (for example 30 days).
- Network consents and referral records: as the brokerage's records require; buyer-search consents expire after 90 days.
- Logs: [__] days.
7. How we protect it
Encryption in transit; workspace separation enforced in the database; sensitive fields (for example message bodies, pay details and model keys) sealed with additional encryption; staff access only for support or security, each time logged; rate limits on public forms. If a breach affects your information we will notify the professional responsible and, where the law requires, you and regulators (for example under New York's SHIELD Act).
8. Your choices and rights
Depending on where you live, you may have the right to:
- know or access the personal information held about you, and get a copy;
- correct it;
- delete it;
- opt out of sale, sharing for targeted advertising, or profiling with significant effects (we do none of these);
- limit the use of sensitive information (we do not collect it for inferences);
- appeal a decision on your request; and
- not be treated differently for using these rights.
These rights come from state laws such as California's (CCPA as amended), and comprehensive privacy laws in [Virginia, Colorado, Connecticut, Texas, Oregon and other states], each with its own thresholds. We honor the requests these laws give you whether or not a law strictly applies. We verify requests before acting on them. An authorized agent may ask for you where the law allows.
Email choices. Reply "stop" to an agent's conversation email and nothing more is sent. Every marketing email from Radah has an unsubscribe link.
Removal at your request. You may ask the agent's office to remove your details. The office removes them: your contact details and notes, your messages and inquiries, and your account on its website. Transaction records the law requires the office to keep (for example a signed contract and the deal's documents) are kept.
Cookies. Agents' websites use first-party cookies only (section 2). Clearing your browser's cookies for the site starts you fresh. We do not respond differently to "Do Not Track"; [we honor Global Privacy Control signals as an opt-out of sale or sharing, though we do neither].
9. Children
The Service is for adults doing real estate business. We do not knowingly collect information from children under 13 [16].
10. Contact
[Radah legal entity name], [postal address], [privacy@radah.app]. For consumers: also contact the agent or brokerage whose website or email you used.
11. Changes
We will post changes here with a new date and, for material changes, email customers [30] days ahead.
12. Google user data
An agent may connect their own Google account to Radah and turn on any of three features. Radah asks Google only for what the feature they turn on needs, at the moment they turn it on.
- What Radah accesses. Calendar: the events on the agent's own Google Calendar (their title, time, place, description, number of guests and a link to open them in Google), whether the agent is busy or free at given times, and the events Radah itself creates on its own "Radah" calendar inside the agent's Google Calendar (showings, appointments and the deal dates the agent picks). Radah only reads the agent's own events and never changes them, and cannot read anyone else's calendar. Gmail: Radah can send email the agent approves, or allows to go out on its own, from the agent's Gmail address. Radah cannot read, search or delete anything in the agent's mailbox. Google Drive: only the files the agent picks to attach in Radah and the files Radah saves for the agent in a "Radah" folder. Radah cannot see the rest of the agent's Drive.
- Why. Calendar: to keep the agent's Google Calendar up to date with their Radah schedule, to show the agent their own Google events (with their titles and details) next to their Radah appointments, and to offer clients tour times when the agent is free. Gmail: so messages the agent approves come from their own address and appear in their Sent folder. Drive: to keep deal documents and signed papers in the agent's own Drive and to link files the agent chooses to a client, listing or deal in Radah.
- What Radah stores. A sealed (encrypted) Google token for the connection, the Google account's id and email address (shown only to that agent), which features are on, the ids of the calendar events Radah created, and for Drive the file ids, names and links of files the agent attached or Radah saved. The agent's own Google events and their busy or free times are read when the agent opens their calendar, held in memory for a few minutes at most, and never saved in Radah's database or written to logs. Radah keeps its own record of each email it sent (as it does for every email it sends), never a copy of the mailbox.
- Who sees it. The agent. The agent's own Google events (titles and details) are shown only to that agent, never to teammates, brokers, assistants or clients. People in the agent's workspace who may see a client, listing or deal in Radah see the name and link of a Drive file attached to it (opening the file still follows the agent's Google sharing), and the messages the agent approved, as with every Radah message. Radah staff cannot read Google data; support sees only whether a connection works. Google data is never shared with anyone else except as needed to provide these features (for example, Google itself) or when the law requires it.
- No advertising, no sale, no AI. Radah never uses Google data for advertising, never sells it, and never uses it to train or improve any AI model. Nothing from Gmail, Calendar or Drive, and nothing derived from it, is sent to an AI model.
- Keeping and deleting. Disconnecting Google in Radah revokes Radah's access at Google and deletes the stored token; the agent may also remove Radah's calendar. Links to Drive files can be removed at any time (the files stay in the agent's Drive). When an agent leaves a workspace or a workspace is closed, Radah revokes that agent's Google access and removes Radah's calendar. An agent can also remove Radah's access at any time in their Google Account settings.
- Limited Use. Radah's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.