Privacy Policy
Effective 16 November 2026.
This policy explains what personal data Intentric collects, the roles we act in, how the data is used, who it is shared with, and the choices and rights available to you. It covers both this marketing website and the Intentric product itself; see Scope, just below, for how those two differ.
Intentric is operated by Kanata Florida, LLC, a Florida limited liability company doing business as Intentric, of 2213 NW 1st Pl, Cape Coral, FL 33993, United States. Where this policy says “we” or “us”, it means that company. Whether we are the controller or a processor depends on the data; the next sections say which.
Scope: This Website vs. the Intentric Product
This policy covers two different things, and it is worth separating them clearly up front:
- This website (the public pages at this domain, including this one) is a site of its own, separate from the Intentric product and its sign-in page. These pages have no login of their own, no user account system and no customer database. The only way to give us information through them is by submitting the contact/request-access form, which a hosted form-delivery service (Web3Forms) relays to our inbox (see Sharing).
- The Intentric product is the separate, authenticated platform that organizations use, once onboarded, to turn infrastructure intent into policy-gated, human-approved, audited cloud changes. It has its own accounts, organizations, and data. A sandbox, where we offer one, runs the same workflow against a simulated cloud for an anonymous, temporary session.
Most of what follows about accounts, infrastructure intent, connections and billing applies to the product, not to this marketing site. Where a section applies to only one of the two, it says so.
Our Roles: Controller and Processor
| Data | Our role | Whose instructions we follow |
|---|---|---|
| Account and marketing data: contact-form submissions, billing contact details, and the information needed to run an account, secure it and bill for it | Controller | Our own, as described in this policy |
| Customer content: the requests, deployment definitions, plans, approvals, configuration, connections and records an organization puts into or generates through the product | Processor | The organization’s, which is the controller of the data it holds |
Where the product holds personal data about the people in an organization, such as names and email addresses, the organization decides who is a member and what they can do, and we process that data on its behalf. We also use a member’s sign-in details ourselves to secure the service and to bill for it. Intentric is the controller of member account data (name, email address, sign-in details) for running accounts and the service. Within an organization’s workspace, the organization is the controller of the data it manages, and Intentric processes that data on its instructions.
A data processing addendum is available for customers who need one; see the Data Processing Addendum page.
What We Collect
What we collect depends on whether you are browsing this marketing website or using the Intentric product.
| Where | Category | Examples |
|---|---|---|
| This website | Contact & access-request data | Name, work email, company, your role if you give it, what you are asking for (a demo or a conversation with sales), and whatever you write in the message field, if you submit the contact form, together with the page you sent it from, the page that linked you there, and any campaign tags in that page's address. The form sends them to the hosted form-delivery service, which relays them to our inbox; if the service cannot be reached, the form instead opens your own email program with the message ready to send |
| Intentric product | Account & identity data | Name, email, organization, memberships and invitations, the identity provider a person signs in with, passkeys, recovery codes and sessions |
| Intentric product | Infrastructure intent & configuration data | Natural-language requests, the plans and resource configurations generated from them, and approval decisions |
| Intentric product | Usage & audit data | API usage, records of each AI run (the provider, model and token use, but not the text of the request or reply), notifications, and audit entries, including the identity of whoever took an action and when |
| Intentric product | Billing data | Billing contact details, subscription and quote history; card details are handled directly by our payment processor and do not pass through our systems |
| Intentric product | Connections you set up | The settings and short-lived tokens needed to use the services an organization connects (see Connections made on your behalf) |
| Sandbox | Temporary session data | An anonymous, temporary organization with simulated infrastructure, removed when its time limit passes |
How We Use It
- To respond to inquiries submitted through the contact/request-access form.
- To provide, operate, and maintain the Intentric product for customers who use it, including generating infrastructure plans, checking them against your rules, routing them for human approval, and executing approved plans.
- To maintain the audit trail that records who did what, and when, so customers (and we) can review and reconstruct activity on their account.
- To secure the service: detecting abuse, enforcing rate limits, and investigating suspected credential compromise.
- To bill for the product, via our payment processor.
- To comply with legal obligations and enforce our agreements.
We do not use data collected through this marketing website to make automated decisions about you, and we do not sell it.
For visitors and customers in the EU and UK, we rely on these legal bases:
- performance of our contract with you or your organization (accounts, running the service, billing);
- our legitimate interests (securing the service, preventing abuse, improving it, and business communications with customers and prospects);
- consent, where we ask for it;
- compliance with legal obligations (tax and accounting records).
Connections Made on Your Behalf
The product acts for an organization by connecting to services the organization chooses. Each connection is set up by an administrator of that organization, who decides which to use. What we hold and send for each:
- Cloud accounts. When an approved change runs, the product uses a short-lived credential for the organization’s own Amazon Web Services, Microsoft Azure or Google Cloud account. We do not store long-lived cloud credentials. The cloud provider processes the request as the organization’s own account.
- Email and chat. Notifications go to each member’s in-product inbox, and an organization can also have them sent by email or posted to Slack or Microsoft Teams channels. Email is sent through the organization’s own sender: it signs in to its Google Workspace or Microsoft 365 account, or uses an email provider or mail server it configures. A notification carries identifiers and display facts, never the text of a comment.
- Document storage mirrors. An organization can mirror a deployment's definition, one way, to an S3 bucket, a Google Drive folder or a OneDrive or SharePoint library it controls. We hold the connection’s settings, and the credential used to write to it is kept in a secrets store rather than in the product’s database. Nothing is read back from the mirror, and a document is checked for credential-shaped text before it leaves.
- Source control. An organization can bind a deployment's definition to a git repository, so that the product can read it and propose changes from it. A change from the repository still goes through the same approval.
- Sign-in and directories. A person can sign in with Google, Microsoft, GitHub, GitLab or Bitbucket, or through their organization’s own single sign-on provider, and an organization can provision its members from its identity provider. We receive the identity details the provider returns at sign-in, such as a name and email address, and keep the link between that identity and the person’s account.
- AI processing. When you describe infrastructure to Intentric AI, ask it about your deployments, or generate a runbook, the text of your request and the context needed to answer it are sent to OpenAI, which generates the response. For a deployment that context can include the names and settings of its resources, its recent changes, and its verification and drift findings. Before anything is sent, text that looks like a credential, such as an access key, private key, password or token, is replaced with a placeholder. That detection is not exhaustive, so please do not put credentials in a request. We do not train or fine-tune models on this data. Under OpenAI’s API terms that data is not used to train OpenAI’s models, and OpenAI keeps abuse-monitoring logs for up to 30 days. See Responsible AI for what the AI can and cannot do.
Sharing and Sub-processors
We do not sell personal data, and we do not share it with third parties for their own marketing purposes. We share data only as needed to operate the service:
- Service providers (sub-processors) who help us run the service, such as hosting, payment processing, AI model processing, and Web3Forms, the hosted form-delivery service that relays contact-form submissions to our inbox. They receive only what they need to perform their function and are bound by confidentiality and data-protection obligations. The current list, with each provider’s purpose and the data involved, is on the Sub-processors page.
- Cloud providers and other connected services acting on the organization’s behalf, as described above; these are the organization’s own choices rather than ours.
- Legal disclosures. We may disclose data if required by law, subpoena, or other legal process, or to protect the rights, property, or safety of Intentric, our customers, or others.
- A change in business control (merger, acquisition, or asset sale). We would require any successor to honor the commitments in this policy for data collected under it.
Each customer organization’s data is kept separate from every other customer organization’s data; it is not pooled or shared across organizations.
How Personal Data Is Protected
- Encrypted before it is stored. The personal data the product holds about people (names, email addresses, and the records that tie a person to an organization, a sign-in provider, a passkey or a session) is kept in a separate, listed set of places, and the identifying parts are encrypted before they are stored. Passkeys and recovery codes are held in a form that cannot be read back.
- Records refer to people by reference. The audit trail identifies who acted by an opaque reference rather than by name or address, which is what lets a person be erased without disturbing the record of what happened.
- No long-lived cloud credentials. Execution runs under a short-lived credential issued per job, which expires when the job ends.
- Hashed secrets. Issued API keys and similar bearer credentials are hashed at rest; the plaintext is shown once, at issuance.
No security program can guarantee absolute protection against every possible attack. The Security page describes the controls in more detail.
Cookies and Local Storage
This website sets no cookies and keeps nothing in your browser’s local storage, and it runs no analytics or advertising. The Intentric product uses cookies and browser storage that are needed to keep you signed in and to remember your settings. Each one is listed, with its purpose and lifetime, in the Cookie Policy.
Retention
- Contact/access-request submissions are kept as long as needed to respond to your inquiry and for a reasonable follow-up period, then deleted or anonymized.
- This website runs no analytics and builds no visitor profiles. The servers that deliver this website keep standard access logs (IP address, time, page requested, browser), used for security and troubleshooting, for no longer than 30 days.
- Product account and configuration data is retained for the duration of the customer relationship. After termination you have thirty (30) days to export it, and after that we may delete it, subject to any legal hold or legal obligation to retain it.
- Within the product, records are kept for set periods by class: financial records for seven years; the audit trail for 400 days; AI run records for 180 days; and notifications and webhook delivery records for 30 days. An organization can lengthen any of these periods but not shorten them. A legal hold placed by an organization administrator stops deletion while it is in force.
- Brokered cloud session credentials are short-lived by design and expire automatically when the job that requested them ends; we do not retain them past that point.
- A sandbox session is anonymous and temporary, and is removed when its time limit passes.
Your Rights, Export and Erasure
Depending on where you are located, you may have rights over your personal data under laws such as the EU/UK General Data Protection Regulation (GDPR) or the California Consumer Privacy Act and California Privacy Rights Act (CCPA/CPRA). We aim to honor these rights for anyone they apply to, regardless of location, including the right to:
- Know what personal data we hold about you and how it is used.
- Access a copy of your personal data.
- Correct inaccurate personal data.
- Request deletion of your personal data, subject to legitimate exceptions (for example, records we are required to retain, or that a legal hold covers).
- Object to or restrict certain processing, and request portability of data you provided to us.
- Not be discriminated against for exercising any of these rights.
Export. Every item of personal data the product holds is listed in an inventory that is checked whenever the product is built, so an export can find all of it. A member can download what an organization holds about them, and an administrator of the organization can download a member’s data, without contacting us first. Secrets such as passkeys and recovery codes are withheld from an export, because handing them back would turn a privacy right into a way to obtain credentials.
Erasure. Erasing a person makes their data permanently unreadable, including from a backup, and we cannot undo it on request. Their sessions, sign-in links, passkeys and recovery codes are removed with it. Erasure is refused while a legal hold covers the person. The audit trail is not changed, because it refers to people by reference.
One organization at a time. Because each organization is the controller of the data it holds, a request covers one organization; if you belong to more than one, exporting or erasing from one does not affect the others. An organization’s export about someone else covers only what that organization holds, and does not reveal where else the person has an account.
To exercise any of these rights, or if you would rather we handle it for you, contact us at the address in Contact, below. We will verify your request and respond within the time required by applicable law. This section describes the rights we aim to honor directly; it is not a claim of participation in any specific third-party-certified privacy compliance program.
International Transfers and Regional Notices
Personal data is processed and stored in the United States, on Amazon Web Services. Where personal data is transferred from the EU, EEA or UK, Intentric relies on the European Commission’s Standard Contractual Clauses and the UK International Data Transfer Addendum. The Sub-processors page lists each provider’s location.
Privacy questions and requests go to privacy@getintentric.com.
Intentric does not sell personal information or share it for cross-context behavioural advertising. The website loads no advertising or analytics trackers. A Global Privacy Control signal is honoured as a request to opt out of sale and sharing.
Children’s Privacy
Neither this website nor the Intentric product is directed at children, and we do not knowingly collect personal data from children under 13 (or the equivalent minimum age where you live, such as 16 in parts of the EU). If you believe a child has provided us with personal data, contact us and we will delete it.
Changes to This Policy
We may update this policy as the product, this website, or applicable law changes. We will update the effective date at the top when we do. For material changes that affect Intentric product customers’ data, we will aim to provide more direct notice (for example, by email) in addition to updating this page. We encourage you to review this policy periodically.
Contact
Questions about this policy, or requests to access, correct, or delete your personal data, can be sent to:
Or by post to Kanata Florida, LLC, 2213 NW 1st Pl, Cape Coral, FL 33993, United States.
To report a security vulnerability, please follow the responsible disclosure process on the Security page rather than disclosing it publicly.