Privacy Notice
How AbodeStack handles account, builder, homeowner, property, and private-document information during its product preview.
Scope and preview status
This notice describes the AbodeStack public website, product demonstration, and authenticated homeownership platform. The service is currently a product preview. Demo records are fictional and must not contain real customer information.
Before AbodeStack accepts production customer data, this notice, the Terms of Service, contractual commitments, and operational procedures must receive legal and security review.
Information the platform processes
Depending on the features used, AbodeStack may process account names and email addresses; builder organization roles; property addresses and characteristics; ownership periods; equipment, warranty, maintenance, and service records; private documents, receipts, and property images; support and privacy requests; and security and audit events.
AbodeStack is not intended to collect Social Security numbers, payment-card or bank credentials, government identification, medical records, alarm or access codes, or other information unrelated to maintaining a digital home record.
How information is used
Information is used to authenticate users, maintain tenant and property permissions, organize the digital home record, support builder-to-homeowner handoff and ownership transfer, provide requested maintenance and document features, protect the service, respond to privacy requests, and meet legal obligations.
AbodeStack does not use private home records for advertising and does not sell personal information. Product analytics and future integrations must use the minimum information necessary for their stated purpose.
Documents, photographs, and AI features
Private files are stored in non-public object storage and are delivered only after server-side authorization. Uploads are restricted by size and detected file type. Production uploads must remain disabled until malware scanning and quarantine controls are configured and verified.
Private documents are not sent to an AI provider by default. Any future AI processing of private content must include a clear in-product notice, purpose limitation, data minimization, appropriate provider terms, and user action or consent where required.
Sharing and service providers
Information may be shared with authorized builder personnel, current homeowners, or successor homeowners according to server-enforced roles, property assignments, document visibility, and transfer rules. Former-owner private service records remain separated from successor access unless a limited transfer summary was deliberately shared.
Cloud infrastructure and other vetted service providers may process information only to operate and secure the service. Provider access must be contractually limited and reviewed before production use.
Retention and deletion
AbodeStack keeps information only for an identified product, security, contractual, or legal purpose. Retention periods must be assigned before production onboarding. Deletion requests may require review where records affect another authorized party, ownership history, fraud prevention, legal claims, or required audit evidence.
Deletion workflows must remove applicable database records and private objects and account for recovery copies according to the documented retention schedule.
Security
AbodeStack uses encrypted Cloudflare D1 and R2 storage, HTTPS, private object bindings, role- and property-scoped authorization, restricted secrets, and audit records. No system can guarantee absolute security. Administrators must use multifactor authentication before production data is admitted.
Your choices and requests
Authenticated users can use the Privacy Center to download a machine-readable summary of personal data and submit correction or deletion requests. Identity verification may be required before a request is completed. Questions can be submitted through the public contact page.
Changes to this notice
The notice is versioned. Material changes will be presented in the product before they apply to authenticated use. An acknowledgement records that a notice was presented; it is not treated as consent for optional processing.
Contact
Use the contact page for privacy questions. Authenticated users can submit access, correction, and deletion requests through the in-app Privacy Center.