Tapmy security overview
Security on Tapmy is shared. Tapmy runs the platform, creators protect their accounts and customer data, buyers protect their own logins, and Stripe Connect handles payments and payouts.
On this page
What kind of security question is it?
Pick one: account protection, customer data, payment safety, abusive content, a compromised login, or a product vulnerability. Each needs different evidence. Never send passwords, one-time codes, API keys, full card details, bank credentials or ID documents in a support message.
Who is responsible for what?
Tapmy operates and maintains the platform's controls and responds through its own processes.
Creators are the sellers. You are responsible for your offers, delivery, support, taxes and refund policy, and for handling customer information you can access. Limit permissions, secure your email and connected accounts, export as little as you can, and review public content before publishing.
Buyers should give accurate contact details, protect their email and payment accounts, and check messages before acting. They go to the creator for delivery or refund questions, and to Tapmy for platform problems, account safety or suspected impersonation.
Stripe processes payments and pays creators out through Stripe Connect, and decides payout availability and timing. A Tapmy order or analytics number is not a bank payout, and it is never a reason to share card credentials.
How do I protect my account?
- Use a unique password kept in a reputable password manager.
- Secure the email tied to Tapmy with strong recovery options and multi-factor authentication where offered.
- Turn on any Tapmy authentication controls you see in your account.
- Keep your browser, operating system and devices updated.
- Review connected services and remove ones you no longer use.
- Confirm sensitive requests through a Tapmy route you already know, not a link in a message.
- Limit customer exports and share summaries when you can.
- Keep test and live activity clearly apart.
- Report suspicious access or content quickly and keep the evidence.
Do not reuse passwords, share logins casually, or paste customer data into public notes or AI prompts. Redact screenshots before sending them to support.
What does good security hygiene look like?
- You know who owns account, email, payment and customer-data duties.
- Strong sign-in and recovery are on where available.
- Team and connected access is limited to what is needed.
- Evidence you send to support is redacted.
- You know where to escalate suspicious activity.
What if something goes wrong?
If you think your account is compromised, stop editing and follow Report a compromised account. If a message asks for credentials or payment secrets, see Recognize phishing and fake Tapmy messages. For fraud, impersonation, abuse or rights claims, save the URLs and timestamps and do not repost the content.
No single setting makes you safe. Product controls, people, devices, email, integrations and data habits all matter.
What next?
Read Protect your Tapmy account, Tapmy and payment data and Customer data protection for creators. Report platform security concerns to Tapmy Support with the minimum safe evidence.