Different events stay separate
Privacy notices, acknowledgement, acceptance and genuinely optional consent are not merged into a single checkbox.
Privacy by design
Privacy is not a checkbox.
It is part of the product.
TailLane is designed to keep privacy notices, acknowledgement and optional consents separate. Access controls follow roles and workspace boundaries; features covered by privacy gates remain inactive when required evidence, configuration or documents are missing.
This page describes product design choices. It is not a legal notice and does not replace the documents applicable to each facility and processing activity.
Product decisions
Understandable controls, not generic statements.
The beta makes the approach visible. Every capability is described according to its actual status, without turning privacy into an absolute promise.
Access by role and scope
Application controls follow roles and workspace boundaries, limiting access to the authorised scope without promising invulnerable security.
Fail-closed sensitive workflows
Features covered by privacy gates remain inactive when required configuration, evidence or documents are missing.
Relevant changes are reviewed
Every relevant change to controls opens a traceable review; only changes that affect the notice provided to individuals require a new notice.
Reviewable governance
Retention, suppliers and risk have dedicated tools.
TailLane provides structured, versioned tools for retention criteria, supplier roles, recipients, transfers, legal holds, controls and residual risk. They must be configured and approved for each facility’s real use case.
- Retention criteria configurable by phases and events, without invented periods.
- Suppliers and recipients classifiable by activity and role.
- Decisions and reasons kept as historical evidence.
- Guided imports and operational exports support portability and reduce lock-in.
Transparency
What it means — and what it does not.
TailLane provides verifiable tools and gates. It does not replace a facility’s privacy notice, create blanket consent for every processing activity or claim that every future configuration is automatically compliant.
TailLane is in public beta. Capabilities that are not yet operational remain labelled as in development or inactive and are not presented as already available.
Frequently asked questions
Privacy in kennel software, without the legal fog.
Clear answers about the design principles visible in the current beta.
Are acknowledgement and consent the same thing?
No. Acknowledgement records that a specific notice version was made available. Consent applies only to a genuinely optional and separate choice.
Does TailLane automatically enable sensitive features?
No. Features covered by privacy gates remain inactive when the necessary configuration, evidence or documents are missing.
Does every change require a new privacy notice?
Every relevant change to controls opens a review. A new notice version is required only when the change affects what must be communicated to data subjects.
Does the facility keep control of its data?
TailLane includes guided import, human review of uncertain records and readable export. Applicable documents still define the operational roles, responsibilities and conditions.
See the product decisions in a real interface.