Who runs this, and how to reach us
Prongo is a personal platform operated by TM Dev, an individual developer based in Belgium. It is the data controller for the information described here. You can see more about the person behind it at tm-dev.be.
For anything about your data, such as access, deletion, corrections, or questions, email . This is a small project, so requests are handled personally, normally within 30 days.
What we collect, and why
We keep the data needed to run your account and your deployments. We collect nothing for advertising, and we never sell it. Here is the full list.
| Data | What it is and how we use it | Why we’re allowed to |
|---|---|---|
| Account details | Your email (required), an optional display name, and your password stored only as a salted hash, never in plain text. We use these to create and run your account. | Contract. We need it to give you an account. |
| Sign-in session | A session token tied to your account, so you stay logged in between visits. Held in an essential cookie (see Cookies below). | Contract. You cannot use a logged-in dashboard without it. |
| GitHub connection | If you connect GitHub, we store your GitHub identity and an access token (encrypted at rest) so Prongo can read the repositories you choose to deploy. Nothing else in your GitHub account is touched. | Your consent. You choose to connect, and you can disconnect any time. |
| Your projects and deploy logs | The project and service configuration you create, and the build/deploy logs the platform produces while running them. | Contract. This is the service doing its job. |
| Your secrets and environment values | Secrets you add are encrypted at rest and only injected into the services you explicitly choose. They never appear in logs or the API in plain text. | Contract. We need it to run your apps the way you configured them. |
| Visual API projects | If you use a Visual API (mocked-API) project, the canvas and mock definitions you build are stored as your project content, under the same encryption and retention as any other project. | Contract. This is the service doing its job. |
| Activity log | A record of key actions (who did what, and when) tied to your email, kept as a security and audit trail for your own projects. | Legitimate interest. It keeps the platform safe and accountable. |
| Feedback you send | Anything you submit through the feedback form, so we can improve the platform. | Legitimate interest. We act on what you tell us. |
| Your IP address (briefly) | When you sign in or register, your IP is used in memory to rate-limit repeated attempts against abuse. It is not written to a database and not kept afterwards. | Legitimate interest. It prevents brute-force attempts and abuse. |
No billing data yet. Prongo takes no payments during the beta, so it holds no card numbers or billing details. When paid plans launch, the billing information kept and the payment processor used will be listed here first, and our refund policy explains how cancellations and returns work.
Cookies
Essential cookies
These are needed for the site to work and are always on:
| Cookie | Lifetime | What it’s for |
|---|---|---|
| Session cookie | ~30 days | Keeps you signed in. HttpOnly, SameSite=Lax, and Secure over HTTPS. |
| GitHub-connect cookie | ~10 minutes | Secures the GitHub linking step against tampering, then expires on its own. |
Optional analytics cookies
On the marketing site, we ask first. Nothing below loads unless you click Accept in the cookie banner.
| Service | Lifetime | What it’s for |
|---|---|---|
| Microsoft Clarity (_clck, _clsk, MUID) | 1 day to 1 year | Anonymous usage analytics on this marketing site: clicks, scrolling and session recordings, so we can improve the UX. Provided by Microsoft. |
| Google Tag Manager | n/a | Loads the measurement tags we configure. GTM itself sets no cookies, but the tags it loads may. |
Your choice, any time. Your answer is stored in your browser. Use “Cookie settings” in the footer to change it; declining stops the analytics scripts. We use no advertising cookies.
Who we share data with
Running a hosting platform means a few trusted services handle parts of the job. Each one only gets what it needs for its task. We never sell your data.
| Service | What it does | When it applies |
|---|---|---|
| GitHub | Sign-in and reading the repositories you choose to deploy. | When you sign in with GitHub or connect a repo. |
| Google (Gemini AI) | Generates plain-language explanations of failed deploys. We send the recent deploy logs, your repo’s root file names, and optionally selected files. | Only if you turn on AI explanations. Off by default; you can also use your own API key. Off means nothing is sent. |
| Microsoft (Clarity) | Anonymous usage analytics and session recordings on the marketing site. | Only if you accept analytics cookies in the banner. |
| Google (Tag Manager) | Loads our measurement tags on the marketing site. | Only if you accept analytics cookies in the banner. |
| Let's Encrypt | Issues the TLS certificates for your URLs and custom domains. | Your domain names appear in public certificate-transparency logs, which is standard for any HTTPS site. |
| Cloudflare | DNS resolution only (DNS-only mode). It does not proxy or inspect your traffic. | For resolving platform and custom domains. |
| EU hosting provider | Runs the servers the whole platform lives on, inside the EU. | Always. This is where your data is processed and stored. |
Transactional email (things like account notices) is minimal during the beta. If a dedicated email provider is added later, it will be listed here first.
AI and error data
We do not train AI models on your source code. Your code is never used to train, fine-tune or improve any model, ours or anyone else’s, and we never use it in marketing or videos.
When a project fails to build, start or run, we do keep a small, anonymised error signal: the failure category (for example build failed, out of memory, wrong port, health check timeout), the framework and runtime, the step where it failed, and one normalised error line with file paths, values, domains and secrets stripped out. It is not linked to your account or project, and it contains no source code.
We use these error signals to:
- recognise common failures faster and suggest a fix in the dashboard;
- improve the platform and its documentation;
- publish anonymous, aggregate statistics in marketing material and videos, such as “the five most common deploy errors”. Never anything that identifies you or your project.
We keep error signals for 12 months, then delete them. Aggregate statistics that no longer contain individual records may be kept. The optional AI explanations (Gemini, see above) are separate: they are off by default and only send data when you turn them on.
Where it lives, and how long we keep it
Where it lives, and how it’s protected
Everything runs on servers in the EU. Secrets and access tokens are encrypted at rest, traffic is encrypted with TLS, and every project is isolated from every other. The security page covers the how in more detail. Platform admins can see project metadata and resource usage across the platform to manage capacity and provide support, but secret values stay masked to anyone who isn’t the project owner. See our permissions page for details.
How long we keep it
Account data is kept while your account exists. Deleting a project tears down its running services; deleting your account removes your profile, sessions, settings, secrets and projects. A minimal record (an internal id and a reason) is retained after deletion to prevent abuse and keep the audit trail honest. Logs are kept only for a limited time. Anonymised error signals are kept for 12 months (see AI and error data).
Your rights under the GDPR
- Access: get a copy of the personal data we hold about you.
- Rectification: have inaccurate details corrected.
- Erasure: have your data deleted (the “right to be forgotten”).
- Portability: receive your data in a portable form.
- Restriction and objection: limit or object to certain processing.
- Withdraw consent: for anything based on consent, such as the GitHub connection or AI explanations.
To use any of these, email . If you believe we’ve mishandled your data, you also have the right to complain to your data protection authority. In Belgium, that is the Gegevensbeschermingsautoriteit (APD/GBA).
Children, and changes to this policy
Not for children
Prongo is a tool for developers and is not intended for anyone under 16. We don’t knowingly collect data from children.
Changes to this policy
As the platform grows, this page will be updated. The date at the top always reflects the latest version. Significant changes will be called out clearly.