Privacy Policy
Last updated: November 2026 · Launch Milestone 16 Nov 2026
We only read cost and execution metadata. We never inspect, replicate, or store table records or lakehouse files.
Ask us and we send you your account, organization and project data, including plans and build records.
Ask us and we delete your organization, its projects, build records and stored credentials within 30 days.
1. What We Collect
Account & Profile Information
When you register or join an organization, we collect your name, email address, and optionally your company name and role. If you sign in using Google, GitHub, or Okta SSO, we receive your name, verified email address, and profile picture from the provider. We do not request or receive access to any other services or data in your identity provider account.
Project Inputs & Prompts
Architecture prompts, business problem statements, functional requirements, and configuration parameters you submit to TeksPlan and TeksBuild. These are used solely to draft plans, construct data models, and generate code diffs for your project.
Execution Logs & Approvals
Audit records of actions taken within the platform, including stage transitions, agent build task statuses, test execution results, and human gate approvals (including the timestamp, approver identifier, and decision channel: web app, email link, Slack, or Microsoft Teams).
Cloud Usage Metadata (TeksOptima)
For connected Snowflake accounts: warehouse names and sizes, credit consumption, query identifiers, execution durations, and query text read from ACCOUNT_USAGE and INFORMATION_SCHEMA. For connected Databricks workspaces: system tables covering billing, compute clusters, SQL warehouse metrics, and job histories. We never read, copy, or store the contents of your database tables or data lake files.
Infrastructure Telemetry (Teksinfra)
Pipeline health metrics, failure event signals, Airflow DAG identifiers, dbt model names, and Snowflake query IDs ingested from the InfraOps worker running inside your network.
2. What We Never Collect (Zero Table Data Guarantee)
No Database Table Contents
Tekspaz never reads, copies, replicates, or stores the underlying business records, customer transactions, or data stored inside your database tables, Snowflake tables, or Databricks lakehouses. All database privileges requested by TeksOptima and InfraOps are strictly read-only on system metadata views.
Credentials Encrypted, Never Shown Again
Some connections need a credential: an OAuth token, a Snowflake key pair, a database password, or a cloud access key for a data source you add. We store each one encrypted at rest with AES-256-GCM and never show it again after you enter it. Disconnecting deletes it, and you can revoke it with your provider at any time.
User Identity Anonymization (Databricks)
User identities in Databricks — query authors, job owners, cluster creators, and email addresses in tags — are replaced by a salted cryptographic hash inside your Databricks workspace before anything leaves your perimeter. The salt remains inside your secret scope and is never sent to Tekspaz, ensuring hashes cannot be reversed by us.
SQL Statement Text Omitted by Default
In Databricks, SQL statement text is not sent to Tekspaz unless you explicitly choose to enable it in workspace settings; otherwise, the field is sent as NULL.
3. Why We Process It
Service Delivery
To execute software planning, generate and test code in isolated sandboxes, verify CI/CD pipelines, deliver incident root-cause analysis, and provide warehouse cost-saving recommendations.
Security & Human Governance
To maintain tamper-evident audit logs of who approved what code change, infrastructure deployment, or database statement.
Account Communications
To send transactional emails such as email address verification, password resets, and critical approval requests.
Platform Improvement
To understand platform performance, aggregate error rates, and improve agentic workflows using anonymized telemetry.
5. How Long We Keep It
Account Data
Account, organization, and project data is kept while your account is active. When you ask us to delete it, we delete it within 30 days.
Usage Snapshots (TeksOptima)
We retain the 30 most recent committed daily snapshots per workspace and purge older records daily. Incomplete or stale uploads are deleted after 24 hours.
Immediate Token Purge on Disconnect
Disconnecting a Snowflake, Databricks, GitHub, or Vercel account immediately deletes the stored access and refresh tokens, preventing any further retrieval of metadata.
6. Your Rights: Export & Erasure
Access, Rectification & Portability
You have the right to request a complete copy of the data associated with your account, correct any inaccuracies, or export your projects.
How Export & Deletion Work Today
There is no self-service export or delete button yet. We handle each request by hand: we export your account, organization and project data, including TeksBuild's build records, and delete it everywhere it is stored within 30 days of your request.
Exercising Your Rights
To request a data export or deletion of your personal data and organization records, email sales@tekspaz.com.
8. Contact & Privacy Inquiries
Data Privacy Officer
For any questions or concerns regarding this Privacy Policy or our data protection practices, please contact our team at sales@tekspaz.com.
Questions about your data or wish to exercise your rights?
Email us for a copy of your data, a correction, or deletion.