---
title: "Privacy policy | Siper"
description: "Privacy policy for siper.io: what the contact form, counters, Cloudflare scripts and the playground do with data, and how Siper processes personal data."
url: https://siper.io/privacy
---

Legal

# Privacy policy

Last updated 10 November 2026.

Summary

## What this site does with your data

This site collects data in the five places below. The rest of this policy covers the Siper service.

| Feature | Data | Where it goes |
| --- | --- | --- |
| Contact form on [/contact](https://siper.io/contact) | Full name, work email, company size and your message. | Your browser sends the fields to the Gurubase contact service, which stores the request and emails it to the Siper team. |
| Counters | Cookieless, first-party counts, such as a QR scan, a sample run or a click on the demo button. | The counter stores the event name, the option chosen and the page path. It sets no cookie and reads no IP address, user agent or referrer. |
| Cloudflare Web Analytics | Cookieless page analytics. It loads a script from a Cloudflare host. | Cloudflare. |
| Cloudflare Turnstile | A check that protects the playground and the contact form from abuse. It loads a script from a Cloudflare host, and only on those two pages. | Cloudflare. |
| Playground | The text you enter, and the result. | An edge proxy on the site sends your text to the Siper service. Sections 3, 4 and 8 say what may be kept and how it may be used. |

This site allows exactly two third-party scripts: Cloudflare Web Analytics and Turnstile. The analytics and the counters set no cookies, so the site shows no cookie banner.

We also use Bing Webmaster Tools and Google Search Console to see how search engines index this site.

Clause 1

## Scope

This policy applies to the siper.io website, the Siper playground, the Masking API, the AI Gateway, sales conversations and support. If an enterprise customer has signed a separate contract or data processing annex, that document takes priority for that customer's environment.

Clause 2

## Who we are and how to reach us

Siper is a product of Gurubase. For privacy, support and sales questions, write to [contact@siper.io](mailto:contact@siper.io).

Clause 3

## Categories of data we collect

- **Website and contact data:** first and last name, work email, company information, message content, request date and technical records.
- **Playground data:** the text you enter, the masked output, the detected categories and counts, the IP address of the request, and browser or client information. This also includes the entry point of the request (website or MCP). Use made-up data, not real personal data.
- **Production usage data:** API key, request time, error code, usage volume, category counts and security records. The default aim is not to log raw personal data.
- **Payment and billing data:** plan, amount of usage, billing details, and payment data that the payment provider processes.
- **Support data:** support requests, screenshots, technical output, contact history and samples that the customer shares.

Clause 4

## How Siper processes data

- In the managed Siper service, masking runs on servers in Istanbul, in Türkiye.
- In mask-only use, your application sends text to the Siper /mask endpoint. Siper returns the masked text and detection metadata.
- In gateway use, your existing SDK request passes through Siper first. After masking, Siper sends the masked content to the model provider you selected.
- On-prem, VPC or air-gapped installs can be configured so that production data stays in the customer's environment.
- The demo environment is separate from production customer data. Demo inputs may be used to improve the service and its detection quality. Production customer data is not used for model development.
- Reverse mapping, audit trail and retention policies are configured by customer contract and install choice.

Clause 5

## Purposes of processing

- To provide the Siper service, and to run masking and gateway requests.
- For security, abuse prevention, debugging and capacity planning.
- To run sales, demo, proof of concept, customer support and contract processes.
- For usage-based pricing, billing and accounting duties.
- To answer legal requests and protect our rights.

Clause 6

## Legal grounds

- Forming and performing a contract.
- Meeting legal obligations.
- Legitimate interest: security, product reliability, debugging and fraud prevention.
- Explicit consent: where required, for marketing messages or optional cookies.

Clause 7

## Transfers and sub-processors

Siper may use services for hosting, security, email, payment, error tracking, support and optional model providers. In the gateway flow, customer configuration decides which model provider receives a request. For on-prem or air-gapped installs, the contract sets the scope of sub-processors separately.

For this site, those services include Cloudflare and the Gurubase contact service that receives contact requests.

Clause 8

## Retention

- Playground data may be kept for as long as needed to improve the service and for security. It is then deleted or made inaccessible.
- Contact and support records are kept for as long as needed to manage the request, for security and for legal obligations.
- Billing records are kept for the period of the relevant accounting and tax obligations.
- Customer contract and install model set the retention of production logs and audit trails.

Clause 9

## Your rights

You can exercise your rights under applicable law, including those in KVKK Article 11, by writing to [contact@siper.io](mailto:contact@siper.io). These include the rights to request information, correction and deletion, to object to processing, and to learn which parties received your data. A request may need identity verification.

Clause 10

## Security

Siper supports data minimisation with encryption in transit, access control, API key management, audit trail and install options in the customer's environment. No technical or administrative measure removes all risk. Access permissions, data classification and usage policies on the customer's side also matter. The [security page](https://siper.io/security) has more detail.

Clause 11

## Changes

We may update this policy when the product, the infrastructure or legal requirements change. For important changes, we change the date on this page and, where required, notify customers separately.
