Privacy and data handling
Privacy notice
This draft notice describes the operational privacy model for Knight Connect. Owner and legal approval are required before production publication.
Information the service handles
Knight Connect may process account identity and authentication records, organizational membership and leadership data, unit-created content, support requests, security and audit events, and billing records needed to provide the service.
Payment-card and bank-account details are collected and stored by Stripe through its hosted payment surfaces. Knight Connect receives provider identifiers, status, invoice, amount, and reconciliation information, but is not designed to receive the full payment credential.
Why information is used
- Authenticate invited users and apply role- and unit-specific permissions.
- Deliver features selected by an organization and measure governed quota usage.
- Process, reconcile, support, and audit subscription and one-time purchases.
- Protect the service, investigate failures, and meet applicable recordkeeping obligations.
Sharing and service providers
Information is shared only as needed to operate authorized workflows, with the relevant organization, configured service providers, or when legally required. Provider access and retention terms remain subject to owner and legal review.
Retention and requests
Operational, security, support, and financial records may have different retention requirements. Retention periods, request rights, and the responsible legal entity remain subject to owner and legal review.
Use the published support path. Signed-in members should avoid placing passwords, payment credentials, or unnecessary sensitive member information in a support request.