Privacy policy

What we collect, why we collect it, and what we do not do with it. Short, because there is not much.

In effect from 23 October 2026.

Who is responsible

The controller of the personal data described here is:

Nimions
a sole trader, trading as Penstoke
Wellington

Shropshire

United Kingdom

support@penstoke.com
+44 7947 837070
+880 1344 913431

What we collect

Your account. Your name and email address, the organization name, the members you invite and their roles, and a hash of your password. We never store the password itself.

What you configure. The providers, endpoints, buckets, apps, campaigns and schedules you set up, and the credentials for the provider accounts you connect. Credentials are encrypted at rest.

What the gateway does. A record of each request routed: when, which endpoint or alias, which provider answered, the response status, how long it took, how many tokens or bytes it involved, and which API key made it. This is what the usage charts and the audit trail are built from.

Payment. Handled by Paddle. We receive the subscription state, the plan and the country Paddle determined for tax. We never see or store your card details.

The newsletter, if you ask for it. Your email address and the date you confirmed it, and nothing else — no name, and no record of what you open or click. An address typed into the signup box is not stored at all: we mail it a confirmation link, and the address is written down only when somebody reading that mailbox opens the link. Unsubscribing deletes it.

Devices you have signed in from. For each account, a one-way digest of the browser and address of each sign-in, with the browser and address themselves kept beside it so a message can name them. It exists for one purpose: to tell you when your account is used from somewhere it has not been used before. There is nothing in it to read back as a history of where you have been, and we do not look up where in the world an address is.

Technical. IP address, user agent and timestamps in server logs, kept for security and debugging.

What the AI gateway records about a call

Every call through the AI gateway is logged: when, which endpoint or alias, which provider answered, the status, the latency, the tokens and the cost. That record has no content in it and cannot be switched off — it is what the usage figures, the budgets and the audit trail are built from.

Two settings do involve content, both on by default, both yours to turn off under Settings → AI in your dashboard:

  • Log previews. The first 500 characters of the prompt and of the answer are stored on the log row, so a developer can see what a call actually sent when debugging one. Only people with a seat in your organization can read them.
  • Response caching. An identical request can be answered from a stored copy instead of calling the provider again, which means the complete answer is held for the cache lifetime — one hour by default. It saves the call and the money it would have cost.

Turn both off and nothing of what you route is stored at all: the log keeps the shape of the call and none of its content. Neither setting ever applies to the storage gateway, which never sees your files, and there is nothing of this kind in the push gateway.

What we do not collect

  • Card numbers. Those go to Paddle and never reach us.
  • The bytes of the files you route. Storage is presigned: an upload goes straight from your user to your bucket and its contents never pass through us.
  • Anything from third-party advertising or analytics trackers. The public site carries none.
  • Email addresses or phone numbers belonging to the people who use your apps. Push targeting works on a topic every install subscribes to, or on an anonymous device token the app registered for itself, so no contact detail of an end user ever reaches us.

What we never do with any of it

  • We do not sell, rent or broker personal data, and we never have.
  • We do not use it for advertising, do not serve advertisements, and do not build profiles for anyone else to advertise against. Reading a customer's own AdMob earnings is read-only reporting of money they have already been paid.
  • We do not send marketing email or SMS on a customer's behalf, to anyone. Penstoke has no such feature.
  • We do not accept, import or hold lists of contacts, and nothing in the product can message a person who has not installed the customer's own app.

What Penstoke is for, and the product categories it is not, are set out in full on our acceptable use page.

Why we are allowed to hold it

  • To perform the contract — your account, your configuration and the routing you asked for.
  • Legitimate interests — keeping the service secure, debugging it, preventing abuse, and the usage records that show you what you are using.
  • Consent — the newsletter, and only the newsletter. You give it by opening the link we mail to your address, and you withdraw it with one click from any message we send. Nothing else here asks for consent, and nothing else is affected by withdrawing it.
  • Legal obligation — tax and accounting records, principally held by Paddle as merchant of record.

Who it is shared with

We do not sell personal data and we do not share it for advertising. It reaches other parties only where the service cannot work otherwise:

  • Paddle — payment, invoicing, tax and refunds, as merchant of record.
  • The providers you configure — requests you ask us to route are sent to them, under their own privacy terms and on your account with them.
  • Our hosting and database providers, who store the data on our behalf under contract.
  • Anyone we are legally required to disclose to, where we are satisfied the request is valid.

