Last updated: 09 July 2026

Privacy Policy

This policy explains what information ReleaseHQ collects during beta, why it is used, and how users can ask questions or request changes.

Starter beta document. This is written in plain language for early testing and should be reviewed by a qualified lawyer before a public paid launch.

1. Information we collect

We may collect account details such as name, email address, password hash, studio or organization name, and role.

We may collect billing setup information such as billing contact name, billing email, billing phone, auto-renewal consent timestamp, billing status, and payment provider customer/subscription IDs. ReleaseHQ should not collect or store raw card numbers, CVV, or sensitive payment credentials.

We may collect client and project information added by users, including client names, email addresses, phone numbers, company names, project names, milestone details, comments, approval records, payment references, UTR numbers, invoice details, and uploaded payment screenshots.

We may collect uploaded files and preview files, such as presentations, drawings, layouts, BOQs, invoices, contracts, images, and other deliverables.

We may collect technical and audit information such as login activity, secure link activity, file upload activity, approval events, release events, timestamps, and basic system logs.

We may collect beta feedback you choose to submit, including what felt confusing, what felt useful, pricing feedback, and feature requests.

2. How we use information

We use information to provide the ReleaseHQ workflow: accounts, dashboards, client review links, file previews, approval records, payment proof tracking, release checks, audit trails, and beta support.

We may also use information to improve product reliability, debug errors, understand feature usage, prevent misuse, and communicate important beta updates.

Beta feedback may be used to prioritize features, improve workflows, refine pricing, and decide what ReleaseHQ should become before public launch.

3. Legal and consent basis

During beta, ReleaseHQ processes personal information because users provide it to use the product, invite clients, record approvals, and track payment proof.

If you add a client’s contact details or send a client review link, you are responsible for having a valid reason or consent to share that information with ReleaseHQ.

4. Service providers

ReleaseHQ may rely on third-party infrastructure providers for database hosting, app hosting, file storage, email delivery, analytics, support, and payment links. These providers process information only to help operate the product.

Current beta infrastructure may include services such as hosted PostgreSQL databases, deployment platforms, email providers, storage providers, and payment providers selected for the product.

5. File and payment data sensitivity

Project files, drawings, client records, invoices, UTR numbers, and payment screenshots can be sensitive. Upload only what you are comfortable testing in a beta product.

Do not upload highly confidential, regulated, government-restricted, medical, financial, or unusually sensitive material unless you have reviewed the risks and obtained appropriate permissions.

6. Data retention

We keep beta data for as long as needed to provide the product, support users, maintain audit trails, resolve issues, and improve ReleaseHQ.

Client review links are intended to expire after 15 days. Review files may be deleted after the retention period. Released final files may be removed from storage after the first successful download.

You may ask for deletion or export of your beta workspace data. Some records may need to be retained for audit, security, dispute-resolution, legal, or backup reasons.

7. Security

We use reasonable technical and organizational measures for a beta product, including login controls, private file storage patterns, signed preview/download links, and database-backed access controls.

No online product can guarantee perfect security. Keep your password safe, limit who receives client links, and keep independent backups of important deliverables.

8. Your choices and requests

You may ask to access, correct, export, or delete personal information connected to your beta account, subject to technical, legal, security, and audit constraints.

If you are a client who received a ReleaseHQ link, contact the consultant who invited you, or contact the ReleaseHQ beta team if you need help finding the right owner.

9. Children

ReleaseHQ is intended for professional and business use. It is not intended for children.

10. Contact

For privacy requests or beta support, contact the ReleaseHQ founding team through the support email or WhatsApp channel shared with beta users. Formal privacy contact details should be added before public paid launch.