This policy explains what Infersync Ltd ("Infersync", "we", "us") collects when you use infersync.com and the Infersync application, who else processes it, how long we keep it, and the rights you have over it.
Infersync Ltd is registered in England and Wales, company number 16434490, at 66 Paul Street, London, EC2A 4NA, United Kingdom. We are the data controller for the personal data described here. For anything in this policy, write to hello@infersync.com.
What we do not collect
We do not read your source code. Your agents run on your own machines, and neither the runner nor the Infersync GitHub App sends us the contents of your repositories, so that data never reaches us and cannot be passed to anyone else, including any AI provider.
What we collect
- Account data. Your name, email address and GitHub account identifier, taken from GitHub when you sign in.
- Access requests. The email address and the line you leave on the access form.
- Workspace data from GitHub. Repository names, and pull request titles and states, with who merged or closed them. The organisations you belong to, read once when you sign in, to offer you a workspace your team already has.
- Records you create in Infersync. Goals, steps, notes, skills and comments, and the record of each agent run: the actions it took (file names and commands, not file contents), how long it ran, the result of the check and its pull request.
- What you type in the bar. And the goal and step text needed to plan the work and answer you.
- Usage data. On this website: pages visited, approximate location derived from IP address, browser and device type, and timestamps. The product itself collects no analytics.
- Technical data. IP address, request logs, and error reports generated when something fails.
Why we use it, and our legal basis
- To provide the service (performance of a contract): planning and handing out work, watching agent runs, checking the work, and answering in the bar.
- To keep it working and secure (legitimate interests): error monitoring, rate limiting, abuse prevention, and understanding which features are used.
- To send service messages (legitimate interests), and marketing email only where you have consented. You can withdraw consent at any time.
- To meet legal obligations, including tax and accounting records.
We do not sell your personal data, and we do not use it to train AI models.
Who else processes it
We use the sub-processors below. Each acts on our instructions and is bound by contract to protect the data it handles.
- Cloudflare. Hosting, the database and request logs. Handles all service data, at rest and in transit, including request identifiers such as IP address for abuse prevention.
- GitHub. Sign-in and the integration. Receives account identity; tells us about repositories and pull requests.
- Groq. The model the service uses to plan goals and answer in the bar. Receives the goal, step and bar text, never code.
- Resend. Email. Receives your email address and the message.
- Slack. Notices to our own team, such as a request for access. Receives your name, GitHub login and email.
- Cal.com. Booking a call. Receives the name and email you book with.
- Google Analytics, PostHog and Sentry. This website only: page views, usage events, error reports and technical identifiers such as IP address and device information.
We may also disclose personal data where the law requires it, or in connection with a merger, acquisition or sale of assets, in which case we will tell you before your data becomes subject to a different privacy policy.
International transfers
Your data is processed in the United Kingdom, the European Union and the United States. Where data leaves the UK or EEA, transfers rely on the UK International Data Transfer Addendum or the EU Standard Contractual Clauses, alongside the safeguards our providers operate.
How long we keep it
- Account and workspace data: while your account is active.
- After an admin deletes a workspace: kept 30 days so it can be restored, then deleted for good. Ask us and we delete it sooner.
- Request logs: up to 7 days.
Your rights
Under the UK GDPR and EU GDPR you have the right to access your data, to have it corrected, to have it deleted, to restrict or object to how we use it, and to receive a portable copy. Where we rely on consent, you can withdraw it at any time.
Write to hello@infersync.com and we will respond within one month. You can uninstall the Infersync GitHub App at any time from your GitHub settings, which revokes our access immediately.
If you are unhappy with how we have handled your data, you can complain to the UK Information Commissioner's Office at ico.org.uk, or to your local supervisory authority in the EEA.
Security
Traffic is encrypted with TLS 1.2 or above, and data at rest is encrypted by our infrastructure providers. Access is role-based and scoped to a workspace, so one workspace cannot see another's data. Each machine's key is stored encrypted. No system is perfectly secure, but we monitor for errors and suspicious activity, and aim to acknowledge a reported security issue within one business day. Report issues to hello@infersync.com.
Cookies and analytics
The product uses only the cookies needed to sign you in and keep your session; blocking them stops you signing in. This website uses analytics cookies (Google Analytics and PostHog) to see which pages are read.
Children
Infersync is a business product and is not directed at anyone under 16. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.
Changes
We will update this policy when our practices change, and change the date at the top when we do. Material changes will be notified by email or in the product before they take effect.
Contact
Infersync Ltd, 66 Paul Street, London, EC2A 4NA, United Kingdom. hello@infersync.com. See also our Terms of Service and Support page.