Every record has a boundary.

Crecy keeps the operating record whole while deliberately narrowing what residents, owners, staff and support can reach. The boundary follows the relationship—not the navigation menu.

This page describes controls present in the product architecture. It does not represent an independent certification or guarantee.

Property record

Maple Court

Organization
Maple Property Group
Accounting book
Toronto · CAD
Units
24
Access rule
Relationship + scope

Operator

Sees the permitted operational record for the active organization and property scope.

Resident

Receives only the tenancy-facing projection for their own active relationship.

Owner

Receives the ownership-facing projection for invited interests and finalized records.

Server command

Re-checks role, organization, property and object before the action runs.

Database policy

Limits the rows the caller can reach even after application-level authorization.

Representative Crecy control model. The three product surfaces intentionally receive different projections of the same property relationship.

One property does not mean one view.

The operator works from the property record. A resident receives the tenancy-facing projection. An owner receives the ownership-facing projection. Each relationship is intentionally smaller than the operating system behind it.

Record familyOperatorResidentOwner
Portfolio operationsFull organization contextOutside scopeOutside scope
Lease / tenancyOperational recordOwn active tenancyOutside scope
Resident identityPermitted operational fieldsOwn accountOutside scope
Owner reportingStatement + remittance workspaceOutside scopeOwn property interest
Property documentsAccess by role and propertyDelivered recipient versionsDelivered owner versions

A correction leaves a trail.

Posted journal entries are append-only. A correction reverses and replaces the original instead of silently rewriting history. Transactions remain inside one accounting book and currency, and retried commands return their original result instead of posting twice.

Maple Court · Operating book

September ledger activity

Currency

CAD

DateEntryAmountState
Sep 01Resident rent+CA$1,850.00Posted
Sep 04Repair expense−CA$420.00Posted
Sep 05Repair reversal+CA$420.00Reversal
Sep 05Corrected repair−CA$395.00Posted

The original repair posting still exists.

Correction is represented by a reversal and replacement rather than a quiet overwrite.

Demonstration net activity

CA$1,455.00

Representative demonstration data; not a customer financial record.

A document is unavailable until it earns release.

Files live in private storage. A lease, notice or statement must pass the quarantine and scan lifecycle before an access-checked, short-lived link can expose an exact version to an authorized recipient.

Versions supersede instead of overwrite, preserving the artifact a resident or owner actually received and acknowledged.

Document record

Owner statement · September 2026

Version
v3
Storage
Private
  1. 09:14:02Upload receivedQuarantinedUnavailable to recipients
  2. 09:14:03File identity verifiedVerifiedExpected hash recorded
  3. 09:14:11Malware scan completedCleanProvider result recorded
  4. 09:14:12Version releasedEligibleExact version may be delivered
  5. 09:16:27Owner delivery createdDeliveredAccess-checked short-lived link
Representative custody record. Versions supersede rather than overwrite prior released artifacts.

Money and support take narrower paths.

Crecy records payment truth without holding resident rent, and support receives no standing path into customer data. Both flows are deliberately constrained before they begin.

Payer

Resident

Confirms merchant, amount, currency, method and fee.

Payment handling

Connected provider

Handles card or bank credentials and returns provider references.

Settlement destination

Operator account

Crecy records verified payment state; it does not hold resident rent.

Provider webhooks are signature-verified and handled idempotently.

Support session SUP-042

Investigate document-delivery mismatch

Mode

Read-only

Scope
Maple Court · document delivery
Expires
14:30 local time
Audit evidence
Session + each support read
Opening a support session does not bypass tenant row policies and does not grant a write path into customer records.
Representative support-access record.

Built controls are not the same as external assurance.

Crecy explains what the architecture does and states plainly what has not been independently assured. Crecy holds no SOC 2 or equivalent certification.

There is no published uptime percentage or penetration-test claim without a defined evidence period, signed scope and remediation record. WCAG 2.2 AA remains the accessibility target, not an external conformance claim.

TopicCurrent evidencePublic posture
Tenant isolationRow policies, scoped commands and negative testsBuilt control
Financial integrityAppend-only postings, reversals and idempotencyBuilt control
Document handlingPrivate storage, quarantine and scan lifecycleBuilt control
SOC 2No independent report currently heldNot claimed
Published uptimeNo declared monitoring period yetNot claimed
Penetration testNo signed report and remediation record yetNot claimed

Review the controls. Ask about the evidence. Expect precise answers.

North American availability is being prepared alongside payment, privacy, support and localization gates.