01Who we are
SimonOps ("we", "us") builds lead-response automation for real estate brokerages. This policy explains what information we access when a client connects a Google account to our service, why we access it, and what we do with it. We operate from Italy and are the controller of the data described below.
02What we access
When a client connects a Google account, we ask for permission to use only what the service needs:
- Gmail — sending only: permission to send replies from the client's address. We do not read, search, label or delete anything in the client's mailbox, and we do not ask for permission to do so.
- Google Calendar: only if the client turns on appointment booking — their agents' availability, and the ability to create appointments.
- Google Sheets: the spreadsheets the client chooses to share with us, such as a property listing sheet or a lead log.
Lead inquiries reach us because the client forwards their lead alerts to an address we provide, not because we read their mailbox. Replies from leads arrive at that same address and are passed on to the assigned agent. We process the personal details those messages contain, such as a lead's name, email address, phone number and search criteria.
03How we use it
We use this data only to provide the service the client has asked for: reading the lead alerts forwarded to us, drafting and sending replies, matching leads to listings, booking appointments, alerting the client's agents, following up with leads that go quiet, and producing summary reports for the client.
04Google user data: what we access, use, store, share and delete
SimonOps'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.
What we access. SimonOps asks for one Google permission: https://www.googleapis.com/auth/gmail.send. It lets us send an email from the Gmail address the client connects. It does not let us read, search, label, modify or delete any message in that mailbox, and we do not ask for any permission that would.
How we use it. We use that permission only to send the first reply to a new lead, from the assigned agent's own address, about the home the lead asked about. We do not send anything else from the connected account.
What we store. We store the OAuth token, encrypted, so that replies can be sent, and we record the time each reply was sent. We do not store or archive any other data from the connected Google account.
Who we share it with. We do not sell Google user data, use it for advertising, use it to build or train AI or machine-learning models, or transfer it to anyone else, except where the law requires it. People at SimonOps do not read Google user data unless the client has asked us to (for example, to investigate a problem), where it is necessary for security or abuse investigation, or where the law requires it.
How long we keep it and how to delete it. When a client disconnects their account or stops the service, we delete the stored token immediately and all other data within 30 days. Anyone can revoke our access at any time in their Google Account, under Security, Third-party access, or ask us to delete their data by writing to simon@simonops.world.
05Who processes the data with us
We rely on a small number of service providers, each of which handles data only to deliver the service:
- AI language model provider (OpenAI): the text of an inquiry and the relevant listings are sent to generate a reply or extract details. We use it through its API for this purpose only.
- Server hosting (Hetzner, Germany): our automation software runs on servers located in the European Union.
- Telegram: short alerts, such as the name and search criteria of a new high-priority lead, may be sent to the client's chosen chat.
We do not share Google user data with anyone else, except if the law requires it.
06Storage and retention
Access tokens are stored encrypted on our servers. Message content is processed to complete each task and is not kept in a separate archive of our own. Execution logs keep only what is needed to run and troubleshoot the service, and we delete them after a limited period. Lead records live in the client's own spreadsheets or CRM.
07Your choices
- Revoke access at any time in your Google Account under Security, Third-party access. Doing so stops our access immediately.
- Ask us to delete any data we hold about you or your leads by writing to the address below. We will confirm once it is done.
If you are in the European Economic Area, you also have the rights to access, correct, restrict and port your personal data, and to complain to your local data protection authority.
08Security
Connections use HTTPS, credentials are stored encrypted, and access to our systems is limited to the people who operate the service. No system is perfectly secure, so if we learn of a breach affecting your data we will tell you promptly.
09This website
simonops.world does not use cookies or advertising trackers. To understand how many people visit and which pages they read, we use Cloudflare Web Analytics, a privacy-first tool that sets no cookies, does not track you across sites and does not build visitor profiles. It records aggregate data such as page views, referring site, country and device type.
The site is hosted by Netlify, which processes technical data such as IP addresses to deliver the pages and keep them secure. Fonts are served by Bunny Fonts, a European provider that does not log visitors. If you book a call through our scheduling link, the booking is handled by our scheduling provider (Cal.com) under its own privacy policy.
10Changes to this policy
If we change this policy, we will update the date at the top and, for material changes, notify our clients directly.
11Contact
Questions or requests:
simon@simonops.world →