Security & privacy
Kartios is designed to give useful information to the people responsible for carrying the work—without making every detail visible to everyone.
Review Kartios With UsProtection in practice
Ministry records remain scoped to the workspace that owns them.
Server code checks permissions and resource ownership for reads and writes.
Useful context follows workspace roles and entrusted ministry relationships.
Hosted files use private storage and authorized server access.
Browser sessions are not given ordinary direct access to application tables.
Visibility with responsibility
Choose a responsibility to see the useful context and the boundary that remains in place.
This is a practical explanation, not an exhaustive permission matrix. Exact access depends on active workspace membership, assigned role, and entrusted relationships.
People and accounts
Showing The identity model.
External sources connect through a controlled source link to one church-specific workspace person and membership. That membership connects to a stable person identity across Kartios. Account access remains optional and separate, and every other workspace owns its own directory record.
External source
Recurring sources can keep a durable source link. A one-time import does not create one.
Recognizes which external record belongs to which workspace person.
Owns this church’s name, birthday, contacts, and field authority.
Carries role and participation in this church. Login access remains separate.
The durable human anchor across Kartios.
Credentials and verified login email remain separately controlled.
Receives its own directory record, contacts, role, and source links.
Contacts are not credentialsA shared household email remains useful without becoming a login.
Recognition is not controlA source link does not automatically grant authority over fields.
Workspaces stay separateOne church’s directory changes do not rewrite another’s.
This is a practical explanation of the identity safeguards, not an exhaustive account-repair or permission workflow.
Clear about the boundaries
Kartios describes current protections plainly and invites ministries to review their requirements rather than assuming one posture fits every organization.
Questions worth reviewing
The author retains access. Other visibility follows the selected audience: the wider church or ministry, pastors, a small group, or a discipleship relationship.
No. Administrative status alone does not reveal prayer shared only with pastors. Current pastoral prayer visibility is limited to owners and pastors.
Ordinary platform-support views hide prayer titles, bodies, authors, and pastoral details. This describes application views, not a claim that privileged infrastructure operators are technically incapable of database access.
Review Kartios with us
Walk through the roles, relationships, sensitive information, and visibility boundaries that matter to your church or ministry.
Book a WalkthroughExplore Kartios for Ministry LeadersSecurity & privacy
Prayer, care, discipleship relationships, and leadership context can be deeply personal. Kartios is designed to give useful information to the people responsible for carrying the work—without making every detail visible to everyone.
Visibility with responsibility
Access can follow both a workspace role and a specific ministry relationship, such as mentoring someone or leading a group.
Showing Member.
This is a practical explanation, not an exhaustive permission matrix. Exact access depends on active workspace membership, assigned role, and the relationships entrusted to the person.
Protection in practice
Sensitive by nature
People and accounts
Kartios preserves the distinction between knowing someone in ministry and giving them account access. That separation supports managed people, controlled invitations, and retained history without treating every profile as a login.
Showing The identity model.
External sources connect through a controlled source link to one church-specific workspace person and membership. That membership connects to a stable person identity across Kartios. Account access remains optional and separate, and every other workspace owns its own directory record.
External source
Recurring sources can keep a durable source link. A one-time import does not create one.
Recognizes which external record belongs to which workspace person.
Owns this church’s name, birthday, contacts, and field authority.
Carries role and participation in this church. Login access remains separate.
The durable human anchor across Kartios.
Credentials and verified login email remain separately controlled.
Receives its own directory record, contacts, role, and source links.
Contacts are not credentialsA shared household email remains useful without becoming a login.
Recognition is not controlA source link does not automatically grant authority over fields.
Workspaces stay separateOne church’s directory changes do not rewrite another’s.
This is a practical explanation of the identity safeguards, not an exhaustive account-repair or permission workflow.
Clear about the boundaries
Kartios describes current protections plainly and invites ministries to review requirements with us rather than assuming one posture fits every organization.
Security and privacy questions
The author retains access to their request. Other visibility follows the audiences selected for it: the wider church or ministry, pastors, a small group, or a discipleship relationship.
No. Mentor and group-leader visibility follows the relationships and groups they are responsible for leading rather than opening unrestricted workspace access.
No. Administrative status alone does not reveal prayer shared only with pastors. Current pastoral prayer visibility is limited to owners and pastors.
Normal access begins with a verified identity and active workspace membership. Server reads and writes apply workspace and resource checks, with database constraints and restricted browser table access providing additional protection.
Yes. A ministry can represent a person and coordinate work around them without creating account access. Login identity is linked separately through a controlled account process.
An inactive membership no longer establishes normal workspace access or counts toward pricing. Kartios retains ministry history rather than silently deleting it, and that history remains subject to authorization.
Hosted uploads use private storage. Object paths are workspace-prefixed, and the application checks authorization before serving or deleting supported uploads.
Ordinary platform-support views hide prayer titles, bodies, authors, and pastoral details. Separately authorized support tools show operational counts and account state. This describes application views, not a claim that privileged infrastructure operators are technically incapable of database access.
Kartios does not currently claim SOC 2 certification, HIPAA compliance, or another independent certification or audit that has not been completed.
Yes. A walkthrough can focus on your ministry roles, sensitive information, visibility expectations, and any requirements Kartios should be evaluated against.
Review Kartios with us
Walk through the roles, relationships, sensitive information, and visibility boundaries that matter to your church or ministry.
