Terms, privacy and how we handle your data

01What we collect

We collect only what we need to run the service:

• —Account data: name, email address, company, team role.
• —Search Console data: queries, pages, clicks, impressions, CTR, position, country and device for the properties you connect.
• —Billing data: billing address, tax ID and the last four digits of your card. Full card details stay with our payment processor.
• —Usage data: sign-in times, feature usage and error logs, kept without advertising identifiers.

02Google API data

Serplyze asks for one Google permission: the read-only Search Console scope (webmasters.readonly). We use it only to read performance data for the properties you choose and show it back to you. We cannot change settings, submit sitemaps or manage users in your Search Console.

We do not sell Google user data, use it for advertising, or allow people to read it, except with your consent, for security investigations, or where the law requires. Serplyze’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke access at any time in your Google account settings.

03How we use it

To provide and secure the service, send alerts and invoices you asked for, answer support requests, and understand in aggregate which features are used. We never build advertising profiles.

04Retention

We keep data only as long as it is useful to you or required by law:

05Sharing

We share data only with the subprocessors listed in the DPA, each bound by contract to process it on our instructions, and with authorities where the law compels us. We do not sell personal data.

06Your rights

You can access, correct, export or delete your personal data, and object to or restrict its processing. Most of this is self-service in Settings; for anything else, write to privacy@serplyze.com. You may also complain to your local data protection authority.

07International transfers

Our primary hosting is in the EU. Where a subprocessor handles data outside the EU, we rely on an adequacy decision or the European Commission’s standard contractual clauses.