Privacy policy

1. Scope and authorization

The app is currently for authorized internal testing and use with companies the operator owns, administers or is otherwise permitted to access. Each QuickBooks Online company requires Intuit authorization. Being able to sign in with an email address does not itself grant permission to another company’s data.

The real-company workspace supports company verification and export. It does not expose accounting posting, update, delete or inactivation. Import preparation and guarded native deletion testing are separate sandbox features.

2. Data the app accesses

After authorization, the app can request company identity and supported accounting records. Returned information can include company/customer/vendor/employee names, contact and address fields, transaction dates, amounts, accounts, tax/currency fields, record IDs and transaction links. Only fields returned by the API are available.

If a source CSV/XLSX is loaded for sandbox import preparation, its supplied content, mapping choices and validation results are processed locally. Limited customer, vendor, invoice, bill and journal-entry create profiles are implemented for guarded sandbox review and testing. Execution is locked by default, native testing is incomplete, and each permitted test requires a separately reviewed, exact authorization. Production import posting is blocked.

3. Purpose of processing

The app uses the information to verify the intended company, search/preview supported records, generate user-requested exports, validate import preparation, review explicitly authorized sandbox changes, and maintain operation/audit evidence. It preserves supplied source text and values rather than automatically cleaning or repairing them.

The current app has no configured advertising, data-sale or third-party analytics integration.

4. Where data and credentials are kept

The accounting backend runs on a Windows PC in Pakistan and listens only on loopback addresses. The public information website does not run that backend or receive its QuickBooks record data.

App credentials and authorization tokens are stored in Windows Credential Manager for the Windows user. Production and sandbox have separate credential targets. Secrets are not returned to the browser or placed in project/configuration files by the app. The private token input clears after submission.

Import previews and bounded sandbox reviews use memory. Export searches are captured in temporary local files on this PC. Temporary search captures are removed when cleared, replaced or the app closes; temporary generated download files are removed when their stream closes, including failed requests. Saved downloads, generated receipts, source/validation audits, pre-change snapshots and operation journals may remain in local files. These ordinary source/export/audit files are not automatically encrypted by the app. Their protection depends on the operator’s Windows, device, backup and access controls.

5. External services

The app communicates directly with Intuit over HTTPS for authorization maintenance, company verification, API reads and separately authorized, supported sandbox test writes. Initial real-company authorization uses Intuit’s official OAuth Playground. Intuit handles its own login, consent and service data under its own policies.

These information pages are prepared for accuportix.radiantaccounting.net on cPanel hosting, separately from the accounting PC. When published, hosting infrastructure may process normal request information such as IP address, browser details, requested URL, time and security/service logs. The pages do not request QuickBooks credentials, tokens, company files or financial records and do not include an accounting-data upload form.

If you email the operator, the message and its delivery metadata are processed through the relevant email providers and used to address your request. Do not send app secrets or company record exports by email.

6. Retention and local deletion

The app has no automatic schedule that erases all local exports and audit evidence. The operator controls local files and should retain or remove them according to legitimate business, backup and applicable record-keeping needs. Source snapshots are not complete restorable QuickBooks company backups.

Disconnect removes the saved local authorization grant and attempts Intuit revocation. Saved app credentials remain available for later explicit use. Disconnect does not erase previously downloaded exports, original source files, audits, journals or copies in backups. Those files must be managed separately by the operator.

7. Security and access limits

The app uses environment-specific API hosts, local request-origin and antiforgery checks, serialized provider access and explicit company verification. A saved authorization after restart is not shown as Connected until a fresh authenticated probe succeeds. Production accounting write requests are blocked in the current local workspace.

These controls do not establish a security certification or a guarantee against every device, account or network risk. The operator remains responsible for its computer access and business procedures.

8. Requests and updates

For questions or applicable access, correction or deletion requests relating to the app, contact hamza@radiantaccounting.net. The operator may need to establish your authority and consider applicable retention obligations. QuickBooks source-record changes and account requests are handled through authorized QuickBooks access and Intuit’s processes.

This policy should be reviewed when hosting, app capabilities, operators, data sharing or retention practices change. Updated text and its effective date will be shown here when adopted.