DCORP Invoice & Stock Terms and Conditions.

Current binding app Terms: Version 2026-09-27-1 — approved. The full previously approved text below is retained unchanged.

1. AGREEMENT AND AUTHORITY

These Terms and Conditions govern access to and use of the DCORP Invoice & Stock application, related licence services, device approval services, managed business synchronization, receipt/QR services, backup and Google Drive features, branch administration and support services supplied by Design Corporation (“DCORP”, “we”, “us” or “our”). By selecting “I accept”, the person accepting confirms that they have read these Terms and, where they act for a business or organisation, that they have authority to bind that business or organisation (“Customer”, “you” or “your”). If you do not accept the current Terms, you may not activate or continue using the application where acceptance is required.

2. LICENCE TO USE THE APPLICATION

Subject to payment arrangements, an active DCORP licence, approved device access and these Terms, DCORP grants the Customer a limited, non-exclusive, non-transferable and revocable right to use the application for the Customer’s internal business operations. The application is licensed, not sold. No ownership of the software, source code, branding, designs, licence system or other DCORP intellectual property is transferred to the Customer.

3. DEVICES, APPROVAL AND ACCESS CONTROL

Each installation may receive a device identifier used for licensing, security and support. Device access may be PENDING, APPROVED, SUSPENDED or REVOKED, and a device may be removed from the active device register by DCORP. Licence limits may apply to the number of approved devices and branches. A removed, suspended or revoked device does not gain a right to continued use merely because application data remains on that device. The Customer must not tamper with licence controls, bypass device restrictions, falsify device identity, reverse engineer protected licence functions or use another customer’s licence.

4. TERMS ACCEPTANCE AND RE-ACCEPTANCE

A device cannot be approved, and may not continue approved access, unless the current Terms version has been accepted through the application and the acceptance record is available to the DCORP licence service. When DCORP publishes a materially updated Terms version, prior acceptance does not satisfy the new version. The application may therefore require the Customer to review and accept the updated Terms before normal approved access resumes. Acceptance records may include the Terms version, device identifier, acceptance name and timestamp.

5. CUSTOMER ACCOUNTS AND USER RESPONSIBILITY

The Customer is responsible for its owner, manager and employee accounts, PINs, permissions, device security and user activity. The Customer must ensure that only authorised persons use the application and must promptly remove access for persons who should no longer have it. Actions performed by authorised users may be recorded in local or server audit records where the relevant feature supports auditing.

6. BUSINESS DATA AND ACCURACY

The Customer remains responsible for the accuracy and legality of business information entered into the application, including product, stock, pricing, tax, customer, supplier, sales, invoice, branch and employee information. DCORP does not independently verify commercial records entered by the Customer. The Customer must review invoices, receipts, stock figures, tax settings, reports and exported documents before relying on them for accounting, tax, legal or business decisions.

7. LOCAL DATA, MANAGED BUSINESS SYNC AND SERVER PROCESSING

The application is designed to operate with local device data and may also use DCORP-managed synchronization to keep supported business records available across authorised devices. Where managed synchronization is enabled, relevant operational records may be transmitted to and processed by DCORP’s configured cloud infrastructure for synchronization, conflict handling, recovery and multi-device operation. This operational synchronization is separate from privacy-minimised licence heartbeat telemetry. DCORP does not acquire ownership of the Customer’s business records by processing them for these services.

8. BACKUPS, ARCHIVES AND DATA RECOVERY

The application may provide encrypted local backup, managed synchronization, receipt archiving and Google Drive backup/archive features. These mechanisms serve different purposes and no single mechanism should be treated as an absolute disaster-recovery guarantee. The Customer should verify that important backups have actually completed and should retain appropriate independent business records. A displayed “success” status confirms the application’s recorded result at that time; it does not guarantee that a device, network, cloud provider or third-party account will remain available indefinitely.

9. GOOGLE DRIVE AUTHORIZATION AND RESPONSIBILITY

Where the Customer connects Google Drive, the Customer authorises the application and DCORP’s supporting services to use the permissions required for the selected Drive feature. Files may be created, updated or replaced within the scope granted by the Customer. The Customer remains responsible for its Google account, available storage, access permissions and compliance with Google’s terms. Disconnecting or losing access to Google Drive may prevent new Drive backups or archives but does not by itself transfer ownership of the Customer’s files to DCORP.

10. RECEIPT AND QR SERVICES

Where digital receipt or QR features are used, receipt data or generated receipt images may be temporarily processed or hosted through DCORP-supported services so that the QR link can continue to resolve, including after a receipt is archived to Google Drive. A public receipt link is intended to expose only the receipt content required for that receipt experience, not the Customer’s full application database. DCORP may repair or republish an archived receipt link when required to keep an existing receipt QR functional.

11. THIRD-PARTY SERVICES

Google, Supabase, internet service providers and other supported third parties operate under their own terms, privacy practices, quotas, outages and account rules. DCORP is not responsible for a third party suspending, restricting, changing or discontinuing its service, but DCORP will take reasonable steps to maintain supported integrations where practicable.

12. PRIVACY AND LICENCE-SERVICE TELEMETRY

To operate licensing, security, device approval and support, the DCORP licence service may process limited technical information such as the licence identifier, application identifier, device identifier, application version, platform, licence/device status, Terms version, Terms acceptance name and timestamp, licence validation times, heartbeat times, signed offline-lease information and administrative status. The normal licence heartbeat is designed to carry licence-health information rather than customer invoice, stock, customer, supplier, receipt or transaction contents. Operational business synchronization, where enabled, is a separate service described in clause 7. Personal information must be handled in accordance with applicable data-protection law and DCORP’s privacy practices.

