Data processing practices

About this page

AutoSugges is operated by an individual. This page describes how data you entrust to the service — including personal data of your own end users, if any list you author contains it — is processed. It is not a countersigned Article 28 data processing agreement, and one is not available today.

Scope of processing

Processing is limited to: storing the rows you author in your isolated tenant schema, compiling them into runtime artifacts, serving those artifacts from the edge in response to a query, and recording aggregate selection signal (which canonical item was shown and picked, tied to a request id rather than an end-user identity) to improve future ranking.

Sub-processors

The following sub-processors are engaged, each for the purpose stated:

• Supabase — System of record (PostgreSQL) for account and tenant data, and authentication (Supabase Auth / GoTrue) for sign-in.
• Cloudflare — Edge runtime (Workers), compiled artifact storage (Workers KV) and bot/abuse challenge (Turnstile) at sign-up and key provisioning.
• Stripe — Payment processing and subscription billing.
• Bird — Delivery of transactional email (e.g. account and billing notifications).

Isolation and access controls

Your rows are isolated by row-level security, enabled and forced on every relevant table. Runtime autocomplete cannot query PostgreSQL at all — it reads only compiled, verified artifacts. Credential material and internal ledgers live in a schema no API role can address.

Retention and deletion

The active published version of a list plus the five most recently superseded versions are retained; a superseded artifact's retention policy targets deletion from the edge store 30 days after it is deactivated. Requesting deletion of a list or an account removes the corresponding control-plane rows.

Requests

For a sub-processor list update or a data-subject request, email support@autosugges.com.