Skip to main content
Security posture

Security claims, scoped to what we can support.

This page is a plain-language starting point for due diligence. It does not imply third-party audit, card-network, privacy-law, Fair Housing, legal-document, or outcome certification. The current product boundary is published in the Trust Center.
Aptoria
Security posture
Operational controls
Payment credentials
Workflow records
Human review
Workspace-scoped data controls
Autonomy limits and approvals
Security claims, scoped to what we can support.
Security posture
Setup-dependent
1. Workspace-scoped operational controls
2. Payment credentials stay in the configured provider flow
3. Reviewable workflow records
4. Human review for consequential matters
5. Workspace-scoped data controls
Aptoria is designed to scope operational data to the customer workspace and to keep sensitive financial data in approved provider flows.
6. Autonomy limits and approvals
You can set the limits Aptoria will work within today. Routing actions to you for approval comes with its planned drafting and autonomous features.
Published capability boundary
Workspace-scoped data controls
Setup-dependent
Autonomy limits and approvals
Setup-dependent
Workspace-scoped operational controls
1. Workspace-scoped operational controls
Aptoria is designed to scope supported operational records to a customer workspace. Access, roles, and activity should be reviewed in the configured workflow; this statement is not a certification or an absolute access guarantee.
Current publication rule
A capability is not described as available merely because a demo, catalog entry, or internal route exists. Provider, jurisdiction, account, delivery, and human-review conditions must be present for the supported workflow.
Human oversight

Humans stay in control.
Agents stay in bounds.

Who can approve what, when the agent can act, and how exceptions escalate.
Review who can approve what
Approval queues
24
↑ 33%
Items waiting for human review
Autonomous actions
247
↑ 23%
Completed within policy
Permission groups
5
Roles across 12 properties
Escalations
3
↓ 50%
Require your attention
You are viewing as Property Manager
You can approve maintenance up to $1,500. Under $500 the agent acts within policy.
Switch role
Permission roles
What each role can see, approve, and manage.
Approval matrix
Who can approve what, before the agent acts.
Request
Owner
Regional Manager
You
Property Manager
Leasing
Accounting
Maintenance over $500
Maintenance over $1,500
Lease renewal exceptions
Vendor onboarding
Late fee waivers
Payment reversals
New property contracts
Under $500 the agent acts within policy. Above it a person decides, within their role’s limit.
Exception routing
Out-of-bounds items move up one role at a time.
1
Aptoria agent
Acts under $500 within policy; flags anything over, non-standard, or in conflict
2
Property Manager
Maintenance above $500, up to $1,500 · routed with a recommendation
3
Regional Manager
Above the Property Manager’s $1,500 limit
4
Owner
High-value or sensitive requests
Each hand-off is logged to the audit trail.
Property Manager
Approval limits for this role.
Maintenance
Up to $1,500
Late-fee waivers
Up to $75
Vendor onboarding
Not in approval path
Lease exceptions
Can approve
Payment reversals
Not in approval path
Recent approvals
Role required, who decided, and when.
Request
Property
Role required
Decided by
When
Status
Grounds service · $1,180
Oakwood Residences · Grounds
Property Manager
Marcus Webb, Property Manager
Mar 28, 9:37 AM
Approved
Lock re-key · $85
Elm Ave Triplex · Unit B
None · within policy
Aptoria agent · within policy
Jun 6, 2:52 PM
Autonomous
Sample portfolio · fictional data

Current publication rule

A capability is not described as available merely because a demo, catalog entry, or internal route exists. Provider, jurisdiction, account, delivery, and human-review conditions must be present for the supported workflow.
Workspace-scoped operational controls
Aptoria is designed to scope supported operational records to a customer workspace. Access, roles, and activity should be reviewed in the configured workflow; this statement is not a certification or an absolute access guarantee.
Payment credentials stay in the configured provider flow
Where online payments are enabled, payment availability and credentials depend on the configured provider. Aptoria does not present itself as a bank, payment custodian, or universal payments processor.
Reviewable workflow records
Supported workflows are designed to retain reviewable actions and approvals. A record does not by itself prove delivery, settlement, legal validity, completeness, or a particular outcome.
Human review for consequential matters
Aptoria does not make housing decisions or represent automated outputs as legal advice. Sensitive communications, applicant actions, document effect, and exceptions require the accountable human owner.
Published capability boundary
Workspace-scoped data controls
Aptoria is designed to scope operational data to the customer workspace and to keep sensitive financial data in approved provider flows.
Platform control for supported Aptoria workflows.
Published capability boundary
Autonomy limits and approvals
You can set the limits Aptoria will work within today. Routing actions to you for approval comes with its planned drafting and autonomous features.
Setting limits is available after account setup; changing them requires two-factor sign-in.