Privacy Policy

Last updated: October 31, 2026

At Intent, we believe that privacy and transparency are important. This Privacy Policy explains how Intent collects, uses, stores, processes, and shares information when you access or use our websites, applications, infrastructure, and services.

This policy applies to the Intent ecosystem, including Intent FreeDomain, Intent-DNS, Intent-Mail, Intent Web Hosting, their associated dashboards, APIs, and related websites and infrastructure.

1. Scope and About Intent

Intent is a nonprofit technology initiative that develops and operates internet infrastructure and developer-focused services. This policy applies to information processed through services operated under the Intent name and domains.

For the purposes of this policy, "Intent", "we", "us", and "our" refer to the operators responsible for the relevant Intent service. "You" refers to a visitor, account holder, customer, or other person using our services.

This policy applies to information collected directly from you, automatically through your use of our services, or received from third-party services when you authorize an integration.

2. Information We Collect

The information we collect depends on which Intent services you use and how you interact with them. We do not necessarily collect every category listed below from every user.

2.1 Account and Registration Information

• Username, account name, and display name.
• Email address and email verification status.
• Password hashes and authentication-related information.
• Account creation date, account status, and account preferences.
• Information submitted through registration, support, or account forms.
• Authentication sessions, session expiry, and account activity records.

2.2 Domain and DNS Information

• Registered domain and subdomain names.
• DNS records, nameservers, record values, and domain configuration.
• Domain ownership and verification information.
• DNS API tokens and related authentication metadata.
• Domain registration, modification, renewal, and deletion records.

2.3 Email Information

• Email addresses and mailbox account information.
• Email messages, message headers, and attachments processed by the service.
• Sender and recipient addresses, timestamps, and delivery status.
• Mailbox settings, folders, and storage usage.
• Authentication and connection information relating to webmail, IMAP, and SMTP.

2.4 Web Hosting Information

• Website files, uploaded content, and deployment artifacts.
• Site names, project settings, build commands, and deployment configuration.
• Connected repository URLs, repository names, branches, and commit information.
• Custom domains, domain verification tokens, and SSL certificate status.
• Build output, deployment logs, error messages, and deployment history.
• Webhook and integration metadata used to trigger deployments.

2.5 Payment and Transaction Information

Where paid features, IFP Keys, or other payment-related services are offered, we may process transaction references, payment status, product information, amounts, timestamps, and related account information.

Payment card or banking details may be processed by the relevant payment provider. We do not claim to store complete payment card or banking credentials unless a particular payment flow explicitly requires it.

2.6 Support and Communication Information

• Messages sent to our support or administrative email addresses.
• Information submitted through contact forms and abuse reports.
• Discord communications when you contact us through our community.
• Information necessary to investigate and resolve reported issues.

3. Intent FreeDomain

Intent FreeDomain provides domain and subdomain registration services. When you register or manage a domain, we may process the information required to create and maintain your account and domain registration.

This may include:

• Account details and verified email address.
• Domain names and registration dates.
• DNS records, nameservers, and domain configuration.
• Registration, modification, and deletion history.
• IP addresses and other security information associated with account activity.
• Abuse reports, administrative actions, and support correspondence.

We use this information to operate domain registrations, manage DNS, prevent abuse, maintain service integrity, and respond to legitimate administrative or legal requests.

4. Intent-DNS

Intent-DNS provides authoritative DNS hosting and related management functionality, including DNS records, domain configuration, and API access.

When you use Intent-DNS, we may process:

• DNS zones and the domains associated with your account.
• DNS records, including A, AAAA, ALIAS, CNAME, MX, TXT, SRV, NS, and CAA records.
• Nameserver and zone configuration information.
• API credentials, token metadata, and authentication records.
• Account and plan information.
• Operational, diagnostic, and security logs.
• DNS request metadata where collected by the relevant DNS infrastructure.

DNS records are necessary for the operation of the service. Depending on your configuration, record values may contain information about your infrastructure, mail providers, verification services, or third-party platforms.

API tokens should be treated as confidential credentials. You are responsible for protecting your tokens and revoking them if you believe they have been exposed or accessed without authorization.

5. Intent-Mail

Intent-Mail provides email and mailbox functionality. Operating an email service necessarily involves processing email-related information so messages can be received, stored, displayed, sent, and delivered.

This may include:

• Mailbox addresses and account information.
• Email content, message headers, and attachments.
• Sender and recipient addresses.
• Message timestamps, delivery information, and status.
• Mailbox folders, settings, and storage information.
• Authentication information and connection metadata.
• Spam, abuse, and service-security information.

Email content may be processed by systems involved in message delivery, storage, spam prevention, abuse investigation, and technical support. Access to message content by authorized personnel may occur where necessary for service operation, security, support, or compliance with applicable legal obligations.

We do not promise that email communications are end-to-end encrypted. Standard email delivery may involve other mail servers and providers outside Intent's control. Users should avoid sending highly sensitive information through ordinary email unless they have applied appropriate additional protection.

