Privacy Policy

Effective November 3, 2026 · Zigitech Solutions Inc

Draft — this document is pending legal review and may change before it takes effect.

1. Who we are and what this covers

RepoHelpdesk is operated by Zigitech Solutions Inc, a Florida corporation ("we", "us"). This policy explains what personal information we collect through our website, the RepoHelpdesk app, the Agent, the chat widget, the browser extension and our integrations (the "Service"), and what we do with it.

We handle personal information in two roles:

• As a controller, for information about our own customers and visitors: account details, billing, support conversations and website visits.
• As a processor, for Customer Data our customers put into the Service. That includes code, tickets, chats, and information about their end users, such as people who use a customer's Customer Assistant or Guide. Our customer decides how that data is used, and their privacy notice applies to it. If you're an end user of one of our customers, please contact that customer about your data. We'll help them respond.

2. What we collect

Information you give us

• Account details: name, email address, password (stored only as a secure hash), organization, role, and the projects and permissions you're given.
• Billing details: billing contact, address and tax ID. Card details go straight to Stripe. We never see or store your full card number.
• Support and communications: messages you send us, and any chat you choose to share with our support team.

Information from sign-in and integrations

• If you sign in with Google or Microsoft, we receive your name, email address and an account identifier. We don't receive your password.
• When you connect GitHub, GitLab, Bitbucket, Azure DevOps, Jira, Slack, Microsoft Teams or another tool, we receive the access token and account details needed to run the integration. Examples are your username in that tool and the repositories, projects or channels you choose to connect.

Information collected automatically

• Usage metadata: who asked a question and when, which project and channel it came from, how much AI it used, response times and errors. This is what we use for usage reports, billing and keeping the Service running.
• Device and log data: IP address, browser and operating system, Agent version, and security logs such as sign-ins.

Customer Data

Customer Data is the code, tickets, documents, database results, chats, Playbooks and files our customers connect to RepoHelpdesk. Where it's kept depends on how the Agent runs:

• Self-hosted Agent: repositories and chat content stay on the customer's own server. Our cloud service relays messages between users and the Agent without storing their content.
• Managed Agent: repositories and chat history are stored on a dedicated server we run for that customer.
• Shared chats: if a customer shares a chat with our support team, we can read it, read-only, for the period they choose, and every view is logged.

The chat widget and browser extension

The widget appears only on websites the customer's project has allowed. The browser extension checks the address of each page you open so it can tell whether that site is allowed. It doesn't record or send us your browsing history. On an allowed site, when you use the assistant, it can capture a screenshot of the page and a log of the page's recent console messages and network requests to help answer your question. The log has no request or response bodies or headers, and values that look like credentials are removed. That information goes to the project's Agent and AI model, like the rest of the chat.

3. AI processing

To answer a question, the Agent sends the question and the few code excerpts or data it needs to an AI model:

• Your own key: if the customer connected their own AI provider account, the Agent sends requests directly to that provider. That provider's terms and privacy policy apply, and the requests don't pass through our servers.
• Managed AI: if the customer uses AI through our account, requests go to our AI providers (listed in section 6) on our behalf. The provider processes the data only to return a response, and doesn't use it to train its models. We choose providers whose terms guarantee this.

We don't use Customer Data to train AI models. The Agent removes passwords and keys it finds in code before including that code in an answer.

4. How we use information

• To provide, maintain and secure the Service, including sign-in, permissions, relaying messages and running integrations.
• To bill you and to enforce plan and usage limits.
• To send service emails, such as invites, sign-in links, approval requests, billing receipts and important changes.
• To respond to support requests.
• To detect and prevent fraud, abuse and security incidents, and to enforce our Terms.
• To understand how the Service is used, using aggregated or de-identified usage metadata, and to improve it.
• To comply with legal obligations.

If you sign up for product news, we'll email it to you. You can unsubscribe from any marketing email. We don't sell or rent personal information, we don't share it for cross-context behavioral advertising, and we don't use it for automated decisions with legal effects.

Legal bases (EEA and UK)

Where GDPR or UK GDPR applies, we rely on: performance of our contract with you (providing the Service); our legitimate interests (security, fraud prevention, improving the Service, and business communications to customers); legal obligations (tax and accounting); and consent where we ask for it, which you can withdraw at any time.

5. Google user data

RepoHelpdesk's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. We use Google sign-in data only to sign you in and identify your account. We don't use it for advertising, and we don't let humans read it except with your consent, for security, or as required by law.

6. Who we share information with

We share personal information only with service providers that help us run RepoHelpdesk, under contracts that limit them to processing it for us:

We may also disclose information:

• To integrations you connect, when you tell the Service to send data there, for example posting an answer to Jira or Slack.
• When required by law or valid legal process. Where we're allowed to, we'll tell the affected customer first.
• To protect the rights, safety or security of our users, the public or RepoHelpdesk.
• To a buyer or successor if we're involved in a merger, acquisition or sale of assets. This policy would continue to apply to your information.

7. Cookies and similar technology

We use only cookies and browser storage that are needed for the Service to work: keeping you signed in, remembering your settings, and protecting against attacks. We don't use advertising cookies or cross-site trackers, so we don't show a cookie consent banner. If we ever add analytics or other non-essential cookies, we'll update this section and ask for consent where the law requires it.

8. How long we keep information

• Account details are kept while your account is open.
• Usage metadata and logs are kept as long as we need them for billing, usage reporting and security, and then deleted or de-identified.
• Customer Data we hold, for example on a Managed Agent server, is deleted within 30 days after the subscription ends, unless the customer asks us to delete it sooner or the law requires us to keep it.
• Billing records are kept as long as tax and accounting law requires.
• Backups expire on a regular schedule.

9. Security

We encrypt data in transit and at rest, and we limit access to our systems to the people who need it. AI provider keys are kept only where requests to the provider are made, and are encrypted on Agent servers. Passwords are stored only as secure hashes. No system is perfectly secure. If a breach affects your personal information, we'll notify you and the relevant authorities as the law requires.

10. International transfers

We're based in the United States, and our providers process data there. If you're outside the US, your information will be transferred to the US. Where the law requires it, we protect those transfers with safeguards such as the European Commission's Standard Contractual Clauses.

11. Your rights and choices

Depending on where you live, you may have the right to access, export, correct or delete your personal information. You may also be able to object to or restrict some processing, withdraw consent, and opt out of the sale or sharing of personal information. We don't sell or share personal information in that sense. California residents have these rights under the CCPA/CPRA, and residents of the EEA and UK have them under GDPR.

To use any of these rights, email privacy@repohelpdesk.com. We'll verify your identity, respond within the time the law allows, and won't treat you differently for exercising your rights. You can also complain to your local data protection authority. If your data is Customer Data controlled by one of our customers, we'll pass your request to them.

12. Children

RepoHelpdesk is a business tool and isn't meant for anyone under 18. We don't knowingly collect information from children. If you believe a child has given us personal information, contact us and we'll delete it.

13. Changes to this policy

We'll post any changes here and update the date at the top. If a change is material, we'll notify account owners by email or in the app before it takes effect.

14. Contact

Zigitech Solutions Inc
Privacy questions and requests: privacy@repohelpdesk.com