Privacy Policy

Last updated: November 1, 2026

This policy explains what personal data Ploa collects, why, who it shares it with, how long it keeps it, and what you can ask of us. It covers ploa.dev, the dashboard at ploa.dev/app, the ploa CLI and its MCP server, and the emails Ploa sends. It doesn't cover the App Store, Google Play, GitHub or any other service you connect to Ploa: their own policies apply there.

1. Who we are

Ploa is operated by Yehonatan Krispil, an Israeli sole trader trading as Jstudio, of 25 Rova Yizre'el, Apt. 7, Afula 1804340, Israel ("Ploa", "we", "us"). For the personal data in this policy we are the controller, the database owner under Israel's Privacy Protection Law, 5741-1981.

When Ploa handles data about the people who use your apps, such as the names and text in store reviews, we do it for you and on your instructions, as your processor (see section 8).

Questions about privacy: privacy@ploa.dev.

2. What we collect

Your account. Your email address, your name if you give one, your role, your workspace's name and your language. For each passkey, its public key and a label; your fingerprint or face never leave your device. If you turn on an authenticator app, its secret, encrypted. Recovery codes, stored only as hashes.
Signing in and security. Each session's start, last use, IP address and browser (user agent). One-time email codes, stored as hashes, for 10 minutes. Security events, such as a failed sign-in: when, the IP address and what happened.
Your store connections. App Store Connect API keys, Google Play service accounts, Android upload keys and iOS distribution certificates, encrypted in Ploa's vault, and their public details (such as a key's ID or a certificate's expiry). An App Store vendor number or a Play reports bucket, if you add them.
Your apps and what the stores say about them. Identifiers, names and icons; builds' versions and states; releases and their steps; the store page's text, screenshots and videos; your privacy answers; in-app products and offers; ratings, reviews and your replies; rejections and the notes you add; and the downloads, sales and store page numbers the stores report.
What you and your agents do. An audit log of every action: who (you, a member, or a token and the name its agent gives), what, when, and the IP address it came from. API tokens, stored only as hashes.
GitHub, if you connect it. The installation and repositories you link (their IDs, folders and branches) and the GitHub account that linked them.
Push notifications, if you turn them on. Your browser's push address and keys, and the device's name.
Messages. What you write to support, from the site, the dashboard or by email, with the address you write from, and our replies.
Payments, once paid plans open. Paddle takes payments as the merchant of record (see section 4). We receive your plan, its status, and each payment's amount, currency and country; never your card details.

What we don't collect. The site and the dashboard have no analytics, no advertising and no trackers. We don't keep your source code: the CLI reads your project on your machine and sends Ploa what a step needs, such as the version, the app's icon and preflight's findings. Builds you send through Ploa (Android bundles, for signing, and iOS builds if you choose to upload through Ploa) are deleted as soon as the store has them.

We don't sell personal data, and we don't use your data or your apps to train AI models. Ploa has no AI of its own: the agent you use is yours, under its own provider's terms.

3. Why we use it

To provide Ploa, which you asked for (performance of our contract with you): your account, calling the stores with your keys, builds, releases, the store page and the rest.
To keep it secure (our legitimate interest, and Israel's Privacy Protection (Data Security) Regulations, 5777-2017): sign-in limits, security events and alerts, the audit log, backups.
To tell you what you need to know (our contract): sign-in codes, approval requests, a release that reached testers or failed, security notices, and changes to our terms. We send no marketing email unless you agree to it.
To meet the law (legal obligations): tax and accounting records, and answering lawful requests.

Providers who process data for us, under contracts that limit them to doing so:

Google Cloud: Ploa's server and its data, in Israel (the me-west1 region), and a copy of the encrypted backups in the United States (us-central1).
Resend: sending Ploa's emails, and receiving mail sent to @ploa.dev addresses.
Paddle, once paid plans open: payments, invoices, taxes and refunds, as the merchant of record. Paddle collects your payment details itself, under its own privacy notice.
Google Fonts: Ploa's pages load their typeface from Google, which receives your IP address and browser details when it serves it.
Push services run by your browser's maker (such as Apple, Google or Mozilla), for the devices where you turn on notifications. They get only encrypted messages.

Services you connect, on your instructions: Apple (App Store Connect), Google (Google Play), GitHub and RevenueCat. Ploa sends each one what the step you or your agent asked for needs, with the keys you gave.

Otherwise only when the law requires it, to protect people's safety or our rights, or to a buyer of Ploa that takes on this policy, with notice to you.

Outside Israel. Some of these providers process data in other countries, such as the United States and the European Union. We transfer data only as Israel's Privacy Protection (Transfer of Data to Databases Abroad) Regulations allow, and for data from the European Economic Area or the United Kingdom, with the safeguards the law requires, such as the European Commission's standard contractual clauses.

5. How long we keep it

Your account and workspace: for as long as they exist. When a workspace is deleted it waits 30 days, in case it was a mistake, and is then purged: its people, apps, store keys, drafts and builds.
The audit log stays after that. Each row's hash covers the one before, so removing rows would break the record for every other workspace. Its rows hold what was done, by whom, when and from where, never a key or a password.
Sessions: until you sign out, or 30 days after their last use. Email codes: 10 minutes. Security events: 30 days.
Builds: deleted as soon as the store has them.
Support requests: with your workspace, or, if you wrote without an account, until you ask us to delete them.
Encrypted backups: 14 nights on the server, and 180 days in the backup copy in Google Cloud Storage (then up to 7 more days until Google erases it). Something deleted leaves the backups when they roll off.
Payment and invoice records: as long as tax law requires, which in Israel is generally 7 years.

6. How we protect it

Store keys and certificates are encrypted with AES-256-GCM, each with a key of its own, and calls to the stores leave from our server, so your keys never reach your machine or your agent. You sign in with passkeys, without passwords. Tokens and codes are stored as hashes. Every workspace is sealed off from the others. The audit log can't be rewritten without it showing. Backups are encrypted to a key that isn't on the server. Every connection uses TLS.

No system is perfectly secure. If a breach affects your personal data, we'll tell you and the authorities as the law requires.

7. Your rights

You may ask to see the personal data we hold about you, to correct it, to delete it, to receive a copy of it in a common format, or to object to how we use it, and you may withdraw a consent you gave. Israel's Privacy Protection Law gives you the right to review your data (section 13) and to ask for it to be corrected or deleted (section 14). If you're in the European Economic Area or the United Kingdom, the GDPR gives you these rights too.

Write to privacy@ploa.dev from your account's email address. We answer within 30 days. A workspace's owner can ask for an export of the whole workspace or for its deletion the same way. You may also complain to Israel's Privacy Protection Authority, or to the data protection authority where you live.

8. Your apps' users

Some data Ploa handles is about the people who use your apps: reviews and the names on them, ratings, and testers you add. Ploa processes it only to provide the service to you and as you instruct, and it's yours to answer for to those people, including in your app's own privacy policy. A data processing agreement is available at privacy@ploa.dev.

9. Children

Ploa is a tool for developers and businesses, and isn't meant for anyone under 18. We don't knowingly collect data from children.

10. Cookies and browser storage

Ploa sets one cookie: your session, which keeps you signed in (HttpOnly, Secure, for 30 days from your last visit). Your browser's local storage keeps your language and a few display choices. There are no third-party, advertising or analytics cookies, so there's nothing to consent to.

11. Changes

We'll post any change here with a new date. If a change matters to how we use your data, we'll email account owners before it takes effect.

12. Contact

privacy@ploa.dev · Yehonatan Krispil, trading as Jstudio, 25 Rova Yizre'el, Apt. 7, Afula 1804340, Israel.