Privacy Policy

Effective Date: October 23, 2026 · Website: https://krion.ai · Privacy Contact: support@krion.ai

Last updated: October 23, 2026

Privacy at a Glance

The key points in plain language. Each one opens the section that explains it in full, and the complete document follows in 37 sections.

What we collectAccount and profile details, subscription and billing information, plus the technical and usage data needed to run the platform.Section 4Your prompts and projectsWhat you submit to build or change an app is “Project Content.” We process it to do the work you asked for; avoid putting unnecessary sensitive information in it.Section 5How we use itTo build and run your apps, manage your subscription, secure the platform, answer your support requests, and improve the product.Section 7AI providersPrompts and relevant project content are sent to third-party AI models so they can generate and modify your software.Section 11Who we share withHosting, AI, payment (Stripe) and analytics providers, professional advisers, and authorities where the law requires it. We do not sell your personal information.Section 12CookiesEssential cookies keep you signed in and the platform working; analytics and marketing technologies are used only where permitted, and you can control them.Section 9Keeping and deletingInformation is kept while your account is active, and deleted on request subject to legal, billing and backup requirements.Section 14Your rightsDepending on where you live: access, correction, deletion, portability, objection and withdrawal of consent. Email support@krion.ai to use them.Section 19Where your data livesWe operate from Ontario, Canada, and our providers may store or process information in other countries, with appropriate safeguards.Section 13Not for childrenKrion is not designed for children under 13, or for any higher minimum age required by your local law.Section 23Contact ussupport@krion.ai for any privacy question, request or complaint.Section 36

This summary is a convenience. The full document below governs.

1. Introduction and Our Commitment to Privacy

Welcome to Krion AI ("Krion," "Krion AI," "we," "us," or "our").

Krion AI provides an artificial intelligence-powered platform that allows individuals, entrepreneurs, developers, businesses, and organizations to create, customize, manage, and deploy applications, websites, and other digital products using natural language instructions and automated development technologies.

Your privacy is important to us. We recognize that users may entrust our platform with personal information, confidential business information, proprietary ideas, application source code, customer records, and other potentially sensitive material.

This Privacy Policy explains how we collect, receive, use, process, store, disclose, retain, and protect information when you access or use Krion AI.

It also describes the choices and rights available to you regarding your personal information.

This Policy is intended to promote transparency, accountability, and responsible data handling across our services.

By using Krion AI, you acknowledge that you have been provided with this Privacy Policy. Where required by applicable law, we will request your consent for specific processing activities.

We encourage you to read this Policy carefully before using our services, particularly if you intend to upload confidential information or build applications that process information belonging to other individuals.

2. Scope of This Privacy Policy

This Privacy Policy applies to personal information processed through:

  • The Krion AI website at https://krion.ai.
  • The Krion AI application-building platform.
  • Registered user accounts and dashboards.
  • AI-powered development and code-generation features.
  • Applications and websites created using Krion, to the extent that Krion processes their data.
  • Hosting, deployment, and project-management services.
  • Subscription and billing interfaces.
  • Customer support and technical assistance.
  • Promotional communications and newsletters.
  • Official Krion AI communications and interactions.
  • Other products or services that expressly reference this Privacy Policy.

This Policy does not automatically govern the independent privacy practices of third-party websites, applications, integrations, or services that may be accessible through Krion.

Applications built by our users may require their own privacy policies and legal disclosures.

Where a customer operates an application built with Krion, that customer may independently determine how information is collected and used through that application.

3. Identity of the Organization and Privacy Accountability

Krion AI is responsible for managing personal information under its control in accordance with applicable privacy laws.

For privacy inquiries, requests, or complaints, contact:

Krion AI — Privacy Team

Email: support@krion.ai

Website: https://krion.ai

Operating Location: Ontario, Canada

Legal operating entity: [Insert registered business or legal entity name before publication.]

Business mailing address: [Insert appropriate business contact address before publication.]

The designated privacy contact is responsible for receiving inquiries about personal information and coordinating responses to privacy-related requests.

We aim to maintain appropriate internal practices governing access to information, service providers, retention, security, and accountability.

4. Categories of Information We Collect

We collect different categories of information depending on how you interact with our platform.

4.1 Personal identification information

When you register for an account, communicate with us, or use our services, we may collect:

  • Full name.
  • Email address.
  • Username or display name.
  • Company or organization name.
  • Business contact information.
  • Profile picture.
  • Account preferences.
  • Country or general region.
  • Other information you voluntarily provide.

