What information is collected?
Preparing the governed record.
Bookwiser is loading the requested public or applicant surface without changing its authority state.
Preparing the governed record.
Bookwiser is loading the requested public or applicant surface without changing its authority state.

This notice explains how personal information is handled across website requests, beta accounts, organization profiles, support, services, fictional demonstrations, provider handoffs, and controlled product learning.
These questions connect the public notice to real work, real responsibilities, and a clear next step instead of leaving it as abstract policy language.
What information is collected?
Why is it needed?
Who may receive it?
How can a person request access, correction, export, or deletion?
The register explains what Bookwiser manages, what requires another person or provider, and which decisions remain outside this process.
Used for authentication, account operation, and controlled access.
Application answers remain separate from general analytics.
Controlled records are scoped by tenant, purpose, recipient, capability, and expiry.
Private reviewer notes and sensitive answers are excluded from general product metrics.
Privacy and data-rights correspondence is routed through emilia@bookwiser.ca with identity verification before disclosure.
This is the expected path through Bookwiser. Actual service, account, provider, privacy, and legal obligations continue to follow the agreements and policies accepted for that relationship.
The collection route identifies the product, service, security, support, communication, or legal purpose.
Consent, contract, customer instruction, legal requirement, or another reviewed basis is recorded where applicable.
Role, organization, field, recipient, provider, purpose, expiry, and retention rules constrain use.
Access, correction, export, withdrawal, objection, or deletion requests are verified and routed for human review.
These are Bookwiser's public commitments. Signed agreements, qualified professional opinions, and customer-specific deployment reviews add the terms required for each actual relationship.
Marketing, beta, service intake, banking data, customer proof, case studies, and provider access remain separate purposes.
Bookwiser does not position customer or applicant data as an advertising product.
Data categories, residency, sub-processors, support access, retention, deletion, export, and model-training terms require review.
Identity and authority are verified before a controlled record is exported, corrected, or deleted.
For your protection, do not send passwords, credentials, tax identifiers, unredacted legal files, private customer records, or complete banking documents through a public contact path.