This policy explains what personal data Puaro collects, why, who we share it with, how long we keep it, and the choices you have. It covers our website at puaro.io, the Puaro application at app.puaro.io, and the integrations you connect to it.
Who we are
Puaro is operated by Puaro Security Inc., Tel Aviv, Israel ("Puaro", "we", "us"). You can reach us about anything in this policy, including a request about your own data, at info@puaro.io.
For account, website, and marketing data, Puaro is the data controller (in Israeli law, the database controller). That means we decide why and how the data is used.
For the repository content your organization asks us to scan, your organization is the controller and Puaro is its processor. We handle that content on your organization's behalf, under the data processing terms in our terms of service.
Your choice to give us data
No law requires you to give Puaro personal data. Giving it is your choice. If you choose not to give it, some things cannot work:
- without sign in details, we cannot create your account;
- without access to a repository, we cannot scan it;
- without your email address, we cannot answer a contact request or send you the newsletter.
What we collect
Account and organization data
- Sign in details: name, email address, username, and profile image. We receive them from our authentication provider (Clerk) when you sign up, sign in, or accept an invitation, including when you sign in with your GitHub or GitLab account.
- Organization details: organization name, members, roles (admin or member), and invitations, including the email address of anyone an admin invites.
- Plan details: your plan and limits and, if you install through GitHub Marketplace, the GitHub account name, plan, and trial status GitHub sends us. We do not receive or store card or bank details.
Repository and scan data
When you connect GitHub or GitLab, we scan the repositories you choose. To do that we:
- Fetch code temporarily. We download or clone the repository into temporary storage in Google Cloud, scan it, and delete the copy when the scan ends. We do not keep a copy of your repository.
- Store findings. For each possible secret we keep the repository name, branch, file path, line number, the matched line of code as it appears in the file (which can contain the secret itself), a masked copy of that line, short lines of related code (for example, lines in other files that use the same value), severity, the AI verdict and reasoning, the result of validity checks, and its status (open, resolved, rotated, or false positive).
- Store commit and pull request details. For pull request, merge request, push, and history scans we keep commit identifiers and messages, the pull request or merge request author, the person who pushed, and the commit author's name, email address, and profile image link. A finding needs to show who introduced it and when. Some of these people are not Puaro users. We get their details from the repositories you connect and from GitHub and GitLab.
- Store integration credentials. OAuth tokens, personal access tokens, and installation identifiers that let Puaro read your repositories and post results back.
- Run trial checks. If you install Puaro from GitHub Marketplace before you sign up, we run a limited pattern check on new pull requests and post the result as a GitHub check. We do not store findings from these trial checks.
Integrations you connect
- Slack: workspace and channel identifiers and the token Slack issues, so we can post alerts. An alert names the repository, branch, pull request, author, severity, and file and line. It never contains the secret.
- Jira (if you connect Jira): your Atlassian account identifier, email address, and OAuth tokens, so we can create and update Jira issues for findings. The issues never contain the secret.
What you do in the application
- Assignments: when you assign a finding to someone, we keep that person's email address and your note, and we email them.
- Support requests: your name, email address, subject, and message.
- Interface choices: filters, table settings, and open tabs are saved in your own browser (see Cookies).
Emails
- Product emails: we record when the emails we send you are delivered, opened, clicked, bounced, or marked as spam, and when you unsubscribe.
Website forms
- Contact form: your name, company, email address, subject, message, and your consent choices, including whether you asked for product updates. We also keep technical details that help us stop spam: IP address, browser user agent, referring page, how long the form took to fill, the result of the Cloudflare Turnstile bot check, and an automated spam score.
- Newsletter: your email address, the time you subscribed and confirmed, and a hashed (one way scrambled) version of your IP address. Signing up is double opt in: you are subscribed only after you click the confirmation link we email you.
- Limits on repeated submissions: for both forms we keep salted hashes of the IP address and the email address, so one network or address cannot flood the form.
Usage and technical data
- Logs: our servers log requests and errors. A log line can include an IP address, an email address, and account identifiers. Logs pass through a redaction step that removes tokens and secrets before they are written.
- Website analytics: with your consent, Google Analytics on puaro.io.
- Where your sign up came from: a sign up link on puaro.io can carry campaign tags from the address you arrived on (such as
utm_source). If you accepted analytics, it can also carry the site that referred you and the first page you visited. We store these with your account to learn which channels bring sign ups. - First steps in a workspace: we record once per workspace when someone first opens a finding and when someone first opens a fix pull request or merge request, with the time and the user, to see where new teams get stuck.
- Advertising measurement in the application: app.puaro.io loads a Google Ads tag. It sets Google cookies and sends Google the address of the page, your IP address, and browser details, and it tells Google when a new user connects GitHub. We use it to see whether our advertising leads to sign ups. It does not send your code or your findings.
How we use your data
- To run the service: scan repositories, show findings, post checks and comments to GitHub and GitLab, open fix pull requests and merge requests you ask for, and send alerts to Slack, Jira, or email.
- To check whether a leaked credential still works (see Validity checks).
- To manage your account, organization, plan, and invitations.
- To send service emails, such as scan results, scan failures, assignments, and support replies.
- To send a welcome email and onboarding tips after you sign up. You can unsubscribe from these with one click.
- To answer contact requests, to send the newsletter you confirmed, and to send product updates if you ticked that box on the contact form.
- To keep the service secure, prevent abuse and spam, and fix problems.
- To understand how visitors use our website, only if you accept analytics cookies.
- To measure whether our advertising leads to sign ups.
- To meet legal obligations.
We do not sell your personal data, and we never use your code or findings for advertising. We do not make decisions about you by automated means alone that have a legal or similarly significant effect on you. The AI in Puaro judges lines of code, not people.
AI processing
Puaro uses Google Vertex AI (Gemini models) to decide whether a possible secret is real, explain why, and suggest a fix.
- What we send: the matched line, up to three lines before and after it, the name of the key or variable, the file path, the repository address and description, and short lines from elsewhere in the repository that use the same value. We do not send whole repositories.
- The line is sent as is. The model sees the matched line, including the secret value, because it needs the real value to judge it. AI reasoning and fix advice that we store or publish replace the secret with
[secret redacted]. - Where it runs. We call Vertex AI through Google's global endpoint, so Google may process a request in any region where it runs the model.
- No training. Puaro does not train AI models on your code. Under Google Cloud's terms for Vertex AI, Google does not use this data to train its models.
Validity checks
For some providers (GitHub, GitLab, OpenAI, Slack, SendGrid, Stripe, and AWS), Puaro checks automatically whether a leaked credential is still active. To do that, we send the credential to the provider that issued it, using a read only request that changes nothing in the account. We repeat the check from time to time, about daily for a credential that was active and about weekly otherwise. This tells you which leaks need urgent rotation. We do not use the credential for anything else.
Legal bases (EEA, UK, and Israel)
In Israel, we rely on your consent, given when you sign up, connect an integration, or send a form, and on the law where it permits or requires the use. In the EEA and the UK, we rely on these bases:
- Contract: to create your account and provide the service you or your organization signed up for, including scans, findings, alerts, service emails, and support.
- Legitimate interests: to keep the service secure, prevent spam and abuse, run validity checks so leaks get fixed, keep logs, improve the product, send onboarding emails to people who signed up, and answer contact requests. We balance these interests against your rights, and you can object at any time.
- Consent: for analytics cookies on the website, the newsletter, and product updates you asked for. You can withdraw consent at any time, and that does not affect what we did before.
- Legal obligation: where a law requires us to keep or disclose data.
When we act as a processor for repository content, your organization decides the legal basis.
Who we share data with
We share personal data only with the service providers (subprocessors) that help us run Puaro, under contracts that limit how they use it:
- Google Cloud (United States): hosting, databases, task queues, and secret storage in the us-central1 region, and Vertex AI through its global endpoint.
- Clerk (United States): sign in, user accounts, organizations, and invitations.
- Resend (United States): sending product, support, contact, and newsletter emails.
- Cloudflare: the Turnstile bot check on our website forms.
- Google Analytics: website analytics, only with your consent.
- Google Ads: advertising measurement in the application.
Other parties receive data because the service works with them:
- GitHub and GitLab: to read the repositories you connect and post results back.
- Slack and Atlassian (Jira): only if you connect them.
- The provider that issued a credential (GitHub, GitLab, OpenAI, Slack, SendGrid, Stripe, or AWS): it receives that credential, and nothing else, during a validity check.
A small number of Puaro staff can see account and scan data when they need it to run and support the service.
We may also disclose data when the law requires it, to protect our users or the service, or as part of a merger or acquisition, in which case we will tell you before your data falls under a different policy.
International transfers
Puaro is based in Israel. Our servers and databases are in the United States, and our providers may process data in other countries. When we transfer personal data from the EEA or the UK, we rely on adequacy decisions (the European Commission and the UK recognize Israel as adequate), on the EU and US Data Privacy Framework where a provider is certified, or on Standard Contractual Clauses with our providers. You can ask us for a copy of the safeguard that applies to your data.
How long we keep data
- Repository copies: deleted when each scan ends.
- Findings, scan history, and commit details: kept while you use Puaro, so you can review and fix leaks. Uninstalling the Puaro GitHub App deletes that installation's repositories, scan history, findings, and pull request and commit details from our database. Disconnecting GitLab, deleting an organization, or closing your account removes the connection, but findings and scan history stay until you ask us to delete them. We delete them within 30 days of a written request to info@puaro.io.
- Integration credentials: deleted when you disconnect the integration, uninstall the GitHub App, or delete your organization. If you use a personal account, disconnect your integrations before you close it, or ask us to delete them.
- Account details: your user record is deleted when you delete your account. The sign up campaign tags are deleted with it, and your account is unlinked from the first steps recorded for a workspace.
- Webhook payloads from GitHub and GitLab: cut down to identifiers when they arrive. What is left is erased 30 days after processing, and the record itself about 30 days after that.
- Jira identity data: deleted when you disconnect Jira, when your Atlassian account is closed, or when we cannot confirm with Atlassian for 14 days that it is still needed.
- Email records: delivery records are kept while your account is active. We keep the fact that you unsubscribed, or that an email bounced, so that we do not email you again.
- Database backups: kept for up to 7 days, then overwritten.
- Contact form messages: kept as long as needed to answer you and follow up, and deleted on request.
- Newsletter: kept until you unsubscribe. A confirmation link expires after 48 hours. If you never confirm, you are not subscribed, and you can ask us to delete the address.
- Logs: application logs are kept for 30 days. Google Cloud keeps its own record of administrator actions for 400 days.
How we protect data
- All traffic to Puaro uses HTTPS (TLS), and our database accepts encrypted connections only.
- Data is encrypted at rest by Google Cloud.
- Every customer's data is separated by an exact tenant filter in the database, so one organization cannot read another's findings.
- Webhooks from GitHub, GitLab, Clerk, Slack, and Resend are rejected unless their signature or secret token is valid.
- Application secrets live in Google Secret Manager, and logs are redacted before they are written.
- Sensitive actions, such as opening a fix pull request or changing integrations, need an organization admin.
- Staff access to customer data is limited to the people who need it.
No system is perfectly secure. If we learn of a breach that affects your personal data, we will notify you and the relevant authorities as the law requires.
Your rights
You can ask us to:
- show you the personal data we hold about you and give you a copy, or send it to another service;
- correct data that is wrong, incomplete, or out of date;
- delete your data;
- restrict or object to how we use it, including any use for direct marketing;
- withdraw any consent you gave.
Israeli law gives you the right to see your data and to have it corrected. If you are in the EEA or the UK, you have all the rights above. Other places give some or all of them.
Email info@puaro.io from the address on your account. We answer within 30 days, and we do not charge for a reasonable request. If your request is about repository content your organization controls, we will pass it to your organization admin.
You can also complain to your local data protection authority, or in Israel to the Privacy Protection Authority.
Emails and marketing
- Service emails (scan results, assignments, support replies, and notices about our terms or this policy) are part of the service, so you cannot unsubscribe from them while you have an account.
- Welcome and onboarding emails have an unsubscribe link that works with one click.
- Newsletter and product updates are sent only if you asked for them. To stop, use the unsubscribe link in the email or write to info@puaro.io.
Cookies
This section also covers similar storage in your browser.
- Strictly necessary on the website: the website stores your cookie choice (
puaro_cookie_consent, 180 days). Cloudflare Turnstile may set a short lived cookie on our forms to tell people from bots. - Strictly necessary in the application: sign in cookies from Clerk keep you logged in. Connecting Jira sets a cookie (
puaro_jira_oauth) for up to 10 minutes. - Interface choices: the application saves filters, table settings, and open tabs in your browser's local storage and session storage. They stay in your browser.
- Analytics on the website (optional): Google Analytics cookies (
_ga,_ga_*) on puaro.io, set only after you click "Accept analytics". If you decline, Google's script does not load at all. With the same consent, puaro.io keeps the campaign tags of your visit in session storage (puaro_signup_tags), which your browser clears when you close the tab. Without consent, nothing is stored, and only the tags in the current page address travel with a sign up link. - Advertising measurement in the application: the Google Ads tag on app.puaro.io sets Google cookies (for example
_gcl_au). You can block them in your browser settings without losing any feature of Puaro.
You can change your website choice at any time with the "Cookie settings" link in the website footer. Withdrawing consent deletes the Google Analytics cookies on puaro.io.
Children
Puaro is a service for businesses and developers. It is not meant for anyone under 18, and we do not knowingly collect their data. If you believe a child gave us personal data, email us and we will delete it.
Changes to this policy
We update this policy when our product or practices change. The date at the top shows the latest version. For material changes, we will tell signed in users by email or in the application before the change takes effect.
Contact
- Company: Puaro Security Inc., Tel Aviv, Israel
- Email: info@puaro.io