We use this information to create and administer accounts, communicate with users, and provide our services.

4.2 Account and authentication information

When you create or access an account, we may process information such as:

  • Internal account identifiers.
  • Login timestamps.
  • Authentication status.
  • Password-related authentication records.
  • Account verification status.
  • Security preferences.
  • Login history.
  • Session identifiers.
  • Authentication provider identifiers.

Where authentication is handled by an external provider, we may receive limited identity information needed to create or link your Krion account.

We do not require users to disclose passwords from unrelated services.

4.3 Subscription and payment information

When you purchase a subscription, upgrade a plan, or purchase eligible services, we may process:

  • Subscription tier.
  • Payment status.
  • Billing frequency.
  • Transaction identifiers.
  • Invoice information.
  • Billing name and address.
  • Applicable taxes.
  • Subscription renewal dates.
  • Credit purchases and usage balances.
  • Refund or dispute history.
  • Limited payment-method details supplied by our payment processor.

Krion uses Stripe for payment processing.

Payment card details entered into Stripe-hosted or Stripe-controlled payment components are processed by Stripe under its own privacy and security practices.

Krion does not intend to directly collect or store complete payment card numbers or card security codes on its application servers.

We may receive limited transaction and payment-method information from Stripe to administer billing, investigate payment issues, and maintain financial records.

4.4 Technical and device information

When you use Krion, certain technical information may be collected automatically, including:

  • IP address.
  • Browser type and version.
  • Device type.
  • Operating system.
  • Device and browser settings.
  • Referring website.
  • Requested URLs.
  • Access dates and times.
  • General location inferred from IP address.
  • Session duration.
  • Error reports.
  • Application performance information.
  • Technical identifiers.
  • Security event records.

This information helps us maintain a secure, reliable, and functional platform.

4.5 Usage and interaction information

We may collect information about how users interact with our services, such as:

  • Features accessed.
  • Dashboard navigation.
  • Projects created or edited.
  • Application generation requests.
  • AI credit consumption.
  • Subscription feature usage.
  • Deployment actions.
  • Error messages.
  • Feature interactions.
  • Support requests.
  • Aggregated platform usage trends.

We use this information for service operation, debugging, capacity planning, security, and product improvement.

We aim to collect information reasonably necessary for these purposes.

5. AI Prompts, Project Information, and Generated Content

Krion's core functionality involves processing information submitted by users to generate or modify software.

This information may include:

  • Natural language prompts.
  • Application descriptions.
  • Business ideas.
  • Website requirements.
  • Source code.
  • User interface instructions.
  • Database structures.
  • Documents.
  • Uploaded images.
  • API specifications.
  • Application configuration information.
  • Project files.
  • Generated outputs.
  • Revision history.
  • Troubleshooting information.

We refer to this collectively as "Project Content."

5.1 Processing project content

Krion processes Project Content to perform the actions requested by users, including generating software, making changes, displaying previews, maintaining projects, and supporting deployment.

Project Content may need to be transmitted to external AI model providers, hosting infrastructure, or other service providers involved in performing the requested functionality.

Only the information reasonably necessary to perform an operation should be transmitted.

5.2 Confidential and proprietary information

We recognize that Project Content may contain valuable intellectual property, confidential business plans, proprietary code, and private information.

Users should avoid submitting unnecessary sensitive personal information, passwords, private keys, payment card details, or confidential information that is not required for their intended task.

Users are responsible for ensuring that they have the necessary rights and permissions to upload and process information through Krion.

5.3 AI model training

Krion does not intend to use private customer projects to train publicly shared AI models without an appropriate legal basis and, where required, user consent.

However, the processing, retention, and model-training practices of external AI providers depend on the providers and contractual arrangements used.

Before publishing this Policy, Krion must verify and accurately disclose whether AI providers retain prompts, use submitted content for model improvement, or offer contractual training restrictions.

Where feasible and supported by the underlying infrastructure, Krion should implement technical and contractual restrictions on unauthorized training uses.

5.4 Generated applications and outputs

AI-generated source code, applications, text, designs, and other outputs may be retained in user workspaces to enable continued editing, version management, and project recovery.

The availability and duration of saved versions, backups, and project histories depend on the platform's technical capabilities and retention practices.

