Privacy built around purpose and control.
This policy explains how Design Corporation handles information used to provide DCORP products and connected services.
Information we process
DCORP products may process business identity information, authorised user information, operational records, product/stock records, invoices, receipts, branch information, device identifiers used for licensing, and service configuration required to provide the product.
Demo and contact requests
When you request a demo or contact DCORP, we use the name, business name, email address, phone number and message you provide only to respond to the request, arrange the demo and maintain the related support record. These requests are available only to authorised DCORP administrators and may also generate a private notification to the DCORP support inbox.
Google user data
When a user explicitly connects Google Drive, DCORP may process the connected Google account email, OAuth credentials required to maintain the connection, and DCORP-generated files managed through the Google Drive drive.file scope.
DCORP does not request access to unrelated Google Drive files, does not sell Google user data, and does not use Google user data for advertising.
Storage and security
Operational data may be stored locally on authorised devices and, where enabled, in secure service infrastructure required to provide licensing, synchronisation, receipt access or connected features. Sensitive service credentials are kept server-side and are not intentionally embedded in customer-facing APKs or public website pages.
Retention and deletion
Records are retained for as long as required to provide the service, preserve legitimate transaction history, meet legal obligations or support the user's requested workflow. Users may request access, correction, disconnection or deletion where applicable through privacy@dcorp.co.za or the Data Request page.
Google Drive disconnection
Users can disconnect Google Drive from the product and may also revoke DCORP access from their Google Account permissions. Revocation prevents future API access but does not automatically delete files already stored in the user's Drive.
Contact
Privacy enquiries: privacy@dcorp.co.za
Last updated: September 2026.
How Android installation works with your data
DCORP now supports invitation-based installation on a personal Android phone or through a managed Work Profile. These two routes use different tools, but both continue to require the appropriate DCORP licence and device approval.
- Invitations: invitation identifiers, verification attempts, expiry/redemption status and relevant security/audit information may be processed to stop reuse and abuse. A WhatsApp number entered into the Admin website may be used in your administrator's browser to prepare a message; it is not proof that WhatsApp delivered it.
- Personal phone downloads: the APK is held privately in Cloudflare R2; a limited, temporary authorisation controls download. The browser and delivery service may process network and security request metadata as needed to deliver it.
- Work Profile: ManageEngine and Google Managed Play may process the device and managed-account data needed for enrolment and app installation. The level of management and visibility depends on whether the phone is personally owned or company managed.
- Removing Work Profile: local data in that Work Profile is deleted by Android when the profile is removed. Synced business data remains subject to the business's normal account, retention and deletion rules; removal is not the same as requesting cloud-data deletion.
- Support requests: DCORP may ask for the Device ID and business contact details to verify ownership and assist with approvals, removals or installation support. Never share passwords, one-time codes or private signing keys with support.
Where applicable, you can ask about access, correction and eligible deletion through privacy@dcorp.co.za or our Data Request page. For practical steps, see the installation and Work Profile removal guide.
Website information updated 18 October 2026. The original policy statements and the current approved in-app Terms remain intact.