This policy explains what WebOrange Search does with data when you install the plugin on a WooCommerce store and use our hosted search service. It is written to be read, not to be survived.
| Provider | Ioannis Sakkoulas
trading as WebOrange |
|---|---|
| Registered address | Πέτρου Φούμη 23, 71307 Ηράκλειο Κρήτης |
| VAT / Tax ID | EL119679877 |
| Country | Greece |
| Contact | info@weborange.gr |
We are the controller for your account as a merchant: the email address you sign up with, your store domain, your plan and your billing records.
We are a processor for everything the plugin sends us on your store's behalf: your product catalogue and your search statistics. You decide what is sent; we only process it to provide search back to your store.
For each product (and, if variation-level search is on, each variation) we receive:
No order data, no customer data, no personal data of your shoppers is ever sent. The plugin reads your catalogue only. If you add custom fields through our hooks, whatever you put in them is sent too — that choice, and its consequences, are yours.
When a visitor searches on your store, we record:
We do not record IP addresses, user agents, cookies, session identifiers, or any other visitor identifier. There is nothing in our search records that can be traced back to a person by us. We do not set cookies on your storefront and we do not track visitors across sites.
One honest caveat: a visitor can type anything into a search box, including their own name, email or phone number. If they do, that text is stored as a search term. We prune raw search events after 90 days (see below), which limits how long such text can exist, but you should keep this in mind before publishing raw search reports.
The search widget on your storefront sets no cookies. Recent searches, if you enable that feature, are kept in the visitor's own browser storage and never reach us. Our own website uses only a session cookie required for sign-in and form security.
All of it is stored on servers in Germany (EU). Your catalogue lives in a search index dedicated to your store, never shared with another merchant's data. Transactional email is sent from an EU region.
| Sub-processor | What for | Location |
|---|---|---|
| netcup GmbH | Server hosting and the search engine | Germany (EU) |
| Stripe | Payment processing for paid plans | EU / USA (SCCs) |
| Resend | Transactional email (your key, plan changes) | EU (eu-west-1) |
We never see your card details — Stripe collects them directly. We sell nothing to anyone and we run no advertising or analytics trackers on your store.
| Data | Kept |
|---|---|
| Your product index | For as long as your store is registered. Deleted immediately, and in full, when the store is deleted from our system — including the search index itself. |
| Raw search events | 90 days. Enforced by a daily automated job, not by policy alone. |
| Daily search totals | Kept while your store exists. They contain counts only — no individual search is recoverable from them. |
| Account and billing records | While your account is active, then as long as tax law requires us to keep invoices. |
Under the GDPR you may ask us for a copy of your data, to correct it, to delete it, to restrict or object to processing, or to receive it in a portable form. Write to info@weborange.gr and we will answer within one month. You may also complain to your national supervisory authority — in Greece, the Hellenic Data Protection Authority (dpa.gr).
To delete everything yourself: deactivate and uninstall the plugin, then email us to have the store and its index removed. We do not require a reason.
All traffic is encrypted with TLS. Licence keys are stored hashed, never in readable form — which is why we cannot resend an existing key and must issue a new one instead. The master key to the search engine never leaves our server; your storefront receives only a short-lived token that is restricted to your own index and expires within 24 hours.
If we change this policy in a way that matters, we will email the address on your account before it takes effect. The date at the top always reflects the current version.