If you connect a custom domain to Intent-Mail, we may process domain configuration and related MX, SPF, DKIM, and DMARC information to support email setup and verification.

6. Intent Web Hosting

Intent Web Hosting provides website hosting and deployment functionality. When available, the service may allow users to connect source-code repositories, deploy websites, configure custom domains, and manage deployments through a dashboard.

To provide these features, we may process:

• Hosting account information and authentication records.
• Website files, uploaded files, and deployment artifacts.
• Repository names, repository URLs, branches, and commit metadata.
• GitHub account identifiers and usernames when GitHub integration is used.
• Authorization tokens required for the GitHub integration.
• Site settings, build commands, and deployment configuration.
• Build logs, deployment logs, error messages, and status information.
• Custom domains, DNS verification information, and SSL status.
• Webhook events and related deployment-trigger information.
• Visitor and server request logs where collected by hosting infrastructure.

6.1 GitHub Integration

If you connect a GitHub account, you authorize the relevant integration to communicate with GitHub according to the permissions displayed during authorization.

Depending on the permissions granted and features used, the integration may process your GitHub username, account identifier, repository information, and authorization credentials required to access repositories or configure deployment webhooks.

Authorization credentials are intended to be protected using the security mechanisms implemented by the service. You can revoke the integration through GitHub's application settings. Revoking access may prevent deployments or repository-related features from working.

GitHub is an independent third-party service. Its processing of your information is governed by GitHub's own privacy policy and terms.

6.2 Website Files and Public Content

Files and content you deploy may become publicly accessible through your hosting address or custom domain. You are responsible for ensuring that you have the necessary rights to upload and publish that content.

Do not upload passwords, private keys, API secrets, personal information belonging to others, or other confidential material into public website files or build output. Build logs and deployment output may expose information if your build scripts print secrets or private values.

6.3 Website Visitor Information

When a website hosted through Intent receives requests, the hosting infrastructure may process technical request information such as IP addresses, requested paths, timestamps, response status, and user-agent information, depending on the logging configuration.

Website owners are responsible for their own websites, including providing any privacy notices required for information they collect directly from their visitors.

7. Technical and Security Information

When you visit or use Intent services, our systems and infrastructure may automatically process certain technical information, including:

• IP addresses and approximate network information.
• Browser type, device type, operating system, and user-agent strings.
• Request timestamps, requested URLs, and response status codes.
• Authentication attempts and session information.
• Rate-limit, error, diagnostic, and application logs.
• Account actions and administrative audit records.
• Information used to identify suspicious activity or service abuse.

We may use this information to protect accounts, investigate suspicious activity, enforce usage limits, diagnose technical problems, and maintain the reliability of our infrastructure.

8. How We Use Information

We may use collected information for the following purposes:

• Creating, maintaining, and managing user accounts.
• Providing domain registration, DNS, email, and hosting functionality.
• Authenticating users and maintaining account sessions.
• Processing deployments, DNS changes, and email delivery.
• Providing technical support and responding to inquiries.
• Preventing spam, fraud, abuse, unauthorized access, and security incidents.
• Investigating violations of our Terms of Service and acceptable-use rules.
• Maintaining service availability, performance, and reliability.
• Processing payments and managing paid features where applicable.
• Meeting applicable legal obligations and responding to lawful requests.
• Communicating important service, security, or policy changes.

9. Cookies and Similar Technologies

Intent websites and dashboards may use cookies, local storage, or similar technologies where necessary for functionality.

These technologies may be used to:

• Maintain authentication sessions.
• Remember account or interface preferences.
• Protect forms and authentication flows.
• Support security and abuse-prevention mechanisms.

Some third-party integrations may use their own cookies or similar technologies. Their use is governed by the relevant third party's policies.

Disabling cookies may affect login, dashboards, or other service functionality.

10. Data Sharing and Disclosure

Intent does not sell personal information as a business model. We may share or disclose information in limited circumstances where reasonably necessary to operate our services or protect users and infrastructure.

10.1 Service Providers

Information may be processed by infrastructure providers, hosting providers, email delivery providers, payment providers, security services, and other vendors that help operate Intent.

10.2 Security and Abuse Investigations

We may share relevant information when investigating spam, phishing, malware, fraud, unauthorized access, copyright complaints, abuse, or other activity that threatens our users or infrastructure.

10.3 Legal Requirements

We may disclose information where we reasonably believe disclosure is required by applicable law, a valid court order, legal process, or a lawful request from an authorized public authority.

10.4 Protection of Rights and Infrastructure

We may disclose relevant information when reasonably necessary to protect the rights, property, safety, security, and legitimate interests of Intent, our users, or other persons.

10.5 Public Information

Information you intentionally publish through a public website, DNS record, or other public-facing feature may be accessible to third parties. You should not place private information in publicly accessible fields.

11. Third-Party Services

Intent services may integrate with or rely on independent third-party providers. Examples may include:

