Really for insurance agencies
Privacy Policy
This Privacy Policy explains how Really handles personal information in its services for insurance agencies: the agency console at optimization.real-y.io, the AI chat and voice assistants on agency websites and phone lines, agency websites we build, and the Gmail and Outlook inbox features. Really is provided by Yuval Chen, based in Israel ("we", "us" or "our"). Questions? Write to support@real-y.io.
The short version
- We work for insurance agencies. When their customers chat, call or fill in a form, we handle that information on the agency's behalf and under its instructions.
- If an agency connects its Gmail or Outlook inbox, our access is read-only. We never send, change, move or delete email.
- We turn new quote requests in a connected inbox into leads for the agency, and we answer the agency staff's own questions about their email. We don't keep copies of email bodies.
- We don't sell personal information, we don't use it for advertising, and we don't use email data to train AI models.
- Our use of data from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements (section 5).
- An agency can disconnect its inbox at any time in Configurations → Inbox.
1. Who we are and our role
Really provides software to independent insurance agencies. The service is provided by Yuval Chen, based in Israel. You can reach us at support@real-y.io.
For the agency's customers (people who chat with, call, email or send a form to an agency), the agency decides why and how their information is used, and we process it on the agency's behalf. If you're one of these people, the agency's own privacy notice applies too, and you can contact the agency directly.
For agency staff who use the console, we are responsible for their account information.
This policy doesn't cover the Really dating app, which has its own privacy policy.
2. Information we handle
2.1 Agency staff accounts
- Name, email address, role, and the organizations and agencies you're assigned to. Sign-in is handled by Google Firebase Authentication.
- How you use the console, for example the pages you open and the actions you take, to support you and improve the product. We use Mixpanel for this, including session recordings. Content that comes from a connected inbox is masked in those recordings.
2.2 Agency customers (on the agency's behalf)
- Website chat: the messages exchanged with the AI assistant, and the contact and quote details the person provides.
- Voice and phone calls: the caller's phone number, the call recording and its transcript, and an AI summary of the call.
- Website forms and quote applications: the answers given, such as name, contact details, business or property details, and the coverage requested.
- Quotes: when an agency asks for a quote, we send the application details to the insurance carrier's portal on its behalf and store the result.
- Basic technical data from the website widget, such as the page it was used on and the time.
2.3 Insurance agencies we contact
To offer Really to insurance agencies, we collect business contact information that agencies publish themselves or that is in public licensing records: the agency's name, website, business phone and email, and the owner's or licensed agent's name. We use it only to contact the agency about our services. To stop hearing from us, reply to any of our emails or write to support@real-y.io.
2.4 Visitors to real-y.io
When you visit our own website, real-y.io, we use cookies and similar technology to see how the site is used: the pages viewed, how visitors found us, and the type of device and browser. We use Google Analytics for this. We also use RB2B, which may match a visit from the United States to a business profile, such as your name, job title, company and LinkedIn profile, so that our sales team can follow up about our services. We don't use this for advertising. To opt out, write to support@real-y.io and we will delete what we have about your visit. You can also block cookies in your browser.
3. Connected Gmail and Outlook inboxes
An agency can connect a Gmail or Outlook mailbox in the console. Connecting is always the agency's choice and needs the mailbox owner's consent on Google's or Microsoft's own screen.
3.1 What we access
- Google: read-only access to Gmail (the
gmail.readonlypermission) and the account's email address. - Microsoft: read-only access to mail (the
Mail.Readpermission), the basic profile and the email address.
We can't send, reply to, forward, change, move or delete any email.
3.2 What we do with it
- New quote requests become leads. About every five minutes we check for mail that arrived after the inbox was connected. Newsletters, automated mail and mail sent from the mailbox itself are skipped without being analysed. Each remaining message is analysed by an AI model to decide whether it is a request for an insurance quote. If it is, we create a lead for the agency with the sender's name, phone number and email address, the type of insurance, the subject line, a short summary, and a link to open the email in Gmail or Outlook. Older mail is never imported.
- The Assistant answers staff questions. When an agency user asks a question, the Assistant searches that agency's connected mailboxes and reads the messages it needs to answer, then shows the answer with links to those emails. Each user's questions and answers are not stored by us.
3.3 What we store
- For each message we check: the sender, subject, date, a link to it, and our decision (for example "quote request" or "other"). We don't store email bodies or attachments.
- The leads created from quote requests, as described above.
- The connection itself: the mailbox address and a refresh token that lets us keep reading. Refresh tokens are encrypted with AES-256-GCM before they are stored.
- Counts of AI processing used (tokens), to calculate each agency's costs.
3.4 Disconnecting
An agency can disconnect an inbox at any time in Configurations → Inbox. We then stop reading it and delete its stored tokens. For Gmail we also revoke our access at Google. The mailbox owner can also remove our access at any time in their Google account permissions or Microsoft account settings.
4. How we use information
- To provide the service the agency asked for: the website assistants, call handling, leads, quotes, the inbox features and notifications to the agency's staff.
- To support agencies, fix problems and keep the service secure, including preventing abuse.
- To calculate usage and costs per agency.
- To meet legal obligations.
We don't sell personal information, and we don't use it for advertising.
5. Google and Microsoft user data
Really's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We apply the same rules to data from Microsoft. In particular:
- We use email data only to provide and improve the user-facing inbox features described in section 3.
- We don't transfer it to others, except as needed to provide those features (for example to our AI provider, see section 6), to comply with the law, or as part of a merger or sale with the same protections.
- We don't use it for advertising, and we don't sell it.
- We don't use it to develop, improve or train generalized AI or machine-learning models.
- No person reads it, unless the agency asks us to for support, it's needed for security or abuse investigation, or the law requires it.
6. Service providers and sharing
We use these providers to run the service. They may process personal information only on our instructions:
- Google Cloud and Firebase: hosting, sign-in, file storage (such as call recordings) and the Gemini AI model for analysing calls.
- MongoDB Atlas: our database.
- OpenAI: the AI models behind the chat and voice assistants, the analysis of inbox messages, and the Assistant. Under OpenAI's API terms, this data is not used to train their models, and it may be kept for up to 30 days for abuse monitoring.
- Twilio: phone calls.
- Google Workspace: email notifications.
- Mixpanel: product analytics for the console (agency staff only; inbox content is masked).
- Google Analytics: visit statistics for real-y.io.
- RB2B: identifies the businesses and professionals that visit real-y.io (section 2.4).
- Slack: internal alerts to our team about call activity, to help us support agencies.
We also share information with insurance carriers when an agency asks for a quote, and with the agency itself, which receives the leads, quotes, calls and messages from its own customers. We may disclose information if the law requires it, or to protect the rights and safety of our users and others.
7. International transfers
Our servers and most of our providers are in the United States. Where the law requires it, we rely on appropriate safeguards for these transfers, such as the providers' standard contractual clauses.
8. How long we keep it
- Agency staff accounts: while the account is active, and for a short time after it is closed.
- Agency customer information, leads and quotes: for as long as the agency uses Really, unless the agency deletes it sooner.
- Inbox connections: tokens are deleted when the inbox is disconnected. Message records and leads are kept until the agency deletes them or stops using Really.
- When an agency stops using Really or asks us to delete its data, we delete or anonymise it within 90 days, unless the law requires us to keep it longer.
9. Your rights and choices
Depending on where you live, you may have the right to see the information we hold about you, to correct or delete it, and to object to or limit some uses. If you're an agency's customer, please contact the agency first; we'll help it answer you. Agency staff and anyone else can write to support@real-y.io. We'll answer within 30 days, and may ask you to confirm your identity first.
If you're in Israel: you have the rights given by the Privacy Protection Law, 5741-1981, and can complain to the Privacy Protection Authority. If you're in the EEA, the UK or Switzerland: you have the rights given by the GDPR (or UK or Swiss law), and can complain to your local data protection authority. If you're in the US: you may have rights under your state's privacy law. We don't sell or share personal information for targeted advertising.
10. Security
We protect information with encryption in transit (HTTPS/TLS), encryption of inbox tokens at rest, access controls that limit each user to their own organization and agencies, and providers with strong security programs. No method is completely secure. If a security incident puts personal information at risk, we'll notify the affected agencies and the authorities as the law requires.
11. Children
Really is a business service and isn't meant for children. We don't knowingly collect information from children.
12. Changes and contact
We'll update this policy when the service or the law changes, post the new version on this page with a new date, and tell agencies before significant changes take effect.
For privacy questions and requests, contact Yuval Chen (Really), Israel, at support@real-y.io.