Effective date: To be confirmed · Service operator: To be confirmed before launch
1. Acceptance and service scope
These draft terms describe the proposed conditions for using Accrod, a lease-record and portfolio-workflow service. The final terms must identify the contracting entity, supported regions, eligible users, service limits and the features actually supplied.
2. Accounts and workspace access
Users should provide accurate account details, protect sign-in credentials and only invite people who are authorized to access the workspace. The production terms must specify account recovery, team administration, suspension and security reporting procedures.
3. Customer data and permissions
Customers retain the rights they have in the data and documents they upload, subject to the permissions required to operate the service. The final terms must define the limited service-use license, permitted content, ownership, export, retention and deletion processes. Do not imply that Accrod becomes the owner of customer leases.
4. Acceptable use
Describe prohibited use, unlawful uploads, access abuse, interference with other workspaces and any operational restrictions. Keep this language consistent with the actual security controls and enforcement ability.
5. Plans, billing and cancellation
Before paid plans are launched, specify plan inclusions and limits, price and currency, billing frequency, tax treatment, auto-renewal, payment failure handling, price-change notice, cancellation timing, refunds, credits and invoice availability. The checkout must show the amount due and renewal terms before confirmation.
6. Product limitations and professional advice
Accrod may help organize records and bring entered dates to attention. It must not be represented as guaranteeing that a customer meets legal deadlines or complies with every lease or regulation. Customers are responsible for verifying the signed agreement, amendments, notices and relevant legal obligations.
7. Availability, changes and support
Specify support channels and hours, maintenance practices, service commitments (if any), planned changes, export availability and how material changes to the terms will be communicated. Do not promise an uptime level until it is actually supported.
8. Suspension, termination and data export
Explain when either party may terminate, what happens to access, how long the customer can export data, when copies are deleted and what records must be retained by law. Destructive actions should be clear and proportionate.
9. Disclaimers and liability
These clauses require review under the laws of the chosen jurisdiction. The final document must reflect the deployed service, the contracting entity and applicable law, and should be completed only after qualified legal review.
10. Governing law and contact
Governing law, dispute process, legal notices and the correct service address must be supplied by the operator and reviewed before publication. Contact details: the operator must add a verified, monitored address before this draft is approved.
