Privacy Policy

janitor-ai.ca is a content website built to publish informational pages about Janitor AI topics. It does not provide JanitorAI account login, account storage, or subscription management.

The site should be understood as an editorial destination. That means privacy expectations differ from a logged-in product or community platform because the current site experience is primarily page delivery and outbound navigation.

Like most websites, your browser and hosting environment may automatically process technical information such as IP address, device type, browser type, request path, referring page, approximate region, time of access, and basic performance signals as part of ordinary server delivery, caching, and security logging.

This type of data is typically processed to serve the requested page, maintain infrastructure stability, detect abuse, and review site health. It should not be described as optional if it is necessary for the website to load and function normally.

If analytics are installed now or in the future, this policy should name the tool, explain the categories of data involved, and describe whether cookies, cookieless measurement, or aggregate reporting are used. A mature privacy policy should not hide measurement tools behind vague phrases such as standard website optimisation.

If no analytics are currently installed, the policy should remain conservative and avoid claiming detailed behavioural tracking that the site does not actually perform.

This site should only claim the cookie technologies it genuinely uses. On a lightweight editorial website, cookies may be limited to essential hosting behaviour, security protections, and any measurement stack that has actually been implemented.

If consent-dependent technologies are added later, the site owner should review whether a cookie banner, preference tool, or jurisdiction-specific consent notice is required in the relevant regions.

If the site later adds a contact form, email intake, newsletter signup, or similar feature, any information a visitor chooses to submit may include identifiers such as name, email address, message content, and device metadata associated with the submission. That information should only be collected where the route is real, monitored, and supported by a matching privacy explanation.

Do not send passwords, banking information, identity numbers, or private account credentials through any contact route published on this site unless a secure, stated process exists for that purpose.

This site links to JanitorAI and related first-party resources for login, app access, pricing, and help routes. Those destinations operate under their own privacy policies, cookies, and account terms.

Once you leave janitor-ai.ca and visit a third-party website, the privacy practices on that destination are controlled by the third party rather than by this domain.

A production-ready site should keep technical logs, contact submissions, and analytics records only for as long as they serve a legitimate operational, security, legal, or editorial purpose. Retention periods should be reviewed alongside hosting configuration and any tools added over time.

If no submission features exist, the primary retention questions usually relate to server logs and any installed analytics platform rather than to user accounts.

Depending on the hosting provider, CDN, analytics vendor, or email service used, technical data may be processed or stored outside the visitor's home jurisdiction. That is common on modern web infrastructure and should be disclosed in a calm, factual way rather than hidden behind broad legal language.

If the site owner later adds vendors that process personal data, this policy should be updated to reflect the relevant transfer context and safeguards where required.

Visitors may have legal rights relating to access, correction, deletion, objection, or complaint depending on the laws that apply to them and the way the website is operated. The practical scope of those rights depends on what information the site actually collects.

If the site owner publishes a real contact route for privacy requests, this section should be updated to explain how those requests can be made and what information may be needed to verify them.

Privacy language should evolve when the site changes. If this website adds a contact form, analytics, advertising, newsletters, embedded media, affiliate tracking, or any other data-collecting feature, this policy should be updated before or at the same time that feature goes live.

The best privacy policies are operational documents, not decorative footers. They should track the real behaviour of the site as it exists today.