Skip to content

Privacy Policy

Last updated: 2026-10-29

This policy explains what data Claw Studio collects through the ClawStud iOS app, its backend at api.clawstud.com, the ClawStud visit-tracking pixel, and the clawstud.com website. It describes what is actually stored, not what a generic template would claim.

Who we are

Claw Studio operates the ClawStud app and this website. For anything in this policy, including access, correction or deletion requests, write to [email protected].

For the business data you load into ClawStud (your customers and orders), you are the data controller and Claw Studio acts as your processor. For your own account and for visits to clawstud.com, Claw Studio is the controller.

Your account

When you create a ClawStud account we store:

  • Your name, email address and organization name.
  • Your password, stored only as a bcrypt hash — we cannot read it.
  • Session and refresh tokens, stored hashed, so you stay signed in.
  • A device identifier (Apple’s identifierForVendor) tied to your session.
  • If you sign in with Google: your Google account ID, so we recognise you next time, and the name and email Google shares with us. We never see your Google password.

Push notifications

If you enable notifications, the app registers your device so we can alert you when a new order arrives. We store the Apple push token, the platform and environment, your OS version, app version, device model, locale and time zone. Push is optional; the app works without it, and revoking the permission stops the delivery.

Your business data

ClawStud shows the stores, orders, customers, products and suppliers that you create or that we sync from a store you connect. That includes personal data about your own customers — names, email addresses and shipping addresses. We store it to provide the service, we do not sell it, and we do not use it to train anything or for our own marketing.

Payments

If you connect Stripe, we store your Stripe account identifier and OAuth tokens, encrypted at rest, with read-only scope. We never see or store card numbers: payments are handled by Stripe under its own privacy policy.

Client portal (clawstud.com/portal)

The client portal gives you a unified view of your business metrics. It has a free plan and two paid monthly plans; there is no free trial. Paid plans are charged to a credit or debit card via Stripe; we never see or store card numbers. Subscriptions auto-renew until you cancel.

When you sign up we store your email and a hash of your password, and email you a one-time link to confirm the address; the account works once it is confirmed. When you subscribe, Stripe sends us a webhook with your email and subscription ID and we store the subscription status. Sessions are stored as a random token in an HTTP-only cookie for 30 days. The portal runs on Cloudflare Workers, with its data in Cloudflare D1.

If you connect Google, “Google user data” below explains exactly what we read and how we handle it.

If you connect Stripe, you paste a Restricted Key from your Stripe dashboard into the portal. We encrypt it with AES-256-GCM and store it on your account. We use it to read your MRR, balance, customer count and active subscriptions. The key never leaves the Worker in plaintext. We never write to your Stripe account — permissions are read-only by the choice of Restricted Key you create.

You can cancel at any time from the Billing tab: it opens Stripe's hosted billing portal where you can also update your card and view invoices. After cancellation, your access remains until the end of the current paid period.

You can disconnect any integration at any time from the Integrations tab; its tokens and the reports cached from it are deleted immediately (a few short-lived caches expire within ten minutes), and an entry is added to the audit log.

Google user data (Analytics and Search Console)