Users should maintain independent backups of important projects and information.

5.5 Human access to project content

Authorized personnel or service providers may require limited access to Project Content for legitimate activities, including:

  • Responding to customer support requests.
  • Investigating technical errors.
  • Diagnosing platform failures.
  • Addressing security incidents.
  • Investigating suspected abuse.
  • Complying with valid legal requirements.

Such access should be restricted to appropriate personnel and governed by confidentiality and security controls.

Krion does not claim that project content is inaccessible to all personnel or infrastructure providers.

6. Information Within Applications Built Using Krion

Users may create applications that collect information from their own customers, employees, visitors, or end users.

Such applications may process:

  • Names and email addresses.
  • Contact forms.
  • Customer records.
  • Appointment information.
  • Transaction records.
  • User accounts.
  • Uploaded documents.
  • Business records.
  • Other application-specific information.

The privacy responsibilities for this information depend on the architecture, hosting configuration, and relationship between Krion and the application owner.

6.1 Responsibilities of application owners

Application owners are responsible for establishing lawful purposes for collecting information through their applications.

They may also be responsible for:

  • Providing their own privacy notices.
  • Obtaining required consent.
  • Defining data retention periods.
  • Responding to end-user privacy requests.
  • Securing application-specific integrations.
  • Complying with applicable industry and privacy regulations.

6.2 Krion's processing role

Where Krion hosts or processes information solely on behalf of an application owner and under that owner's instructions, Krion may act as a service provider or data processor.

In other situations, Krion may independently determine certain processing purposes, such as platform security, account administration, and billing.

The applicable responsibilities may be further described in customer agreements or a Data Processing Agreement.

6.3 Third-party integrations

Applications may connect to external services, databases, APIs, or hosting providers.

Information transmitted to those services is subject to the relevant provider's practices and the configurations selected by the application owner.

Krion is not automatically responsible for independent processing performed by unrelated third-party services.

7. How We Use Personal Information

We process personal information for legitimate and disclosed business purposes, including the following.

7.1 Providing our services

We use information to:

  • Register and authenticate accounts.
  • Create and manage workspaces.
  • Process application-building instructions.
  • Generate and edit software.
  • Save projects.
  • Provide development tools.
  • Enable supported deployment features.
  • Operate subscriptions.
  • Maintain user preferences.

7.2 Improving functionality

We may analyze relevant usage and technical information to:

  • Identify software errors.
  • Improve performance.
  • Understand feature adoption.
  • Optimize platform reliability.
  • Improve user interfaces.
  • Evaluate service capacity.
  • Develop and test new functionality.

Where practical, we may use aggregated or de-identified information for these purposes.

7.3 Communications

We may use contact information to send:

  • Account verification messages.
  • Security alerts.
  • Important service notifications.
  • Subscription confirmations.
  • Payment receipts.
  • Billing reminders.
  • Customer support responses.
  • Material policy updates.
  • Product announcements where permitted.

Marketing communications will be subject to applicable consent and unsubscribe requirements.

7.4 Security and fraud prevention

We may process relevant information to:

  • Detect unauthorized access.
  • Prevent account abuse.
  • Investigate suspicious activity.
  • Protect infrastructure.
  • Enforce platform rules.
  • Address payment fraud.
  • Investigate vulnerabilities.
  • Protect users and third parties.

7.5 Legal and regulatory obligations

We may use or retain information to:

  • Comply with applicable laws.
  • Maintain tax and financial records.
  • Respond to legally valid requests.
  • Investigate disputes.
  • Establish or defend legal claims.
  • Meet regulatory obligations.

We do not use personal information for unrelated purposes without an appropriate legal basis.

9. Cookies and Similar Technologies

Krion may use cookies, local storage, session technologies, and similar tools.

These technologies support website functionality and help us understand how the platform is used.

9.1 Essential technologies

Essential technologies may be used for:

  • Authentication.
  • Session management.
  • Security protection.
  • Load balancing.
  • Application functionality.
  • Saving necessary preferences.
  • Maintaining shopping or checkout sessions.

Certain essential technologies may be required for the service to function.

9.2 Analytics technologies

Where enabled, analytics technologies may help us measure:

  • Website traffic.
  • Visitor interaction.
  • Page performance.
  • Signup completion.
  • Conversion rates.
  • Technical errors.
  • General feature usage.

The actual analytics services used should be disclosed in the relevant cookie notice or provider list.

