Privacy Policy
This is a customer-facing review wireframe, not final policy language. It preserves the required topic coverage without presenting unresolved legal or privacy decisions as settled facts.
Who Revenue Alchemy Is
Revenue Alchemy’s final legal entity name, business address, and privacy contact are still under attorney/privacy review.
Information We Collect
Revenue Alchemy website forms must not collect raw card numbers, bank-login credentials, passwords, recovery codes, or private keys.
How We Collect Information
Information may come directly from a visitor or customer, from Stripe and approved service providers, through secure onboarding and approved system connections, from authorized business contacts, and through website analytics only when configured.
How We Use Information
Purpose categories under legal review include administering memberships, verifying payment/subscription status, completing onboarding, performing approved bookkeeping and invoicing work, communicating service status, maintaining security, complying with law, and improving configured website/service analytics.
Payments and Stripe
Payment credentials are entered in Stripe-hosted interfaces. Revenue Alchemy receives limited payment, customer, and subscription status needed to operate the membership. The final privacy description must match the implemented Stripe configuration.
Onboarding and Financial Information
Approved policy language must describe requested categories, secure connection and upload methods, access controls, customer responsibilities, and third-party system involvement. Never send credentials or sensitive financial records through a public form, ordinary email, text, Telegram, or Google Docs.
Cookies and Analytics
Final cookie and consent language must match the actual inventory and configuration.
Service Providers and Sharing
Provider categories may include payment processing, website hosting, secure onboarding/file handling, accounting or financial-system connections, support/communications, analytics/security, and professional/legal services. The final provider inventory and sharing language require verification.
Data Security
The final policy should describe verified access controls, approved systems, secure payment handoff, incident handling, and customer security responsibilities without claiming perfect security or unverified certifications.
Data Retention
Retention periods are not stated in this wireframe. A retention schedule must be approved before final policy language is published.
Privacy Rights and Requests
Jurisdiction-specific rights, identity verification, authorized agents, appeals or complaints, and the monitored request process remain under attorney/privacy review. No privacy-request CTA is published in this draft.
Children’s Privacy
Children’s privacy language remains under attorney review. This wireframe does not state an age threshold or final policy.
Changes to This Policy
The notice method, effective timing, and treatment of material changes remain under attorney review.
Contact Us
The monitored privacy contact and mailing address remain under attorney/privacy review.