Honest about what we do and what we don't

ACC360 Phase 1B adds application-level user-scoped filtering so users normally see their own records in the app. All new records are stamped with the authenticated user's identity, and all reads filter by that identity.

Important limitation: Full backend row-level security depends on platform-level enforcement. While ACC360 filters records at the application level using user identity fields, this is not the same as enforced database-level RLS. Users with direct API access could theoretically access unscoped records. This remains a production hardening item.

Dashboard numbers depend on the accuracy of user-entered records. ACC360 cannot verify records are accurate.

Value and depreciation planning features are for personal and operational organization only. They are not tax, accounting, insurance, or legal calculations.

Beautiful dashboards that update as your records change are based solely on data you enter into ACC360.

Controlled testing lets ACC360 validate real workflows — how families track appliances, how churches manage equipment, how contractors log repairs — before opening to the general public.

Controlled testers provide feedback on usability, dashboard clarity, report usefulness, and pricing interest. This feedback shapes the final product before broad public release.

A small, careful first launch also limits the exposure window while backend RLS, billing, and admin role escalations are pending with the Base44 platform team.

ACC360 is now structured for first controlled tester execution. The first tester group should use limited, non-sensitive records or sample data while platform-level RLS, secure admin role confirmation, billing setup, orphan migration, and accessibility testing are completed.

What testers should avoid uploading during early testing:

• →Passwords or login credentials
• →Bank account numbers or financial account details
• →Tax IDs or Social Security numbers
• →Medical records or health information
• →Student records or educational documents
• →Private legal documents
• →Highly sensitive receipts or confidential business documents
• →Anything you are not comfortable sharing in a new digital tool

For initial testing, use sample data or general household and equipment records. Receipts, warranties, appliance manuals, and basic photos are fine.

ACC360 demo and sales pages — including the Demo Walkthrough page (/demo) and Sales One-Pager (/sales) — are designed to explain the product clearly during controlled tester and demo launch. Example dashboards, walkthroughs, and report examples shown on these pages are educational previews using illustrative numbers. They should not be mistaken for real customer data, verified financials, or guaranteed outcomes.

No real customer names, testimonials, logos, or verified savings claims appear in ACC360 demo or sales materials. Numbers shown in examples (such as "47 assets" or "$1,240 monthly expenses") are illustrative only.

ACC360 is being prepared for controlled tester launch. Controlled testing validates usability, dashboard value, reporting workflows, pricing feedback, and real-life organization scenarios with a small, carefully selected group of testers.

Broad public launch requires additional backend/database RLS review, billing integration, secure admin roles, and final production hardening. These items are documented in the Backend Hardening Plan, Billing Readiness Plan, and Admin Role Plan inside the app.

ACC360 will not claim broad public launch readiness until all hardening acceptance criteria are met and verified.

ACC360 may be mentioned to a congregation or group as a controlled beta interest opportunity for up to 200 people. This is not broad public launch. Active testing should expand in waves, and testers should use sample or non-sensitive records while security, billing, admin, orphan migration, and accessibility items remain under review.

A church mention does not equal church endorsement unless church leadership explicitly approves that later.

ACC360 has preparation tools for controlled tester launch, platform escalation, billing-mode selection, and manual accessibility testing. These tools create planning records and document decisions.

Preparation records do not mean broad public launch readiness. ACC360 remains in controlled tester launch until platform responses, tester evidence, accessibility testing, and billing decisions are complete.

ACC360 can send weekly summary emails when enabled. Weekly reports may include due date, expense, handoff, and asset summary information. The default detail mode is Summary Only, which shows counts rather than record details.

Weekly reports are disabled by default during controlled beta. Users must actively enable them in Settings. Users can disable weekly reports at any time.