9.3 Marketing technologies

If Krion uses advertising pixels or similar marketing technologies, these may measure campaign effectiveness, referrals, and advertising interactions.

Nonessential marketing technologies must be deployed in accordance with applicable consent and privacy requirements.

9.4 Managing cookies

Users may manage cookies through their browser settings and any consent-management controls provided by Krion.

Disabling essential cookies may interfere with account authentication or other core functionality.

Where legally required, Krion will offer choices for accepting or rejecting nonessential cookies.

10. Analytics and Platform Performance Monitoring

Krion may use analytics, error monitoring, and performance tools to understand platform stability and improve user experience.

Depending on the tools enabled, collected information may include page views, interaction events, device information, application errors, and session identifiers.

We seek to limit unnecessary collection of directly identifiable information through analytics systems.

Sensitive Project Content should not be intentionally included in ordinary analytics events unless necessary and appropriately protected.

If third-party analytics or monitoring providers are used, their identity and relevant processing practices should be disclosed through an accessible service-provider notice.

11. Artificial Intelligence Providers and Automated Processing

Krion may rely on external AI systems to interpret prompts, generate source code, modify applications, and produce requested outputs.

To deliver these functions, relevant Project Content may be transmitted to AI providers.

11.1 Information shared with AI providers

Depending on the requested operation, transmitted information may include:

  • User instructions.
  • Relevant code files.
  • Application specifications.
  • Project structure.
  • Error descriptions.
  • Requested changes.
  • Supporting context.

We should limit shared information to what is reasonably necessary to perform the requested task.

11.2 AI-generated outputs

AI systems can generate incomplete, inaccurate, insecure, or otherwise unsuitable outputs.

Users should independently evaluate generated applications and code before deploying them in environments involving sensitive information or critical business processes.

11.3 Automated decision-making

Krion uses automated systems to generate and modify software.

If Krion introduces automated decisions that produce legal or similarly significant effects on individuals, it will assess the applicable notice, explanation, review, and objection requirements before deploying those features.

11.4 AI provider transparency

Krion should maintain an accessible list of material AI providers that receive customer content, including relevant information about their processing roles and applicable retention or training restrictions.

12. Disclosure and Sharing of Information

We may disclose information to third parties where necessary to provide our services or where otherwise permitted by law.

12.1 Infrastructure and hosting providers

We may use hosting, database, storage, and infrastructure services to operate the platform.

These providers may process information necessary to store data, run applications, maintain backups, and support availability.

12.2 AI technology providers

AI providers may receive relevant Project Content to fulfill user requests.

12.3 Payment service providers

Stripe and related payment infrastructure may process billing information, payment identifiers, transaction records, and fraud-prevention information.

12.4 Analytics and security providers

Providers offering performance monitoring, analytics, security screening, and error reporting may receive relevant technical information.

12.5 Professional advisers

We may disclose information to legal, accounting, auditing, insurance, or other professional advisers where reasonably necessary and subject to appropriate confidentiality obligations.

12.6 Legal authorities

We may disclose information where legally required or when reasonably necessary to respond to valid legal processes, enforce rights, or address significant security threats.

Where lawful and appropriate, we may challenge overly broad requests or notify affected users.

12.7 Business transactions

Information may be disclosed or transferred in connection with a proposed or completed merger, acquisition, restructuring, financing, or sale of business assets, subject to applicable confidentiality, security, and legal requirements.

12.8 No sale of personal information

Krion does not sell personal information to data brokers in exchange for monetary compensation.

If Krion introduces advertising or other disclosures that qualify as a "sale" or "sharing" under applicable privacy laws, it must update its disclosures and provide required choices before engaging in those activities.

13. International Data Transfers

Krion operates from Canada, but its services and infrastructure may involve providers located in other jurisdictions.

Personal information may be stored, accessed, or processed outside the user's province or country.

Depending on the service providers used, information may be subject to the laws of those jurisdictions, including lawful requests from public authorities.

Where required, Krion will implement appropriate safeguards for international transfers.

Such safeguards may include contractual protections, appropriate service-provider assessments, and legally recognized international transfer mechanisms.

Where applicable, additional arrangements may be required for transfers governed by the GDPR, UK GDPR, or other regional laws.

Krion cannot guarantee that all customer information remains exclusively within Canada unless a specific data-residency commitment has been separately established.

14. Data Storage and Retention

