Organization boundaries
Membership checks and row-level policies separate organization records. Privileged server workflows repeat authorization checks.
Trust you can ask questions about
Sensitive rental work needs clear boundaries. Understand who is sharing information, who can act on it and which evidence supports the next step.
For independent landlords and property teams.
Access and evidence · illustrative preview
A verification invitation does not grant access to another applicant’s evidence or authorize a signature or payment. This illustration is a workflow explanation, not a live security assessment.
Fictional data. Explore the homepage demo to try the connected workflow.
Keep the work moving with clear ownership, recorded progress and an explicit next action.
Present the purpose, requested information and relevant privacy details before the applicant chooses whether to continue.
Organization membership, staff roles and action-specific access checks govern the workspace and applicant requests.
Keep consent, review decisions, documents and relevant financial events in their recorded context. Review sensitive actions through the existing authorization controls.
Use the privacy workflow for access, correction, consent withdrawal and deletion requests, subject to applicable retention and legal-hold review.
What’s connected
Membership checks and row-level policies separate organization records. Privileged server workflows repeat authorization checks.
Verification, signing and payment actions keep their own required checks. A link for one action does not grant the other capabilities.
Provider tokens stay on the server and are encrypted for storage. Applicant-facing pages do not receive stored bank-provider credentials.
Consent records, review activity and relevant administrative and financial events support later inspection. Sensitive actions can require elevated authentication.
PIPEDA and applicable provincial privacy requirements need to be assessed for the organization and its activities. Consent is one obligation alongside purpose, safeguards and accountability.
Supported document and deposit-policy workflows use jurisdiction context. Confirm the current rule, available form and tenancy type before relying on a result.
Fit the way you work
Start with essential information. Add shared ownership and review controls as your portfolio needs them.
Explain the information request, follow the applicant’s choice and keep the decision with its supporting evidence.
Review staff roles, retention settings, provider arrangements and data-processing terms as part of your own security and privacy due diligence.
Understand the workflow before bringing your own records.
Talk through your setupNo certification or universal compliance guarantee is claimed here. Applicable federal/provincial requirements, configuration, provider contracts and your organization’s responsibilities need their own review.
No. Confirm hosting regions, subprocessors, provider transfers and contractual requirements for your implementation. Do not infer residency from Canadian branding.
The privacy policy, data processing addendum and trust disclosure are linked below. Contact us to discuss your organization’s due-diligence requirements.
Official guidance explains the applicable requirements. These links are reference material, not endorsements or certifications of Northstar.
Try the fictional landlord-to-applicant journey on the homepage.