Last updated 6 October 2026 · Ospry Suite Ltd, registered in the UK, company number 17455389, registered office 7 Walnut Way, Leicester, LE8 5TJ
Ospry’s application and primary database run on a cloud server operated by IONOS in the United Kingdom. We use a small number of other companies to run the service, some of them in other countries. Each one is listed here with what it actually does. We do not sell data, and we do not use your data or your clients’ data to train anything.
A cloud server operated by IONOS in the United Kingdom runs the application, its primary database, our search server, the page-speed checks, the osprysuite.com website and file storage (Cue photos, client photos, report archives). Account data, audit results, Cue records and encrypted credentials live here.
Generates text for Cue's replies to website visitors, content drafts, Ask Ospry, keyword briefings, suggested page titles and descriptions, and demo-site wording. A request can contain business details, public website content, notes and facts you entered, Site Brain passages, audit or keyword figures, and what a visitor typed into Cue, as typed, including contact details they chose to give, with what that visitor said on an earlier visit in the past 60 days. Data from Google APIs is not included. Runs on our account unless you connect your own key, in which case it runs under your own Anthropic terms. Anthropic states API inputs and outputs are not used to train its models by default and are normally deleted within 30 days, subject to its contractual, safety and legal exceptions.
Takes the payments. Receives your name, email and billing address, and holds payment and invoice records; card details go straight to Stripe and never reach us. Stripe also acts as an independent controller for its own fraud and compliance checks.
Sends all our service email: sign-in and password messages, invitations, billing notices, chat, booking and escalation alerts, weekly summaries, client reports and monthly updates, and audit tool lead alerts. It carries the whole message: recipient, subject and body, including any visitor details in an alert.
HighLevel runs our own customer records: the name, email, country and marketing choice of everyone who signs up (whether or not they agreed to marketing), waitlist entries, and the email and findings from our own unbranded audit tool. Here we are the controller and HighLevel acts for us.
Custom Search (a keyword and a country), PageSpeed Insights and the Chrome UX Report (the address of the site being checked) and search suggestions (a keyword and a language or country), each used only when it is set up on our server. These send search terms and web addresses, not personal data about you.
Rank checks and competition reads send search queries (a keyword and a place) through our own search server, which runs on our server, to public search engines. No personal data is sent.
Place lookups from our server (a town and a country), and the map tiles shown on the area map, which your browser loads directly from OpenStreetMap, so it sees your IP address and the page asking for the tiles.
DNS for Ospry's own domains only. Traffic goes straight to our server; customer data is not stored there as part of this use. Listed for transparency; not a sub-processor.
If your agency installs Ospry's CRM app: the sub-accounts it is installed on, read and written within the permissions granted (account details, contacts, opportunities, notes, custom fields, and messages such as a callback confirmation text). We also copy the CRM's conversations into Ospry every few minutes (text, email, social and call notes, with the contact's name and message text) so Cue and the inbox can show them. Opening Ospry inside the CRM passes us your name, email, role and account so we can sign you in.
Our affiliate platform provider for the partner programme: partner tracking, commission records and payouts. It may collect payout and tax details from partners directly; Ospry does not store bank or tax numbers. Its tracking script and cookie are only used on our partner pages after the visitor accepts, and only when partner tracking is switched on.
Search Console and Analytics (read only); Business Profile (a read-write permission, used only to read); Google Calendar (reads event times and adds or renames the callback bookings Cue makes, with the visitor's name, phone or email, page and question); YouTube (reads your channel, uploads videos you scheduled). Data received from Google APIs is not sent to Anthropic or any other AI service.
Only if you give us a Bing Webmaster token: reads your own site's Bing performance data.
Only if you turn on alerts on a device: the push service run by your browser's maker (for example Google, Apple, Mozilla or Microsoft) delivers them. Alerts are encrypted to your device, so the service cannot read them, though it can see that one was sent.
Code exists to use OpenAI for Cue replies, but it is switched off. We will update this page and the privacy policy before it is ever switched on.
Facebook, Instagram, TikTok, LinkedIn, X and Pinterest: connecting and posting are not offered at launch.
Connectors for other CRMs and paid SEO data providers exist in the code but are switched off. Any we turn on will be added here first.
Removed straight away when the workspace is deleted; a copy can remain in an encrypted backup until that backup is deleted.
Deleting a site deletes its audits, keyword history, reports and uploaded photos straight away.
The business can set a shorter or longer period within the limits Ospry allows. Deleted straight away when the site or workspace is deleted.
Counted from the last message. The business can set a shorter or longer period within the limits Ospry allows.
The business can set a shorter or longer period within the limits Ospry allows. Also removed when the site or workspace is deleted, or on request.
A visitor not seen for 12 months is removed with everything recorded against them.
A hashed network address and the email used. Removed after a successful sign-in, and in any case within 90 days.
A copy of each email we sent, including chat alerts with visitor details. Copies sent to a workspace's own logins go when the workspace is deleted; others are deleted on request.
Deleted on request.
Kept after a referred workspace is deleted, because they are records of what we owe partners.
Encrypted at rest. Disconnecting, deleting the workspace, or uninstalling the CRM app clears them.
Also removed when the push service reports the device no longer accepts them.
Nightly encrypted database backups, kept so we can recover from a failure. The company also holds copies of those encrypted files. Restoring from a backup has been tested.
Server and application logs, kept for fixing faults, are deleted after 30 days. The osprysuite.com web server's access log, which includes visitors' IP addresses, is kept for a limited period and rotated.
If you are an agency, the data you bring belongs to you and your clients. We process it on your instructions and for no other purpose. You can export or delete a workspace at any time from Settings; what the export and deletion cover today is set out in the privacy policy.
If we add a sub-processor, this page changes first. Anything about data, security or a suspected vulnerability: hello@osprysuite.com.