Krion retains personal information only for periods reasonably necessary for the purposes described in this Policy, subject to applicable legal, contractual, operational, and security requirements.

Retention periods may differ depending on the type of information.

14.1 Account information

Account records may be retained while an account remains active and for a limited period afterward where necessary to complete deletion processes, address disputes, or meet legal obligations.

14.2 Project Content

Project files, prompts, and generated code may be retained while projects remain active or while the user maintains an applicable account.

Deletion may be subject to backup cycles, legal holds, technical dependencies, and the retention practices of relevant infrastructure providers.

14.3 Billing records

Invoices, transactions, and tax-related information may be retained for legally required accounting and financial recordkeeping periods.

14.4 Technical logs

Technical and security logs may be retained for appropriate periods based on operational necessity, security requirements, and legal obligations.

14.5 Support correspondence

Support records may be retained for continuity, quality assurance, dispute resolution, and troubleshooting for an appropriate period.

14.6 Backups

Information removed from live systems may remain temporarily in protected backups until those backups expire or are overwritten in accordance with applicable retention procedures.

14.7 Retention review

Krion should periodically review whether retained information remains necessary and securely delete or anonymize information that is no longer required.

Specific retention periods should be documented internally and made available where required by law.

15. Account Deletion and Project Removal

Users may request deletion of their accounts and associated personal information by contacting:

support@krion.ai

Where self-service deletion is available, users may also use the relevant account settings.

15.1 Processing deletion requests

After receiving a valid request, Krion may need to verify the requester's identity and authority before deleting information.

Krion will process eligible deletion requests in accordance with applicable law.

15.2 Information that may remain

Certain records may need to be retained for legal compliance, financial reporting, fraud prevention, dispute resolution, security, or other lawful purposes.

15.3 Published applications

Deleting a Krion account may not automatically remove every copy of a previously published application, particularly where deployment occurs through external services or independent hosting environments.

Users may need to take additional action to disable external integrations, remove published content, or delete separately hosted information.

15.4 Exports and backups

Users are encouraged to export important information using available features before requesting permanent account deletion.

Account or project deletion may result in irreversible loss of access.

16. Data Security and Protection Measures

Krion recognizes the importance of protecting personal information and Project Content from unauthorized access, disclosure, alteration, and destruction.

We seek to maintain safeguards appropriate to the nature and sensitivity of the information processed.

Depending on the relevant system, safeguards may include:

  • Encrypted network connections.
  • Secure authentication processes.
  • Account authorization controls.
  • Restricted administrative access.
  • Protected infrastructure configurations.
  • Access logging.
  • Software security updates.
  • Input validation.
  • Security monitoring.
  • Incident investigation procedures.
  • Appropriate backup protections.
  • Vendor security assessments.

The existence and implementation of specific safeguards depend on the platform's infrastructure and operational practices.

No internet-connected service or storage environment is completely free of risk.

Accordingly, we cannot guarantee absolute security.

Users are responsible for maintaining the confidentiality of their authentication credentials and taking reasonable precautions when handling sensitive information.

17. Security Incidents and Data Breaches

If Krion becomes aware of a security incident affecting personal information, we will assess the nature, scope, and potential consequences of the incident.

Where appropriate, we may take steps to:

  • Investigate the incident.
  • Contain unauthorized activity.
  • Protect affected systems.
  • Determine what information was involved.
  • Assess risks to affected individuals.
  • Restore affected services.
  • Implement corrective measures.
  • Notify affected individuals or regulators where required by law.

Notifications will be provided within applicable legal requirements.

We may also maintain legally required breach records and cooperate with appropriate authorities.

Users who suspect unauthorized account access should contact support@krion.ai promptly.

18. User Responsibilities and Sensitive Information

Krion is a general-purpose software creation platform.

Users may be able to build applications for a broad range of industries and purposes.

However, users should not assume that Krion is automatically certified or configured for regulated activities involving sensitive information.

Examples of potentially sensitive information include:

  • Medical records.
  • Government identification numbers.
  • Financial account credentials.
  • Payment card information.
  • Biometric data.
  • Children's personal information.
  • Confidential employment records.
  • Highly sensitive legal documents.
  • Authentication credentials.
  • Private cryptographic keys.

Before using Krion to process regulated or highly sensitive information, users should determine whether the necessary contractual arrangements, technical controls, compliance measures, and permissions are available.

