Information Handling Statement

What Gets Recorded During Your Interactions

Different touchpoints create different information trails. Here's what emerges:

When You Contact Us

Your name materializes first—seems obvious, but that's where it starts. Email addresses follow because conversations need routes. If you call, the number gets noted. Messages you send arrive complete with timestamps. Sometimes people mention their companies, roles, specific automation challenges they're facing. All of that enters our system because it's directly part of the conversation you initiated.

Technical Apparatus Details

Your browser announces itself through standard identification protocols—not because we demand it, but because that's how web infrastructure functions. IP addresses reveal rough geographic zones. Device characteristics show up: screen dimensions, operating system profiles, browser versions. These emerge automatically from the connection itself, long before you type anything.

Service-Related Specifics

Once you're working with our automation tools, operational data accumulates. Which features get activated. Configuration choices you make. Integration points with your existing systems. Error logs when something breaks. Usage frequency patterns. This information exists because the service generates it—it's the exhaust from actual operations, not something we collect separately.

The Functional Requirements Behind Retention

Data persists because throwing everything away immediately would make continuing service impossible.

Operational Necessity

Your account needs identifying markers—otherwise, how would you log back in? Configuration settings stick around because rebuilding them each visit would be absurd. Communication histories let us reference previous conversations instead of starting from zero every time. Payment records exist because financial documentation isn't optional. These aren't philosophical choices; they're requirements for continuous service delivery.

Contractual Execution

When agreements get signed—whether that's accepting terms during registration or executing formal service contracts—certain information becomes part of fulfilling those obligations. Invoicing requires billing details. Delivering contracted automation services requires access credentials to systems we're integrating with. Support commitments mean keeping ticket histories. The contract itself creates retention requirements.

Legal Compliance Context

Canadian regulations compel retention of specific records for defined periods. Tax documentation, transaction logs, certain communications—these fall under mandatory preservation rules. We're not keeping them because we want to; we're keeping them because the alternative involves regulatory violations.

Security and Fraud Prevention

Authentication logs help identify unauthorized access attempts. Transaction patterns can flag suspicious activity. These protections benefit you as much as us—maybe more, since your account is what's being protected. But they require maintaining certain behavioral records.

Notice the absence of "marketing insights" or "business intelligence" in that list. Those aren't the drivers here. We're focused on making the service work and meeting obligations—not building behavioral profiles for their own sake.

When Information Moves Outside Our Direct Control

Sometimes details leave our immediate environment. Here's where they go and why:

Infrastructure Providers

Our servers live in facilities we don't physically operate. Cloud hosting providers therefore access whatever data resides on those machines—though contractual terms restrict what they can do with it. Email delivery services handle message transmission. Database services store structured information. These relationships exist because building our own data centers would be economically ridiculous, but they do mean your information touches systems outside our direct management.

Payment Processing

We don't handle credit card details directly—that would require compliance infrastructure we don't maintain. When you pay, financial particulars flow to payment processors who specialize in secure transaction handling. We receive confirmation of successful charges, but the card numbers themselves never reach our systems.

Integration Partners

Business automation often means connecting your existing tools—CRM platforms, accounting software, communication systems. Those integrations require sharing relevant data with the services you're linking. If you're syncing contact records to your email platform, those contacts have to actually reach that platform. We facilitate the transfer based on your configuration choices, but the data movement happens because you've directed it.

Legal Compulsion

Court orders, regulatory demands, or valid legal process can compel disclosure. If law enforcement presents proper documentation requesting specific records, we'll comply—but only to the extent the documentation requires. We don't volunteer information beyond what's legally demanded.

How Long Things Persist

Retention periods vary based on what category of information we're discussing.

Account data sticks around as long as your account exists—deleting your profile triggers removal of associated details, though backups might preserve copies for 90 days before complete elimination. Communication records typically remain for three years unless you request earlier deletion. Financial documents follow Canadian tax law requirements: seven years from transaction date. Service usage logs get purged after two years unless they're tied to ongoing disputes or investigations.

The timeline isn't arbitrary—it reflects legal minimums, operational needs, and standard business practices. Could we delete things faster? Sometimes. Would that create problems? Often yes.

If you close your account, active deletion begins immediately, though complete removal from all systems including backups takes about three months. Financial records remain longer due to regulatory requirements, but they get isolated from operational systems.

Your Control Options

You're not powerless once information enters our systems. Several mechanisms exist for managing your details:

Access and Review

You can request copies of what we hold about you. We'll compile a readable export—usually within two weeks of your request. There's no charge unless you're making repeated requests in short succession, which might trigger administrative fees.

Correction Rights

Spot something wrong? Tell us. We'll update inaccurate details or complete incomplete records. This applies to factual information—opinions or subjective assessments aren't subject to correction, but basic data errors are.

Deletion Requests

You can ask us to erase your information. We'll comply unless legal obligations prevent it—like those seven-year financial record retention requirements. Active service relationships also complicate deletion; you can't simultaneously demand we maintain your account and forget you exist. But once you close your account, deletion proceeds as described earlier.

Processing Restrictions

In certain circumstances, you can limit how we work with your data. Maybe you're disputing accuracy and want processing paused until that's resolved. Maybe you need the information preserved for legal reasons but don't want it actively used. These scenarios have specific procedures—contact us with details about what you're trying to accomplish.

Portability

For data you've provided directly, you can receive structured exports suitable for transfer elsewhere. This covers things like account information, uploaded content, and configuration settings—not automatically generated logs or derived analytics.

Actually exercising these rights means contacting us through the channels listed at the bottom of this document. Be specific about what you want—vague requests take longer to process.