If you connect Google in the portal, we ask for read-only access to Google Analytics (https://www.googleapis.com/auth/analytics.readonly) and Google Search Console (https://www.googleapis.com/auth/webmasters.readonly), plus your Google account’s email address and name so the portal can show which account is connected. We never write to your Google account.

How we use it: we list the Analytics properties and Search Console sites you can access so you can choose yours, and we read reports — sessions, users, page views, engagement, channels, devices, countries, top pages, real-time visitors, and search clicks, impressions, click-through rate, position and queries — to show them on your dashboard, in the reports you schedule, on the client-portal links you create and to the AI assistants and tools you connect — with an API token or by authorising them, such as ChatGPT. A weekly summary of your totals (sessions, users and search clicks) is written by an AI model that runs on Cloudflare Workers AI; Cloudflare does not use it to train its models, and we never use Google user data to train AI or machine-learning models.

Who we share it with, and how we protect it, are set out in the next two sections.

ClawStud’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

Sharing, transfer and disclosure of Google user data

We do not sell, rent or trade Google user data. We do not share it with advertisers, ad networks or data brokers, we do not use it for advertising, and we do not combine it with other customers’ data. We share, transfer or disclose it only to the parties below, and only as far as each purpose needs:

  • Service providers that run ClawStud for us and process the data only on our instructions: Cloudflare, Inc., which hosts the portal (Cloudflare Workers), stores the data (Cloudflare D1) and runs the AI model that writes the summaries on paid plans (Cloudflare Workers AI); and Resend, which delivers the emails you set up — scheduled reports and alerts — that contain your Analytics and Search Console figures.
  • The members of your workspace, who see what their role (owner, admin or viewer) allows.
  • Destinations you set up yourself: the read-only client-portal links you create; the scheduled reports and alerts you send to email addresses or to Slack, Microsoft Teams, Telegram or WhatsApp, which are delivered through those services; the API tokens you create; and the AI assistants you authorise over MCP, such as ChatGPT (OpenAI) or Claude (Anthropic). Once the data reaches a destination you chose, that service’s own privacy policy applies. You can remove any of them at any time: links, reports and API tokens in the portal, and assistants from their own settings.
  • When the law, a court order or a competent authority requires it, or when it is necessary to protect the security of ClawStud or its users.
  • In a merger, acquisition or sale of assets, and only after asking for your explicit consent.

How we protect Google user data and other sensitive data

We treat Google user data, OAuth tokens, API keys and passwords as sensitive data, and protect them with these measures:

  • Encryption in transit: the website, the portal and its API are served only over HTTPS (TLS), and every request to Google’s APIs is made over TLS.
  • Encryption at rest: Google OAuth tokens, like every other integration token and key, are encrypted with AES-256-GCM before they are stored, with a key kept as a Cloudflare secret, outside the database and the code. The database itself, Cloudflare D1, is also encrypted at rest by Cloudflare.
  • Least privilege: we request read-only scopes and never write to your Google account. Tokens are decrypted only inside our server at the moment of a request to Google, and are never sent to your browser, to the AI assistants you connect or to anyone else.
  • Access control: each workspace is isolated, and every request is checked against your session and your role in that workspace. Passwords and API keys are stored only as salted PBKDF2-SHA256 hashes, sessions use random tokens in HttpOnly, Secure cookies, two-factor authentication is available, and sign-in and the MCP are rate-limited.
  • Internal access: nobody at Claw Studio reads your Google user data unless you ask us for help and agree to it, it is needed for security purposes such as investigating abuse, or the law requires it. Access to the production database, logs and secrets is limited to Claw Studio’s administrators.
  • Audit log: connecting and disconnecting integrations, creating API tokens, changes to two-factor authentication, data exports and account deletion are recorded in an audit log.
  • Retention and deletion: we keep only the latest copy of each Analytics and Search Console report, overwritten on every refresh. Disconnecting Google in Integrations deletes the tokens, the cached reports, the totals calculated from them and your weekly summaries straight away, and also revokes ClawStud’s access in your Google account when it was the last connection using that Google account. Deleting your portal account deletes all of your integrations and cached reports. You can also remove ClawStud’s access at any time at https://myaccount.google.com/permissions.
  • Incidents: if we become aware of a security incident affecting your data, we will tell you and, where required, the competent data protection authority without undue delay.

Visit analytics (the pixel)

If you install the ClawStud pixel on your own website, each visit records the path, referrer, UTM parameters, approximate country, region and city, device type, browser, operating system, a session identifier and a visitor identifier.

We never store the visitor’s IP address. It is hashed with a salt that rotates every day, which means the same visitor cannot be linked across two different days. There are no advertising cookies and no cross-site tracking. Whether you need a consent banner on your own site depends on your jurisdiction and is your responsibility as the site owner.

Crash reports

If the app crashes, it writes a report locally and uploads it on the next launch so we can fix the fault. Reports contain technical diagnostics — the error, the call stack and app and device version — not the contents of your account.

This website

clawstud.com uses Google Analytics 4 to count visits and to see which pages are read. It also records when someone taps the WhatsApp contact button. Google acts as a processor and may store data outside the EU under its own safeguards.

Where the data lives

The backend runs on Vercel, with the database hosted by Neon in the United States. The pixel runs on Cloudflare Workers, with visit data in Cloudflare D1. Push notifications go through Apple. Emails such as password resets are sent through our email provider. Transfers outside the EU rely on the standard contractual clauses those providers offer.

How long we keep it

Account and business data are kept while your account exists. Deleting your account removes it, as described below. Visit analytics are kept in aggregate; the daily salt rotation means the identifiers behind them stop being linkable after 24 hours. Crash reports are kept while they are useful for fixing the fault.

Deleting your account

You can delete your account from inside the app: Settings, then “Eliminar cuenta”, then confirm. If you are the only member of your organization, the organization and all of its data — stores, orders, customers, devices and tokens — are deleted with it. If other people belong to the organization, your user is deleted and their data continues. The deletion is immediate and cannot be undone.

You can also ask for access, correction, portability, restriction or objection by writing to [email protected]. If you are in the EU you may also complain to your national data protection authority; in Spain that is the AEPD.

Children

ClawStud is a tool for businesses and is not directed at children under 16.

Changes

If this policy changes materially we will update the date at the top and, where the change affects you, tell you in the app.

Contact: [email protected]