A general privacy policy alone does not establish compliance with industry-specific regulations.

19. Your Privacy Rights

Depending on applicable law and your location, you may have rights regarding your personal information.

These rights may include:

19.1 Right of access

You may request information about personal information Krion holds or processes about you, subject to applicable limitations.

19.2 Right to correction

You may request correction of inaccurate or incomplete personal information.

19.3 Right to deletion

You may request deletion of eligible personal information where supported by applicable law.

19.4 Right to data portability

Where applicable, you may request certain personal information in a structured and commonly used format.

19.5 Right to withdraw consent

Where processing depends on consent, you may withdraw that consent, subject to lawful restrictions.

19.6 Right to object or restrict processing

Where applicable, you may object to specific processing activities or request restrictions on certain uses of information.

19.7 Marketing choices

You may unsubscribe from promotional emails using the unsubscribe instructions provided in those messages or by contacting us.

19.8 Right to complain

You may contact Krion with concerns about how we handle personal information.

You may also have the right to complain to an applicable privacy regulator.

19.9 Exercising your rights

Submit privacy requests to:

support@krion.ai

We may ask for information reasonably necessary to verify your identity and protect against unauthorized access to personal information.

We will respond within the timeframes required by applicable law.

Some rights may be limited by legal exemptions, contractual obligations, or the rights of other individuals.

20. Canadian Privacy Rights

Krion operates from Ontario, Canada, and is subject to applicable Canadian privacy legislation.

Where applicable, this includes Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).

Our privacy management practices are intended to reflect principles including:

  • Accountability.
  • Identifying purposes.
  • Consent.
  • Limiting collection.
  • Limiting use, disclosure, and retention.
  • Accuracy.
  • Security safeguards.
  • Openness.
  • Individual access.
  • Challenging compliance.

Users in Canada may contact us to ask about the collection, use, disclosure, accuracy, and retention of their personal information.

Subject to applicable legal requirements, users may also raise concerns with the Office of the Privacy Commissioner of Canada or another appropriate privacy authority.

Office of the Privacy Commissioner of Canada

https://www.priv.gc.ca

Additional provincial privacy laws may apply depending on the location, type of information, and nature of the processing.

21. European Economic Area and United Kingdom Privacy Rights

Where the European Union General Data Protection Regulation (GDPR), UK GDPR, or related laws apply, individuals may have additional rights.

These may include:

  • Access to personal information.
  • Correction of inaccurate information.
  • Erasure in applicable circumstances.
  • Restrictions on certain processing.
  • Data portability.
  • Objection to certain processing activities.
  • Withdrawal of consent.
  • Protection in relation to certain automated decisions.
  • The right to lodge a complaint with a supervisory authority.

Krion will assess and respond to these rights where the relevant legislation applies.

Where required, Krion must also provide appropriate information regarding:

  • The responsible legal entity.
  • Processing purposes and legal bases.
  • Applicable legitimate interests.
  • Categories of recipients.
  • International transfer safeguards.
  • Retention periods or criteria.
  • Applicable automated decision-making.
  • Whether providing information is required.
  • Contact information for any required representative or Data Protection Officer.

If Krion is legally required to appoint an EU or UK representative, the relevant contact details will be provided.

Nothing in this Policy is intended to limit rights that cannot lawfully be waived.

22. United States State Privacy Rights

Residents of certain U.S. states may have additional rights under applicable state privacy legislation.

Depending on the law and whether it applies to Krion, these rights may include:

  • Knowing what categories of personal information are collected.
  • Accessing personal information.
  • Requesting correction.
  • Requesting deletion.
  • Obtaining portable copies of eligible information.
  • Opting out of certain targeted advertising or qualifying data disclosures.
  • Limiting certain uses of sensitive personal information.
  • Appealing certain privacy-request decisions.
  • Protection against unlawful discrimination for exercising privacy rights.

Krion does not claim that every U.S. state privacy law applies to its operations.

We will provide any additional notices, controls, or disclosures required where a particular law applies.

Requests may be directed to support@krion.ai.

23. Children's Privacy and Age Restrictions

Krion is not designed or intended for children under the age of 13.

Users must also satisfy any higher minimum age requirements established by applicable law and Krion's Terms of Service.

Where applicable law requires parental or guardian consent for younger users, the relevant requirements must be satisfied before permitted collection or processing takes place.

Krion does not knowingly seek to collect personal information from children in violation of applicable law.

