1. Scope and purpose
PANW Price Assistant is an internal productivity tool for authorized company colleagues to configure products, prepare budgetary quotes and organize projects. This policy covers its account and pricing backend and related support website. Until any formal company handover, Summerle Tan is responsible for account and information administration. Before a company formally takes over operation, the operator identity, administrator responsibilities and privacy contact will be updated and communicated to users. The app and this website do not represent official Palo Alto Networks support.
2. Account, license and device information
Registration and account services process a name or display name, username, account ID, registered email where provided, password-verification information, registration and approval status, license ID and validity, allowed device count, and the version and time of notices accepted. Administrator-created accounts without email do not require a real email address.
We process an app-generated random device ID, device-name label, operating-system platform, app-reported version, first and most recent connection times, device-release status, and login/session verification information. The app-generated ID is not an advertising identifier.
License-extension requests include their dates, decisions and any optional note you submit. Do not include unrelated sensitive information. These records support authentication, registration approval, licensed access, device limits, recovery, deletion and service security, not advertising or marketing.
3. Local projects and pricing requests
Project names, customer names, opportunity IDs, distributor and reseller names, status, expected close dates, notes, quote versions and configuration lists are managed in the device-local project database. The current project library does not automatically synchronize projects to a cloud project service operated by us.
To retrieve products and prices, the app sends the required SKUs, product search terms and authorization information to the pricing backend. Current pricing interfaces do not require project or customer details. Request paths and technical information can still appear in operational or network access logs.
User-initiated backups, PDF/spreadsheet exports and sharing can include project and quote details. Backups also contain an account identifier and account email where present. The system file picker, share sheet and print/export functions process files and destinations you choose. Selected apps, recipients and storage providers apply their own terms. Export files may remain in the app cache. Files kept on the device can also be affected by operating-system backup or device-management settings you independently enable.
The local project database and exported backups do not provide application-level encryption. Integrity checks are not encryption. Use protected devices and storage locations, and avoid unnecessary personal or sensitive details.
4. Logs, administrators and service providers
The pricing backend records request time, endpoint path, method, response status and duration, and account/device IDs when a session is identified. Administrative audit records may include operation targets, times, summaries and outcomes. Network addresses are used for rate limiting; NAS, reverse proxy and other infrastructure may separately retain network addresses and access logs.
163/NetEase email services deliver verification codes, password-recovery codes, registration decisions and license-extension notices. Email providers and mailbox systems process addresses, message content and necessary name, account or request information. Authorized administrators receive information needed for account and license administration. Support emails and attachments are used to answer your request; do not send passwords, API keys or unrelated confidential customer information.
This public website uses OpenAI Sites hosting. The platform processes information needed to serve visits and provides visitor/page-view statistics. Website visits are distinct from app account and pricing activity. We do not upload user databases or local project records to this static website host. Email and hosting providers apply their service and privacy terms and can process information through infrastructure outside your location; information is not guaranteed to remain only on the NAS or in one country.
We do not sell user information, use it for advertising or marketing, or use it for cross-app advertising tracking. No additional data recipients or advertising/user-behavior analytics SDKs are used in the current app flow. Necessary email, hosting and infrastructure processing is not excluded by this statement.
5. Permissions and security
The current app flow does not actively read contacts, location, the photo library or audio recordings, and does not enable user image or voice uploads. Backup restore processes the file you select; exporting and sharing are initiated by you.
Account and pricing connections use HTTPS. Login tokens and the app-generated device ID use system secure storage. Server-side passwords are stored as salted hashes rather than plaintext account records; passwords still need to be transmitted securely when registering, signing in, resetting or confirming deletion. Account, license and administrator checks restrict access. These measures do not mean local files, exports, email, logs or backups are end-to-end encrypted, and no system is absolutely secure.
6. Retention and deletion of records
Account, license and device information is retained for the period needed to provide the authorized account service. Registration and verification records are retained as needed to complete approval, account recovery or related enquiries. Expiry of a verification code or session prevents its continued use; it is not the same as deleting all historical records.
Service and security logs are retained for necessary fault investigation, access auditing and applicable legal obligations. Database backups are restricted to recovery and continuity purposes. Support and notification emails are retained for handling the relevant request and necessary follow-up. Retention is determined by these purposes, applicable requirements and administrator review, rather than a single automatic expiry for every type of record. Records should be deleted or appropriately de-identified when they are no longer needed. This policy does not claim that an automatic 7-, 30- or 90-day cleanup system is already in operation.
Historical logs, mailbox copies and server backups may remain after account deletion until their retention requirement ends and they are administratively cleared. They are not used to continue normal account access. When handling a privacy request, the administrator reviews the remaining records, explains any necessary retention and applicable limits, and assists with deletion of information that is no longer needed. Any legal retention exception is limited to the relevant records and does not justify indefinite retention of unrelated information.
Successful account deletion removes the active authentication database's account and associated license, device, session, registration, verification, extension and notice records and cleans associated administrative audit references. A hashed deletion receipt remains for safe retries. It does not directly include the original username or email, but is not claimed to be unconditionally anonymous.
7. Your choices and account deletion
Use Account > Delete Account, or Delete Account in the sign-in flow, enter the current password and confirm. Successful deletion invalidates the account's sign-ins and license and removes that account's project database records and login state on the device completing deletion. Other users and the shared price list are unaffected. A sole administrator must first transfer administrator responsibility.
Save needed work first. Deletion does not automatically erase exported/shared files, generated export copies in app caches, local records on other devices, mailbox copies, operating-system backups or old server database backups. Historical server copies follow the retention approach above. A backup restore must not be used to reactivate a deleted account without reviewing and applying the deletion request again.
Release & Sign Out frees a device slot. Sign Out ends a login. Neither permanently deletes the account, and stopping use does not automatically remove server records. For assistance, account corrections, incomplete registrations or privacy requests, contact panwapp@163.com. We may verify your identity to prevent unauthorized disclosure or deletion. We do not require a support email to initiate the app's available account-deletion flow.
8. Audience and policy updates
The app is for authorized business users, is not designed specifically for children, and does not verify age. Its content age rating does not verify the age of each user. We update this page when the app's functionality, providers or data handling changes. This policy describes the present service; it is not a guarantee that every historical copy has already been deleted.