Data Handling Statement

1. Data Categories

PyxiVisio may handle account data, subscription request data, contact form data, forecast inputs, uploaded Excel templates, campaign assumptions, market selections, platform allocations, subscriber or audience summaries, historical campaign files, generated reports, PDF or Excel exports, feedback and support records.

2. Purpose of Handling

Data is handled to authenticate users, operate product workflows, generate forecasts and reports, save history, support versioning, run exports, provide feedback and support, maintain admin visibility, debug issues, protect security and improve product reliability.

3. Data Minimization

Users should enter only the business data needed for the relevant forecast or planning workflow. The products are not designed to require personal consumer-level records, government identifiers, payment card numbers, health data or sensitive personal data.

4. Uploaded Templates

Excel templates may include validation rules, required columns and protected formatting to reduce upload errors. Users remain responsible for checking that uploaded files contain authorized, accurate and appropriate business information.

5. Forecast History

Forecasts and versions may be stored so users can review history, compare scenarios, revisit reports and maintain decision context. Where product history deletion is available, user-deleted items may be hidden from the user interface and may later be purged through administrative cleanup workflows, subject to backup, audit and operational limits.

6. Admin and Support Access

Authorized administrators or support personnel may access limited account, session, feedback and operational records where needed to manage users, troubleshoot issues, respond to requests, maintain security, perform cleanup or support subscription administration.

7. Retention and Cleanup

Data is retained for product operation, customer access, support, audit, legal, billing, security and improvement purposes. Generated test data and user-deleted history may be cleaned through maintenance workflows before launch or during normal operation.

8. Security Practices

PyxiVisio uses reasonable safeguards such as access-controlled accounts, session timeout, validation, table-level organization, controlled admin pages and operational monitoring. Customers should also apply their own internal controls before entering confidential business data.

9. Data Quality and Validation

Forecast outputs depend on valid inputs. Templates, forms and dashboards may include rules, required fields, formulas, protected cells or warnings to reduce incorrect submissions, but users must still review data before upload or forecast generation.

9A. Public Website Analytics

Public marketing and sample pages use a consent-controlled Google Analytics 4 implementation. Analytics remains inactive unless the visitor accepts optional analytics cookies. We exclude administrator, sign-in, password-recovery and private forecast-workspace pages. Page addresses are sanitized, and form values, email addresses, account identifiers, reset tokens and forecast inputs are not sent.

Visitors can select Essential only or later change their choice using the Privacy choices control. Hostinger may separately process server access and error logs as part of hosting, security and service operation.

10. Data Requests

Requests for data correction, deletion support, access help, export support or account changes can be sent to support@pyxivisio.io. Requests may require identity, account or company authorization checks.