Technicull Solutions Technology that works the way it should
Services Portfolio Security Contact EN/FR

Privacy

Privacy policy

How Technicull Solutions handles personal information across our website, consulting work, applications, automations, and production integrations.

Effective July 25, 2026 · Last updated July 25, 2026

On this page Scope Our role Information we handle How we use information Apps and integrations Service providers and transfers Security and incidents Retention Your choices and rights Contact

1. Scope

This policy applies when Technicull Solutions (“Technicull,” “we,” “us”) collects or handles personal information through technicull.ca, business communications, consulting and support engagements, custom software, DevOps work, automation, and system-integration services.

A client agreement, statement of work, or data processing terms may add more specific requirements. If those terms conflict with this policy, the applicable contract governs the engagement.

Our privacy program is intended to support applicable Canadian private-sector privacy requirements, including PIPEDA and substantially similar provincial legislation where they apply. A client may have additional duties based on its sector, location, or the sensitivity of its data.

2. Our role

For our own website, sales, billing, and business administration, Technicull determines why and how personal information is handled.

When we operate an app, synchronize data, or access systems on a client’s instructions, the client generally remains responsible for the source data and permitted purposes. Technicull acts as a service provider and uses that data only to deliver, secure, support, and improve the contracted service, or as required by law.

3. Information we handle

Depending on the interaction, this may include:

  • Contact and account details: name, organization, role, email address, phone number, and communication history.
  • Project and support information: requirements, tickets, approvals, documentation, and information supplied while troubleshooting.
  • Integration data: system names, configuration, record identifiers, field mappings, synchronization status, error details, audit events, and client-directed content that passes through an integration.
  • Technical information: IP address, browser or device details, timestamps, security events, and server logs produced by hosting and application infrastructure.
  • Commercial records: proposals, contracts, invoices, payment status, and business contact information. We do not ask clients to send payment-card details through project forms or email.

We aim to collect only information reasonably needed for a stated business or service purpose. Do not send passwords, private keys, API tokens, or production datasets through public website forms.

4. How we use information

  • respond to inquiries and manage client relationships;
  • design, configure, test, deploy, monitor, support, and document technology services;
  • authenticate authorized users and protect systems from misuse;
  • investigate errors, maintain audit records, and improve reliability;
  • meet contractual, accounting, insurance, and legal obligations; and
  • obtain and record production authorization and privacy-related instructions.

Technicull does not sell personal information or use client production data for advertising.

5. Applications, DevOps, and integrations

Services such as the CanFASD Sync app and other client integrations may connect two or more business systems. Depending on the client-approved configuration, they may read, transform, transmit, or update records and create operational logs.

Before production access, we work with the client to define authorized systems, data categories, environments, access scope, testing, retention, monitoring, incident contacts, and rollback expectations. Our production integration signoff provides a practical record of these decisions.

Credentials and other secrets should be exchanged only through an approved secure channel and, where feasible, stored in access-controlled secret management systems rather than source code, ordinary email, or public forms.

6. Service providers and data location

We may use hosting, cloud infrastructure, source control, monitoring, email, collaboration, and professional-service providers where needed to deliver or administer our services. We limit access to the relevant purpose and expect providers to protect the information they handle.

Client-chosen systems and some service providers may process information outside the individual’s province or Canada. Information processed in another jurisdiction may be accessible under that jurisdiction’s laws. Project-specific residency or subprocessor requirements should be documented before production approval.

We may also disclose information where authorized by the client, required by law, necessary to protect legal rights or system security, or connected with a business transaction subject to appropriate confidentiality protections.

7. Safeguards and privacy incidents

We use administrative, technical, and physical safeguards proportionate to the sensitivity and context of the information. These may include least-privilege access, multi-factor authentication, encryption in transit, secure secret handling, logging, backups, patching, and documented deployment or recovery procedures.

No system is completely secure. If we identify a suspected incident involving client-controlled information, we will take reasonable steps to contain and investigate it, notify the appropriate client contact without unreasonable delay, and support legally required assessment, records, and notifications. The organization that controls the affected personal information remains responsible for its regulatory decisions unless a contract or applicable law provides otherwise.

8. Retention and disposal

We keep personal information only as long as reasonably needed for the identified purpose, contractual commitments, security, dispute resolution, and legal or accounting obligations. Retention for client systems, logs, backups, and exported data may be set in the project agreement or production signoff.

When information is no longer required, we take reasonable steps to delete, anonymize, or securely dispose of it. Residual copies may remain in protected backups until their normal rotation.

9. Consent, access, and correction

Subject to applicable law and contractual limits, individuals may ask about the personal information Technicull controls, request access or correction, or withdraw consent for future optional uses. We may need to verify identity before completing a request.

If the information is controlled by one of our clients, the request should normally be directed to that organization. We will reasonably assist the client in responding where required.

This website does not currently use advertising cookies. Our hosting provider may generate essential network and security logs when a visitor requests a page.

We remember your language choice in this browser using local storage. This preference is not used for advertising.

10. Questions or concerns

Contact Technicull Solutions at solutions@technicull.ca. Please use the subject “Privacy request” and do not include unnecessary sensitive information in the initial message.

We may update this policy as services or legal requirements change. The effective date above identifies the current version.

This policy explains Technicull Solutions’ practices and is not legal advice to clients. Project-specific legal, regulatory, health, public-sector, or data-residency requirements should be reviewed by the client’s qualified advisor.
Technicull SolutionsWeb design and IT consulting

Website development, brand identity packages, and IT services for businesses and organizations.

Explore

Services Portfolio Security Contact

Get in touch

solutions@technicull.ca

Have a project in mind? Send us a few details.

© Technicull Solutions Privacy policyProduction signoff Designed and maintained by Technicull Solutions
Hosted on Cloudflare Pages