13. LICENCE HEARTBEAT AND SIGNED OFFLINE ACCESS

The application is designed to perform privacy-minimised online licence validation and a periodic heartbeat, including a forced internet validation cycle approximately every fifth day when the application is being used. DCORP may issue a cryptographically signed, time-limited offline allowance for an approved device. The permitted period may be 0, 1, 3, 7 or 30 days depending on the licence configuration and may end earlier if the licence itself expires. Offline access is temporary permission, not a guarantee of indefinite use without internet access. Expiry, suspension or failure of a licence check does not by itself delete the Customer’s local business data.

14. REMOTE DEVICE AND LICENCE ADMINISTRATION

DCORP may approve, suspend, restore, revoke, remove or otherwise administer a device or licence through the DCORP Admin Control where reasonably required for licensing, payment, security, support, misuse prevention or customer-requested administration. DCORP may also require a device to re-authenticate, revalidate its licence or obtain a new signed offline lease. Removing a device from the active device register releases that device’s licence slot but does not mean that customer operational records, receipts, invoices, stock records or Drive backups are intentionally deleted. Administrative actions may be retained in audit history.

15. BRANCH CONTROL

A single-branch Customer may use the application without visible multi-branch controls. Additional branches require DCORP approval and may be subject to licence limits or separate commercial arrangements. DCORP may approve, suspend or reactivate additional branch access. Where branch status affects application access or synchronization, the application may enforce the current server-side branch state. Suspension of a branch does not by itself delete the Customer’s historical branch data.

16. FEES, RENEWAL, SUSPENSION AND REVOCATION

Licence fees, subscription periods, additional branch pricing and other commercial charges are agreed separately with DCORP. DCORP may suspend or revoke a licence or device where payment is overdue, the licence has expired, a device is unauthorised, the Customer materially breaches these Terms, security misuse is detected, or continued access would create a legal or security risk. When access is blocked, the application may display the Device ID and direct the Customer to support@dcorp.co.za. Suspension, revocation or device removal does not by itself intentionally delete the Customer’s local business records.

17. UPDATES AND COMPATIBILITY

DCORP may release updates for security, compatibility, bug fixes and product improvements. The Customer should install supported updates using DCORP-provided distribution channels. Updates intended to preserve an existing installation should use the same official Android application identity and signing key. DCORP is not responsible for problems caused by unofficial, modified, repackaged or tampered copies of the application.

18. ACCEPTABLE USE

The Customer must use the application lawfully and must not use it to commit fraud, unlawfully process personal information, infringe intellectual property rights, interfere with the service, introduce malicious code, attack DCORP infrastructure, falsify licence records, defeat security controls or enable unauthorised access. DCORP may investigate suspected abuse and may restrict access where reasonably necessary to protect the service, customers or third parties.

19. INTELLECTUAL PROPERTY

DCORP retains all rights in the application, software architecture, source code, licence system, visual identity, trademarks, documentation and original materials supplied by DCORP, except for third-party components governed by their own licences. The Customer retains ownership of its own business content and records, subject to the permissions required for DCORP and supported processors to provide the selected services.

20. SERVICE AVAILABILITY AND NO ABSOLUTE GUARANTEE

DCORP will take reasonable steps to provide a functional and secure service, but software and online services can experience defects, device failures, internet failures, third-party outages, account restrictions or events outside DCORP’s reasonable control. DCORP does not promise uninterrupted or error-free operation and does not promise that any backup, synchronization, receipt-hosting or archive system can provide a permanent 100% guarantee against every possible loss. Nothing in these Terms excludes obligations that cannot lawfully be excluded.

21. LIMITATION OF LIABILITY

To the maximum extent permitted by applicable law, DCORP will not be liable for indirect, incidental or consequential loss arising from use of the application, including loss caused by incorrect data entered by users, unsupported modifications, failure to maintain reasonable backups, third-party service outages or unauthorised access caused by the Customer’s failure to secure its accounts or devices. Any limitation in these Terms is subject to rights and remedies that applicable law does not permit the parties to exclude or limit.

22. SUPPORT AND PRIVACY CONTACTS

For licence blocks, device approval, device removal, branch access or application support, contact: Email: support@dcorp.co.za The Customer should provide the Device ID shown by the application when reporting a licence or device-access problem. For privacy-related queries, contact: Email: privacy@dcorp.co.za

23. CHANGES TO THESE TERMS

DCORP may update these Terms to reflect product, legal, security or commercial changes. Where a new version requires renewed acceptance, the application will present the updated Terms before continued approved access. Acceptance of an earlier Terms version does not automatically count as acceptance of a later version.

24. GOVERNING LAW

These Terms are governed by the laws of the Republic of South Africa. Any dispute should first be raised with DCORP through support@dcorp.co.za so the parties can attempt to resolve it in good faith. Nothing in this clause removes any forum, remedy or consumer right that applicable law makes available and does not permit the parties to exclude.

25. ENTIRE AGREEMENT AND SEVERABILITY

These Terms, together with any written commercial quotation, order, licence arrangement and applicable privacy notice agreed between DCORP and the Customer, form the agreement governing the application to the extent they apply. If a provision is found unenforceable, the remaining provisions continue to apply as far as lawfully possible.

Version 2026-09-27-1 · Published for DCORP Invoice & Stock.