Data you connect from Google

Linking a Google Play, AdMob, Firebase or Google Analytics account grants Penstoke read access to that account on your behalf. We ask for the narrowest scopes each feature needs, and never for permission to change anything in your Google account. Exactly what each connection reads:

  • Google Play — installs, uninstalls, store revenue, ratings, crashes and store listing figures for your own apps, read from the report files Play delivers to your Cloud Storage bucket.
  • AdMob — estimated earnings, impressions, clicks, match rate and eCPM for your own ad accounts.
  • Google Analytics — active users, new users, sessions, screen views and engagement for the properties you pick.
  • Firebase — the names of your Firebase projects and their apps, so a connection can say which project it belongs to, and sending the push messages you ask us to send through it.
  • Signing in with Google — your email address, your name and your Google account identifier, used to create or open your Penstoke account and nothing else. These are non-sensitive scopes and read no Google product.

None of it is personal data about the people who use your apps. Play, AdMob and Analytics report counts and totals, not individuals, and Penstoke asks for no scope that would return a name, an address or a device identifier belonging to one of your users.

Penstoke's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. In plain terms, that means:

  • We use the data only to show you the figures and send the messages the product exists to provide.
  • We do not transfer it to anyone else, except as needed to provide those features, for security, or where the law requires it.
  • We never use it for advertising, and we never sell it.
  • No human at Penstoke reads it, except with your explicit permission, for security, or where the law requires it.

How it is protected. The access token we hold is encrypted at rest with AES-256-GCM, under a key derived from an environment variable of the deployment rather than anything stored in the database — a copy of the database on its own decrypts nothing. It is never returned to a browser after you grant it, and it is never written to a log. The figures read with it are held in the same database, scoped to your organization in the data layer so that no request made by another customer can reach them, and every connection to Google and to the dashboard runs over TLS. What protects it is written out in full, including what is absent, on our security page. Penstoke holds no SOC 2 report and no ISO 27001 certificate, and says so there rather than implying otherwise here.

How long it is kept, and how to remove it. You can revoke access at any time, either by removing the connection in Penstoke or from your Google account's third-party access settings. Revoking stops anything further being read. Removing the connection in Penstoke deletes the stored token immediately and deletes the figures that were read through it. Otherwise the figures are kept while your account exists, as the history the dashboard charts, and for thirty days after the account is closed so you can export them — after which they are deleted with the rest of the account.

Where it is held

The service runs on infrastructure outside the United Kingdom, so your data is transferred and stored internationally. Where personal data of people in the UK or the EEA is transferred, we rely on the standard contractual clauses our hosting providers offer.

How long it is kept

  • Account and configuration data: while your account exists, then 30 days after it is closed so you can export it.
  • Provider credentials: deleted immediately when you delete the provider or the account.
  • Request records and audit trail: retained while the account exists, as the usage history the dashboard shows.
  • Newsletter address: until you unsubscribe, which deletes it outright. We keep no list of people who have left.
  • Server logs: a short rolling window, kept for security and debugging.
  • Invoices and tax records: as long as the law requires, held by Paddle.

What we send you

Most of our email is a reply to something you just did: a verification code, a password reset, an invitation, a receipt. Those arrive because you asked for them seconds earlier, and there is no way to switch them off — asking for one would be impossible if there were.

Two other kinds exist and both can be stopped with one click, from any message, with no account needed. The first is about your own account: a note when it is signed in to from a device it has not been used from before, a welcome when you confirm your address, and the occasional getting-started message in your first week. The second is the weekly app analytics digest, which is switched on per seat and off from the link at the bottom of it. Stopping either changes nothing else, and we keep no record of what you open or click in any of them.

Your rights

You can ask for a copy of your personal data, ask us to correct it, ask us to delete it, object to processing based on legitimate interests, or ask for it in a portable form. Much of this you can do yourself from the dashboard; for the rest, write to us.

If you think we have handled your data badly, tell us first — we would rather fix it. You also have the right to complain to the data protection authority where you live.

Cookies

The dashboard sets one cookie, gw_session, which keeps you signed in. It is strictly necessary, httpOnly, and there is no way to use an account without it. Your theme choice is kept in your browser’s local storage, which never reaches us. There are no advertising or analytics cookies.

Changes and contact

If this policy changes materially we will give notice to the address on your account and change the date at the top of this page.

Questions, or any request about your data, go to support@penstoke.com.