HoldOS private beta terms

1. Private beta status

The private beta is an early-access version of HoldOS. Features may change, appear in stages, experience interruptions, or remain unavailable while they are tested and improved. HoldOS may temporarily pause an affected function when necessary to protect customer data, correct a production issue, or prevent an unverified external action.

Participation in the waitlist does not guarantee admission, a particular feature, or a release date. An invitation provides access only to the beta capabilities enabled for that account.

2. Website previews and feature availability

Public pages may use sample records and interactive demonstrations to explain the intended HoldOS experience. They do not represent a live customer account and should not be understood as a promise that every depicted control, workflow, integration, or result is active in the current beta.

• Available now means a feature is enabled for applicable beta accounts, although permissions, configuration, or provider setup may still be required.
• Private beta means a feature is being tested and may have limits or change.
• Illustrative workflow means the example communicates an intended experience; parts of it may be unavailable or delivered differently.
• In development means the feature is not ready for operational reliance.

Material limitations should be disclosed where the feature is presented or before the user relies on it. A general beta label does not turn a false statement or a fake success message into an accurate one.

3. Payments, mailing, and outside services

Payment processors, banks, email providers, postal vendors, AI providers, and other outside services have their own onboarding, availability, verification, pricing, processing times, and terms. A HoldOS workflow is usable only when the applicable provider connection is configured and the current screen identifies the function as available.

A visible test-mode payment or mail workflow is a simulation. It is not a completed payment, settlement, mailing, delivery, certificate, or provider acceptance unless HoldOS displays a verified provider result. Reaching a browser success page alone does not prove that money settled or mail entered the postal system.

Pending card or bank activity may remain pending until the provider confirms its final status. Mailing costs, postage, processing fees, message charges, and other third-party costs may be separate from a HoldOS subscription and should be shown before a user authorizes the action.

4. Pricing and billing

HoldOS subscriptions are priced by managed-unit allowance. Joining the waitlist or viewing a price does not create a subscription or authorize a charge.

The founding beta offer is limited to the first five companies that complete a paid subscription. It provides 50% off the applicable portfolio subscription price for the first three monthly billing periods, after which the regular monthly price resumes automatically. Stripe Checkout will display the exact amount before confirmation. HoldOS may separately grant complimentary, time-limited access to selected testing workspaces without counting that access as a paid founding subscription.

Payment processing, postage, physical mailing services, SMS, and other usage-based third-party services are separate from the HoldOS subscription when used. Prices and allowances may change for future subscriptions; changes do not silently rewrite an already completed billing period.

5. AI-assisted information and actions

HoldOS may use automated or AI-assisted tools to understand requests, organize records, prepare drafts, or explain available information. These tools can make mistakes. An answer is limited by the records available to the authorized account and should not be treated as a substitute for reviewing the source record.

HoldOS should require review and confirmation before consequential financial, legal, mailing, or account actions. It must not invent a payment, balance, lease term, mailing result, or provider success. When the available information is incomplete or conflicting, HoldOS may ask for clarification or show a warning instead of proceeding.

6. Your responsibilities

• Keep account access private and give each person their own account.
• Use appropriate roles and promptly remove access that is no longer authorized.
• Enter or upload only records you are authorized to manage.
• Verify residents, properties, amounts, dates, recipients, and source documents before consequential actions.
• Review financial, legal, mailing, and AI-assisted output before relying on it.
• Maintain independent copies of critical source records during the beta.
• Report suspected unauthorized access, incorrect workspace data, or provider-status errors promptly.

7. Data, access, and resident visibility

Management workspaces and resident accounts are intended to be separated by server-side permissions. Residents should see only information explicitly made resident-visible for their tenancy. Beta users must not attempt to access another company’s, resident’s, or user’s information.

HoldOS aims to preserve production beta data, but beta software may experience outages or defects. Users should retain original leases, payment records, notices, mailing proof, and other critical business records outside HoldOS while the service remains in beta.

8. No legal, accounting, or emergency service

HoldOS organizes property operations; it does not provide legal advice, tax advice, or accounting advice, guarantee legal compliance, determine that a fee or notice is legally valid, or replace emergency services. Configured fees, notices, deadlines, and document explanations require the user’s independent review.

For fire, suspected gas leaks, immediate danger, active flooding, or another emergency, contact the appropriate emergency service or configured property emergency contact rather than relying on HoldOS.

9. Availability and changes

The beta may be updated frequently. A feature may be changed, replaced, limited, or removed when necessary for security, reliability, provider compatibility, or product development. HoldOS does not promise uninterrupted or error-free beta access.

When practical, HoldOS will identify material changes that affect paid access, important records, or a user’s ability to complete a workflow. A later production service may look or operate differently from the private beta.

10. Feedback, suspension, and ending access

Beta users may provide feedback, report defects, and suggest improvements. HoldOS may limit or suspend abusive, unsafe, unlawful, unauthorized, or security-threatening use. A beta user may stop participating at any time, subject to any record-export or account-close process then available.

Additional commercial terms, including final subscription terms and any provider-specific terms, will be presented before paid public service begins.

Questions or problems

If a screen appears to promise a feature that is not actually available, a provider result is unclear, or an account displays information that may not belong to it, stop using that workflow and contact HoldOS support. Do not submit passwords, full payment credentials, Social Security numbers, or API keys in a support message.