Privacy Policy

This policy describes how TYPA Management ("TYPA", "we") handles personal data in TYPA Hub, our internal operations platform at hub.typamanagement.com. TYPA Hub is not a public consumer service: access is restricted to TYPA staff and to creators contracted with the agency.

1. Who this policy applies to

• Creators represented by TYPA Management who have signed a management agreement.
• TYPA staff (administrators, managers, chat managers, chatters, editors) with active Hub accounts.
• Subscribers and third parties whose personal information may appear incidentally in records uploaded to the Hub by TYPA staff (for example, in chat screenshots that document subscriber requests).

2. Information we collect

From creators

• Identification details (legal name, stage name, contact email, date of birth where required for compliance).
• Identity-verification documents uploaded during onboarding.
• Signed management agreements processed via DocuSign.
• Banking and payment information processed via Stripe.
• Performance and revenue data synced from third-party platforms TYPA manages on the creator's behalf.

From staff

• Account credentials (name, email, hashed password).
• Activity logs associated with actions taken in the Hub.

Incidental third-party data

• Subscriber usernames, display names, and chat-screenshot images attached to custom-content requests, as recorded by TYPA chatters in the course of fulfilling those requests.

3. How we use this information

• Operating the management relationship between TYPA and represented creators.
• Sending and tracking management agreement contracts via DocuSign.
• Calculating fees, generating invoices, and processing payments via Stripe Cashier.
• Coordinating creator content production, scripting, editing, and scheduling among TYPA staff.
• Maintaining a verifiable audit trail for compliance and accounting.

4. Where data is stored

• Application data resides in a managed PostgreSQL cluster operated by DigitalOcean in the London (lon1) region, restricted to network access from TYPA's production infrastructure.
• Files (signed contracts, identity documents, chat-screenshot attachments, edited media) are stored in the typa-compliance bucket on DigitalOcean Spaces, also in the lon1 region.
• Transactional email delivery is handled by Resend.
• Payment data is processed and stored by Stripe under Stripe's own privacy and PCI commitments.
• Electronic signatures are processed by DocuSign under DocuSign's privacy commitments.

5. Sharing and disclosure

TYPA does not sell personal data. We share information only with the third-party processors listed above (each acting under contractual data-processing terms), with TYPA's professional advisers when reasonably necessary, and where required to comply with law, court order, or lawful regulatory request.

6. Retention

Account and transactional records are retained for the duration of the management relationship and for up to seven years thereafter to satisfy accounting, tax, and contractual record-keeping obligations. Identity-verification documents and signed agreements are retained for the period required by applicable regulations. Records may be retained longer where necessary to defend legal claims.

7. Your rights

Creators and staff may request access to, correction of, or deletion of their personal data by contacting us at the address below. We respond to requests within thirty days. Some categories of data (notably executed contracts and accounting records) cannot be fully erased before the end of their statutory retention period; in those cases we will explain the constraint and limit further use.

8. Security

Hub servers run on hardened virtual machines with TLS in transit; database connections require TLS; object storage and email-delivery providers are accessed only over authenticated channels. Access to administrative areas of the Hub is limited to authorised TYPA staff and is logged.

9. Contact

Questions about this policy or about your personal data can be sent to jordan@typamanagement.com.

10. Changes

We may update this policy from time to time. The effective date at the top of the page reflects the most recent revision. Significant changes will be communicated to active Hub users by email.