If we become aware of personal information collected from a child without the required authorization, we will take appropriate steps to investigate and delete the information where required.

Parents or guardians who believe a child has provided personal information improperly may contact support@krion.ai.

Users who build applications directed at children are responsible for assessing and complying with the privacy requirements applicable to those applications.

24. Marketing, Newsletters, and Promotional Communications

Krion may communicate with users about products, feature releases, events, offers, tutorials, and service updates.

Marketing emails will be sent in accordance with applicable requirements, including Canada's anti-spam legislation where relevant.

Where consent is required, Krion will obtain appropriate consent before sending commercial electronic messages.

Users may unsubscribe from promotional communications at any time.

Unsubscribing from marketing messages does not necessarily prevent essential transactional communications, such as payment receipts, account verification messages, or important security notices.

We may retain limited suppression records to respect unsubscribe requests and prevent unwanted marketing.

Krion does not authorize the use of customer personal information for undisclosed third-party marketing purposes.

25. Third-Party Websites, Applications, and Services

Krion may contain links to external websites or integrations operated by third parties.

These may include:

  • Payment providers.
  • External hosting platforms.
  • AI technology providers.
  • Authentication services.
  • Software repositories.
  • Domain registrars.
  • Analytics providers.
  • Communication services.
  • Customer support tools.
  • Other developer integrations.

These services may have independent privacy policies and terms.

Krion does not control every aspect of how unrelated third parties collect or use information.

Users are encouraged to review the privacy documentation of services they choose to connect to their projects.

Where third parties process information on Krion's behalf, Krion will assess the applicable contractual and privacy responsibilities.

26. Business Accounts and Organization Workspaces

Krion may offer account features designed for companies, teams, agencies, or organizations.

Where available, administrators may be able to:

  • Invite team members.
  • Assign workspace permissions.
  • Manage subscription access.
  • Review organization-owned projects.
  • Control application deployments.
  • Manage billing.
  • Remove members.
  • Access certain workspace activity information.

Users participating in an organization-managed workspace should understand that authorized organization administrators may have access to information associated with that workspace.

Krion may process relevant account and workspace information to provide organization-level services.

Organizations using Krion are responsible for communicating applicable internal privacy policies and access rules to their members.

The precise access available to administrators depends on the features actually implemented.

27. Application Ownership, Confidentiality, and Data Control

Krion recognizes that application projects may involve valuable intellectual property and confidential information.

Our handling of personal information does not, by itself, determine the legal ownership of user-generated applications, source code, or other intellectual property.

Ownership and licensing rights are governed by the applicable Terms of Service and customer agreements.

Krion does not treat the submission of Project Content as permission to publicly display confidential user projects for advertising or testimonials.

We will seek appropriate permission before publishing customer-identifiable work, screenshots, business information, or testimonials for promotional purposes.

Users are responsible for ensuring that the information uploaded to Krion does not infringe third-party rights or violate applicable confidentiality obligations.

28. Public Projects and Information Sharing Choices

Certain Krion features may allow users to publish websites, applications, portfolio examples, or other content.

When users intentionally publish projects, information included in those projects may become accessible to the public.

Public information may be:

  • Viewed by other users.
  • Shared through external links.
  • Indexed by search engines.
  • Copied or retained by third parties.
  • Archived by external services.

Removing a public project from Krion may not immediately remove information previously indexed, downloaded, or independently retained elsewhere.

Users should review project visibility and access settings before publishing.

Krion should clearly distinguish private workspace content from publicly published applications.

29. Automated Monitoring, Fraud Prevention, and Platform Integrity

Krion may use automated security mechanisms to help identify suspicious activity, service abuse, or technical threats.

Examples may include:

  • Unusual login activity.
  • Excessive or abnormal resource usage.
  • Repeated authentication failures.
  • Payment fraud indicators.
  • Automated spam activity.
  • Attempts to exploit platform vulnerabilities.
  • Suspicious API requests.

These mechanisms may process relevant technical, account, and activity information.

Where appropriate, suspicious activity may be reviewed before enforcement action is taken.

Krion should avoid collecting unnecessary personal information and should ensure that security-related processing is proportionate to the risks addressed.

30. Data Accuracy and Quality

Krion aims to maintain personal information that is reasonably accurate and complete for its intended purposes.

Users may be able to update certain account information directly through their dashboard.