• GitHub for repository authorization and deployment integrations.
• Infrastructure and hosting providers for servers and network services.
• Payment providers for transactions and paid features.
• Email delivery providers for account verification and service notifications.
• Security and anti-abuse providers for protection against automated abuse.
• External DNS, domain, and certificate-related infrastructure.

These providers may process information under their own privacy policies and contractual arrangements. Intent does not control the independent privacy practices of third-party services.

We encourage users to review the privacy policies of third-party services before connecting accounts or using their features.

12. Public Domain Information and WHOIS

Intent may provide public domain lookup or WHOIS-related functionality for domains managed through our services.

To reduce unnecessary exposure of registrant information, public Intent-managed WHOIS pages are intended to display administrative contact information rather than expose users' private account details. For example, public contact information may identify the domain as Managed by Intent and display admin@int.yt.

This public display approach does not mean that all registration information is deleted from our internal systems. We may retain registration and account information privately where needed to operate the service, prevent abuse, resolve disputes, or comply with applicable obligations.

DNS records and other domain information that you publish may remain publicly accessible through DNS lookups and other internet services. Public WHOIS presentation does not make DNS record contents private.

13. Data Security

We take reasonable technical and organizational measures intended to protect information against unauthorized access, disclosure, alteration, loss, and misuse.

Depending on the service and system, these measures may include:

• Password hashing and authentication controls.
• Session management and revocation mechanisms.
• Access restrictions for administrative systems.
• API authentication and credential protection.
• Rate limiting and abuse-prevention controls.
• Monitoring, diagnostic logs, and security investigations.
• Transport security where supported by the relevant service.

No internet-connected service, storage system, or transmission method can be guaranteed to be completely secure. We cannot promise absolute security, and users should protect their passwords, API tokens, authorization credentials, and private files.

If you believe your account or information has been compromised, contact us as soon as possible.

14. Data Retention

We retain information for as long as reasonably necessary for the purposes described in this policy, including service operation, account management, security, abuse prevention, dispute resolution, and legal compliance.

Retention periods may vary by information category:

• Account information: may be retained while an account remains active and for a reasonable period afterwards.
• Domain and DNS information: may be retained while domains or DNS services are active and as needed for administrative or abuse-related purposes.
• Email data: may be retained while a mailbox or message remains stored, subject to service functionality and deletion processes.
• Hosting files and deployments: may be retained while a site or deployment remains active and according to applicable cleanup procedures.
• Security and audit logs: may be retained for a period necessary to investigate incidents and protect the services.
• Payment records: may be retained as required for transaction administration, accounting, and legal obligations.

We do not promise a single fixed retention period for every type of information. Actual retention depends on the service, the nature of the data, technical requirements, and applicable obligations.

15. Account and Data Deletion

You may request account closure or deletion of information associated with your account by contacting us through the support channels listed below.

Before processing a request, we may need to verify that you control the relevant account or email address.

Deleting an account may affect access to associated domains, DNS zones, mailboxes, websites, deployments, API credentials, and other service resources. Users should export or transfer any information they need before requesting account closure.

Some information may remain in backups, security records, abuse investigations, transaction records, or other systems for a limited period or where retention is necessary for legitimate operational or legal purposes.

Deletion from active systems does not necessarily mean that every backup copy is immediately and permanently erased.

16. Your Privacy Rights

Depending on your location and applicable law, you may have rights concerning personal information we process about you. These may include:

• Requesting access to certain personal information.
• Requesting correction of inaccurate information.
• Requesting deletion of information where applicable.
• Objecting to or requesting restrictions on certain processing.
• Withdrawing consent where processing is based on consent.
• Raising a complaint with an appropriate data protection authority.

To exercise a privacy right, contact us at support@int.yt. We may request reasonable verification before acting on a request. Some requests may be limited where information must be retained for security, legal, or operational reasons.

17. International Data Processing

Intent and its infrastructure providers may operate systems or process information in more than one country. As a result, information may be transferred to or processed in locations outside your country of residence.

Where required by applicable law, we will take appropriate steps intended to support lawful international data transfers.

18. Children's Privacy

Our services are not designed to knowingly collect personal information from children in violation of applicable law.

If you believe that a child has provided personal information to Intent in circumstances where such collection is not permitted, please contact us so that we can review the matter and take appropriate action.

19. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes to our services, infrastructure, data practices, or applicable legal requirements.

When we make changes, we will update the "Last updated" date at the beginning of this page. Where appropriate, we may also provide additional notice through our websites, dashboards, or other communication channels.

Your continued use of Intent services after an updated policy becomes effective is subject to the revised policy, to the extent permitted by applicable law.

20. Contact Us

If you have questions about this Privacy Policy, want to request access to or deletion of information, or wish to report a privacy concern, please contact us.

• General support: support@int.yt
• Administrative contact: admin@int.yt
• Abuse reports: abuse@int.yt
• Website: https://int.yt/
• Community: Intent Discord

Please do not send passwords, API tokens, private keys, or other authentication credentials in ordinary support messages.