Privacy Policy
MemberCanary Last updated: 5 September 2026
This policy explains what MemberCanary does with personal data. There are two different relationships here and they carry different obligations, so we separate them.
1. Two kinds of people, two different roles
If you are a customer — someone who runs a paid community and pays for MemberCanary — we are the controller of your account data. This policy tells you how we handle it.
If you are a member of a community that uses MemberCanary — we are a processor acting on that community operator's instructions. They are the controller. We hold your data because they asked us to, we act only on their instructions, and questions about why they use us should go to them. You can still contact us and we will route your request to them and assist.
2. What we collect about customers
- Name and email address
- Whop account identifier and billing status (we never see your card — Whop handles payment)
- Which platforms you connect, and the credentials or tokens needed to read them
- Product usage: logins, digests opened, actions taken
- Support correspondence
If you only visit our public website, Vercel Web Analytics records anonymous, aggregated page views, referrers, broad location, device type and browser type. It does not use cookies, create a cross-site profile or store your IP address in the analytics dataset. We do not send names, email addresses or member data to website analytics.
3. What we collect about community members
Only what is needed to tell whether someone is drifting away.
We collect:
| Source | Data |
|---|---|
| Whop | Member ID, plan ID, join date, membership status changes, renewal and payment-failure events |
| Discord | User ID, join date, roles, message counts and timestamps, last-active time, which channels are used |
| Telegram | Equivalent activity metadata |
| Derived by us | Engagement score, risk tier, and the reason a member was flagged |
We deliberately do not collect:
- Message content. Not from public channels, not from DMs. We count and time messages; we never read or store what they say.
- Voice or video
- Payment card details
- Any special category data (health, beliefs, biometrics, and so on)
This is a design decision, not a policy statement. The system does not need content to score disengagement, so it does not receive it.
4. Why we process it
| Purpose | Legal basis (GDPR) |
|---|---|
| Providing the Service to the operator | Processing on behalf of the controller (Art. 28); operator relies on legitimate interests |
| Billing and account administration | Contract |
| Security, abuse prevention, debugging | Legitimate interests |
| Anonymous website analytics and performance monitoring | Legitimate interests |
| Service emails to customers | Contract |
| Marketing emails to customers | Consent, withdrawable at any time |
We do not sell personal data. We do not use one customer's member data to serve another customer.
We do not use customer or member data to create or publish cross-customer benchmarks. If this changes, we will update this policy and identify the purpose and lawful basis before that processing begins.
5. Retention
| Data | Kept for |
|---|---|
| Member activity events | 13 months |
| Engagement scores | Life of the account |
| Customer account records | Life of the account, then 30 days |
| Billing records | As required by law |
| Support correspondence | 24 months |
| Aggregated website analytics | One-month reporting window on our current hosting plan |
On account closure we delete member data within 30 days. We honour earlier deletion requests where legally permitted and where the controller instructs us to do so.
6. Sub-processors
We use these providers. Each is bound by contract to protect the data.
| Provider | Purpose | Location |
|---|---|---|
| Whop | Payments, membership data source, merchant of record | US |
| Supabase | Database and file storage | Frankfurt, Germany (EU) |
| Vercel | Website hosting, anonymous analytics and performance monitoring | US / global edge |
| Resend | Transactional email delivery | US |
We will give notice before adding a sub-processor, so customers can object.
Keep this table current. An out-of-date sub-processor list is the most common gap in a small SaaS privacy policy and the easiest one for a careful buyer to catch.
7. International transfers
MemberCanary is operated from Ethiopia, and our providers are largely in the United States. Data will therefore be transferred outside the EEA and UK.
Ethiopia does not have an EU adequacy decision. Where required, transfers rely on the EU Standard Contractual Clauses and, for UK data, the UK International Data Transfer Addendum, as described in our DPA, together with appropriate supplementary measures and transfer-risk assessment.
8. Security
- Encryption in transit (TLS) and at rest
- Access limited to those who need it; today that is one person
- Platform credentials stored encrypted, never in source control
- No message content stored, which materially limits the impact of any breach
- Hosting, availability and performance monitoring is configured not to receive member records or platform credentials
We will notify affected customers of a personal data breach without undue delay and within 72 hours of becoming aware, so they can meet their own obligations.
9. Your rights
Depending on where you live, you may have the right to access, correct, delete, export, restrict or object to processing of your personal data, and to withdraw consent.
- Customers — contact us directly.
- Community members — contact your community operator, who is the controller. If you contact us first we will pass the request on and help them action it.
You also have the right to complain to your local data protection authority.
10. Children
The Service is not directed at anyone under 16 and we do not knowingly process their data. Community operators are responsible for the age policies of their own communities.
11. Changes
We will post updates here and, for material changes, email customers at least 30 days in advance.