For corrections that cannot be completed through account settings, users may contact support@krion.ai.

We may ask for reasonable verification before implementing changes.

Krion is not responsible for independently verifying the accuracy of all information voluntarily entered into user-created applications.

31. Data Minimization and Privacy by Design

Krion seeks to incorporate privacy considerations into product development and platform operation.

Relevant practices may include:

  • Limiting unnecessary collection.
  • Restricting access to sensitive information.
  • Using aggregated information where feasible.
  • Minimizing unnecessary transfers to third parties.
  • Evaluating new product features for privacy risks.
  • Separating development and production environments where appropriate.
  • Reviewing permissions.
  • Limiting disclosure of private project information.

We may update these practices as the platform and its security program evolve.

32. Data Processing Agreements and Business Customers

Certain business customers may require a Data Processing Agreement (DPA) or additional contractual provisions.

Where relevant and available, a DPA may address:

  • Data processing instructions.
  • Processing purposes.
  • Types of personal information.
  • Confidentiality obligations.
  • Subprocessors.
  • Security responsibilities.
  • International transfers.
  • Assistance with individual rights requests.
  • Security incidents.
  • Return or deletion of information.
  • Applicable audit or compliance arrangements.

Customers with specific contractual or regulatory requirements may contact support@krion.ai to inquire about available agreements.

This Privacy Policy does not itself establish that a particular DPA, certification, or regulated-industry processing arrangement is available.

33. Government and Law Enforcement Requests

Krion may receive legally valid requests for information from courts, regulatory bodies, law enforcement agencies, or other public authorities.

We assess requests in accordance with applicable law.

Where legally permitted and appropriate, we may:

  • Review the legal validity of requests.
  • Limit disclosures to information properly required.
  • Challenge requests that are legally defective or overly broad.
  • Notify affected users when permitted.
  • Maintain appropriate records of disclosures.

We do not voluntarily provide unrestricted access to customer information merely because a party requests it.

34. Privacy Complaints and Dispute Resolution

We encourage users to contact Krion if they have questions or concerns about privacy.

Privacy complaints may involve:

  • Unauthorized disclosure.
  • Incorrect personal information.
  • Unresolved deletion requests.
  • Unwanted marketing.
  • Concerns about third-party processing.
  • Inadequate explanations about data use.
  • Suspected privacy incidents.

We will review complaints and provide responses consistent with applicable law.

Where a concern cannot be resolved directly, individuals may have the right to contact an appropriate privacy regulator.

35. Changes to This Privacy Policy

Krion may update this Privacy Policy as our services, technologies, business operations, or legal obligations change.

Changes may be made to reflect:

  • New platform features.
  • New infrastructure providers.
  • Changes to AI processing.
  • New subscription capabilities.
  • Security improvements.
  • Changes in data-handling practices.
  • Updated legal requirements.
  • New privacy controls.

When changes are published, we will update the date at the beginning of the Policy.

Where legally required, we will provide additional notice or obtain consent before materially changing how personal information is processed.

Continuing to use the platform does not replace consent where applicable law requires express permission.

36. Contact Information

For questions, requests, complaints, or concerns relating to this Privacy Policy or Krion's handling of personal information, please contact:

Krion AI

Privacy and Data Protection Inquiries

Email: support@krion.ai

Website: https://krion.ai

Location: Ontario, Canada

Please include sufficient detail to help us understand your request.

For security reasons, do not send passwords, full payment card details, or unnecessary sensitive information through ordinary email.

We will review legitimate privacy requests and respond as required by applicable law.

37. Privacy Policy Summary

At Krion AI, our privacy commitments are centered on responsible and transparent information handling.

We seek to:

  1. Collect information for legitimate and disclosed purposes.
  2. Explain how personal information and AI project content are processed.
  3. Use appropriate safeguards to protect information.
  4. Restrict unnecessary disclosure.
  5. Respect applicable privacy rights.
  6. Provide reasonable mechanisms for users to request access, correction, or deletion.
  7. Maintain accountability for service providers processing information on our behalf.
  8. Explain relevant international processing and transfer risks.
  9. Provide transparency about subscriptions, account information, and data retention.
  10. Review and improve privacy practices as the platform evolves.

Our goal is to help people build applications with artificial intelligence while respecting the privacy of individuals and organizations that rely on our services.

Krion AI — Describe it. Build it. Launch it.

Last Updated: October 23, 2026