TestGuard AI — Privacy Policy (United States)
DRAFT FOR ATTORNEY REVIEW. NOT LEGAL ADVICE. This draft was prepared from the TestGuard code at commit
ad40eab. Every retention period below matches what that code does. A licensed attorney must review it before anyone relies on it or publishes it. Every[BRACKETED]item is a placeholder; seeLAUNCH-CHECKLIST.md.
Effective date: EFFECTIVE DATE
Who we are: Francis Properties LLC ("we", "us"), 7575 Laurel Oak Dr, Suwanee, GA 30024. TestGuard AI is the name of our product.
Privacy contact: support@testguardai.com
This policy explains what TestGuard AI collects, why, how long we keep it, who we share it with, and the choices you have. TestGuard AI is offered only in the United States.
1. What we collect
From GitHub when you sign in
- Your GitHub user id, login, and display name.
- The TestGuard AI installations you can access, and your role (admin or member) in each.
- Sign-in uses GitHub OAuth with the
read:orgscope. The GitHub token is used only during sign-in and is not stored. We do not store your email address from GitHub.
From GitHub when you install the App
- The installation's account name and whether it is an organization or a user account.
- The repositories the installation can see: the full repository name and whether scanning is enabled.
From your pull requests
- Pull request metadata: repository name, pull request number, base and head commit ids, and when the pull request closed.
- The list of files the pull request changes.
- The base and head contents of the changed files TestGuard AI analyzes (tests, snapshots, and CI configuration), and your
.testguard.ymlconfiguration file. These are read to run the analysis. - The ids of the check run and the summary comment TestGuard AI posts, so it can update them later. TestGuard AI reads a pull request's comments only to find its own summary comment.
What we create and store from that
- Scan results: the findings report for a commit, with file paths, line numbers, messages, and short excerpts of the changed test lines around each finding.
- Scan job records (queued, running, done, or failed) and webhook delivery ids, so work is not done twice.
- An audit log of actions: sign-ins, sign-outs, scans, and data purges, with the user or system that took the action.
Feedback you give
- A reviewer's note that a finding is a false positive or should stand, the decision, and the rule and file it applies to, plus any suppression it creates.
- If you email us for support, we keep that correspondence for 90 days.
Billing
- Stripe customer id and subscription id, plan, subscription status, number of billed repositories, payment grace end date, and the ids of Stripe events we have processed.
- Your GitHub account name is sent to Stripe as the customer name.
- Which version of these Terms and the Privacy Policy you agreed to at checkout, and when.
Cookies and sessions
tg_session: keeps you signed in. It lasts 8 hours, isHttpOnlyandSameSite=Lax, and isSecureover HTTPS. We store only a keyed hash of the session id, not the id itself.tg_oauth: a one-time value that protects the sign-in step. It lasts 10 minutes.- We use no advertising, analytics, or tracking cookies, and TestGuard AI sends no telemetry.
Network information
- When you are not signed in, your IP address is used in memory to rate-limit requests. TestGuard AI does not store it in its database. Our hosting provider may keep server logs for 7 days.
2. What we do not collect
- No card numbers. You enter card details on Stripe's hosted checkout page. They never reach TestGuard AI. Stripe holds invoices, payments, and tax records.
- No full repository copy. TestGuard AI does not clone your repository. It fetches only the changed files it analyzes and your configuration file, through the GitHub API.
- No running your code. TestGuard AI never runs your tests or any code from your repository, and does not read CI results or logs.
- No AI processing. As of the effective date, TestGuard AI does not send your code to AI or large-language-model services and does not use it to train any model. We will give at least 60 days' notice before any such change, and you can cancel before it takes effect (see the Terms of Service).
3. Why we use it
- To run the analysis and post the check run and pull request comment.
- To show findings and the feedback queue in the dashboard, and to control who can see them.
- To bill paid plans and apply plan limits.
- To keep the service secure, prevent abuse, and keep an audit trail.
- To respond to support requests and legal obligations.
We do not sell your personal information, and we do not share it for targeted or cross-context behavioral advertising.
4. Who we share it with (subprocessors)
| Subprocessor | Purpose |
|---|---|
| GitHub | Sign-in, reading pull request files, posting checks and comments |
| Stripe | Payments, subscriptions, invoices, and tax records |
| Fly.io (Fly.io, Inc.) | Hosting the service and its database (United States) |
| ImprovMX (ImprovMX Incorporated, United States) | Email forwarding: ImprovMX forwards email sent to support@testguardai.com |
We may also share information if the law requires it, to protect rights and safety, or as part of a merger, acquisition, or sale of assets, under a duty to keep this policy's protections.
5. How long we keep it
TestGuard AI deletes data automatically. The purge runs when the service starts and then every hour. Some periods are chosen at setup within a fixed range; the table shows the values for this launch, with each allowed range.
| Data | Kept for |
|---|---|
| Scan results, scan jobs (once finished), audit log, webhook delivery ids | Retention period: 90 days (allowed range 30 to 90 days) |
| Feedback | Retention period, unless it is the record behind an active suppression |
| Suppressions | Active ones while the repository is present; inactive ones for the retention period |
| Installation and repository records | Deleted when the App is uninstalled or the repository is removed from the installation |
| Data tied to a removed installation or repository (scans, jobs, feedback, suppressions, check-run and comment ids, memberships) | Removal grace period: 30 days after removal (allowed range 7 to 90 days) |
| Check-run and comment ids | Closed pull request period: 90 days after the pull request closes (allowed range 7 to 90 days), or the retention period if unused |
| Users who have not signed in, with their sessions and memberships | Inactive user period: 90 days without a sign-in (allowed range 30 to 365 days), unless they still belong to an existing installation. Their feedback then shows "a former user". |
| Sessions | 8 hours, or deleted at sign-out |
| Sign-in check values | 10 minutes, or deleted once used |
| Billing records (Stripe ids, plan, status, processed event ids), and your recorded acceptance of these Terms and the Privacy Policy at checkout | 5 years after the last billing activity or the uninstall, whichever is later (fixed) |
6. Security
- TestGuard AI reads only the files it needs and never runs your code.
- Secrets (GitHub App, OAuth, webhook, session, and Stripe keys) come only from the server environment and are never logged. Request bodies and webhook signatures are never logged.
- GitHub webhooks are checked against a shared secret signature before they are processed.
- Session ids are random and stored only as a keyed hash. Cookies are
HttpOnlyandSameSite=Lax. - Every form submission must come from TestGuard AI's own site, and every one that changes your data also needs a matching anti-forgery token.
- Pages send a strict Content-Security-Policy and other protective headers. Requests are rate-limited.
- No method is perfectly secure. See https://testguardai.com/security for the full, current details.
7. Your privacy rights
Depending on your state (for example California, Colorado, Connecticut, Virginia, and others), you may have the right to:
- Know and access the personal information we hold about you;
- Delete it;
- Correct it;
- Opt out of sale or targeted advertising (we do neither);
- Not be treated differently for using these rights.
To make a request, email support@testguardai.com from, or naming, the GitHub account involved. We will verify the request by confirming control of that GitHub account, and respond within the time the law requires (for example 45 days under California law). An authorized agent may make a request for you with proof of authority. If we deny a request, you may appeal by replying to our answer; we will respond to the appeal within the time the law requires.
You can also delete most data yourself: uninstalling the GitHub App or removing a repository starts deletion under section 5. Billing records are kept for the fixed period above because we need them for tax and accounting.
8. Children
TestGuard AI is not directed to children. We do not knowingly collect personal information from children under 13, and you must be 18 or older to use TestGuard AI. If you believe a child has given us information, contact us and we will delete it.
9. Data breach
If a security breach affects your personal information, we will notify you and any regulators as required by applicable US state law, without unreasonable delay.
10. Changes to this policy
We may update this policy. For a material change, we will give at least 60 days' notice by email or in the dashboard before it takes effect. The effective date at the top shows the current version.
11. Contact
Francis Properties LLC
7575 Laurel Oak Dr, Suwanee, GA 30024
support@testguardai.com