Privacy Policy

TestingOps (operated by Cunda Yazılım) · Last updated 9 October 2026

TestingOps is a test-management and test-automation platform. This policy explains what data we process when you use the service at testingops.ai and when you connect third-party tools (Atlassian Jira and Confluence, GitHub, GitLab, Bitbucket, Linear and similar) to it.

1. Data we collect

• Account data: name, e-mail address, organisation and role, used to sign you in and to attribute your work.
• Content you create: projects, test scenarios and cases, runs, defects, comments and uploaded documents.
• Connected-tool data: when you authorise a connection (OAuth) or enter an API token, we access the issues, pages, repositories and metadata you have chosen to link, and we store the access and refresh tokens needed to keep that connection working. We also record the account name or e-mail the token belongs to, so you can see which account is connected.
• Technical data: server logs (IP address, request path, timestamps) kept for security and troubleshooting.

2. How we use it

• To provide the service: sync linked issues and documents into your project's knowledge base, generate and run tests, and file findings back into your tracker when you ask us to.
• AI features send the relevant content (for example an issue text or a test case) to the model provider configured for your organisation. Content is not used to train models.
• We do not sell personal data and we do not use it for advertising.

3. Third-party tool connections (OAuth)

When you click "Connect with Atlassian/GitHub/GitLab/Bitbucket/Linear" you are taken to that provider's own consent screen. We request only the scopes needed to read the linked content and, where you use the feature, to create issues. Tokens are stored on our servers, used solely for the connection they belong to, refreshed automatically, and deleted when you remove the connection. Synced content (issue and page text) may be cached for longer than 24 hours so that it can be searched; it is removed when the link or the project is deleted. You can revoke access at any time from the provider's security settings.

3a. TestingOps Tester Agent app for Jira (Atlassian Forge)

If your Jira administrator installs the TestingOps Tester Agent app from our installation link, the app runs on Atlassian's Forge platform inside your Jira site. It does the following and nothing else:

• Reads work items (summary, description, status, labels, assignee, reporter, priority) and comments in the projects where it is triggered, and the display name of the person who triggered it, so that its answers can be addressed to that person.
• Sends those events to TestingOps (testingops.ai), where the rules your organisation configured decide whether to act. TestingOps keeps an audit record of every event and decision (item key, rule, outcome, the text it proposed) so you can see why the agent did or did not act.
• Writes back to Jira only as the app user "TestingOps Tester Agent": comments, an acceptance-criteria section in the description, or a status transition, and only when a rule or an explicit approval from a person in Jira asks for it.
• Stores in Forge app storage only the pairing code that links your site to your TestingOps organisation and the app's own account id. No work-item content, comment text or personal data is kept in the app.
• Honours Atlassian account closure. Once a day TestingOps reports the Atlassian account ids it holds in the audit log to Atlassian's personal data reporting API; for accounts that were closed or whose profile changed, the stored display names are erased. Uninstalling the app erases the stored names for that site immediately.

Content forwarded to TestingOps is processed under sections 2, 4 and 5 of this policy: it may be sent to the AI model provider configured for your organisation, is hosted in the EU, is not used to train models, and is deleted with your organisation's data. Uninstalling the app from Jira, or removing the pairing in the app's admin page, stops all processing immediately. The app requests the Jira scopes read:jira-work, write:jira-work, read:jira-user and storage:app.

4. Where data is stored and who processes it

Data is hosted on Amazon Web Services in the European Union (Frankfurt, eu-central-1). Sub-processors are limited to hosting (AWS), the AI model providers selected for your organisation, and the test-execution service RunningOps operated by the same company. Every sub-processor acts on our instructions under a data-processing agreement.

5. Retention and deletion

Account and content data are kept for as long as your organisation uses the service. Connected-tool tokens are deleted immediately when a connection is removed. Logs are kept for up to 90 days. On termination we delete your organisation's data within 30 days on request.

6. Security

Traffic is encrypted in transit (TLS). Access to production systems is limited to named administrators and audited. Organisations are isolated from each other; customer users can only see the projects assigned to them.

7. Your rights

You can access, correct or delete your personal data and withdraw consent for tool connections at any time. Requests under the GDPR or the Turkish KVKK law can be sent to the contact below; we answer within 30 days.

8. Contact

Cunda Yazılım · testingops.ai/legal/contact