Privacy policy

SaviQora is operated by Madhusudan Kallur Purushothaman. For any privacy question, or to ask what data we hold about you, email contact@saviqora.com.

Account data: your name, work email address, job title if you provide one, and the organization you belong to.

Content you create: requirements, test cases, executions, defects, evidence files and automation definitions.

Operational records: sign-in times, the IP address a session was created from, and an audit trail of actions taken in your organization. These exist so that your administrators can see who did what.

We do not store SAP credentials. SaviQora keeps a reference to a secret held in a secret manager and resolves it only at the moment of use; the credential never enters our database, logs, reports or screenshots.

We do not store card details. When online payment is introduced it will be handled by a payment provider, and card numbers will never reach SaviQora.

There is no third-party analytics or advertising tracking on this site or in the product.

Test data is content you control. We strongly recommend synthetic or masked data. The product generates synthetic identifiers for exactly this reason, and the demonstration environment is labelled so it is never mistaken for a real tenant.

Data is held on servers in Europe, operated by our hosting provider. Backups, once established, will be held in the same region.

While your subscription is active, for as long as you keep it. After cancellation, a retention period of 30 days applies, during which you can export or reactivate. After that, content is deleted. Records we are required to retain for accounting purposes are kept for as long as the law requires.

You can ask for a copy of your data, ask for it to be corrected, or ask for it to be deleted. Email us and we will act on it. Organization owners can also export their organization’s data from within the product.

Self-service export and deletion are on the roadmap and not yet available in the interface; until they ship, both are handled on request. We would rather tell you that than imply a button exists.