1. What We Collect and Why
We collect account identifiers, an email address, and session information to authenticate you, secure your account, and associate your choices with the right person. Profile details, directory submissions, posts, articles, uploads, RSVPs, saved items, and session information are collected when you use those features. The category listings describe their individual purposes, recipients, and retention rules.
Optional communications use the phone number, email address, and preferences you provide. A support inquiry includes your name, email, message, and topic; a bug report can also include its page URL, browser and screen context, and a screenshot you choose to attach. We use this information to respond and maintain a support record. You can unsubscribe from optional communications without deleting your account.
A safety report includes your contact details, the reason for the report, the relevant user or content link, and your description. These reports are kept in our private support queue and routed to our safety contact. The safety-report form does not accept attachments; do not submit suspected child sexual abuse material.
Google, and Apple where enabled, supply identity information when you choose their sign-in option. Password credentials, such as a designated app-review account, are stored as hashes. Native sign-in establishes a session in the app rather than transferring your browser cookies.
Photos, video, and other files are processed when you choose to upload or send them. Camera and microphone permissions support features you request, such as capturing media or joining a call. Declining a permission prevents the associated feature. A location-based feature uses the location or address you supply for nearby results or a listing.
Stripe processes payments. We use associated contact details, payment status, and transaction history for fulfillment, receipts, subscriptions, and accounting; payment methods are not published in your profile. Infrastructure providers process connection and operational information, including IP addresses and browser information, for delivery, security, and traffic analysis.
Protected forms use Cloudflare Turnstile, which receives IP addresses, TLS fingerprints, browser information, the site origin, and form-action identifiers. It processes security signals on our behalf to detect bots. Cloudflare also uses these signals independently to improve its bot-detection capabilities, as described in its Turnstile privacy notice.
Google Fonts requests send your IP address, browser and operating system information, and referring-site information to Google for font delivery and security. These requests can occur before you sign in. Google states in its Fonts privacy information that this service does not set cookies or use this information to create end-user profiles or for targeted advertising.
We do not sell personal information or use it for cross-context behavioral advertising. We also process limited records for safety, fraud prevention, legal obligations, and establishing or defending legal claims.
2. The Three Data Tiers
All personal and user-generated data falls into exactly one of three tiers. Each tier determines how your data is stored, how long it is retained, and what happens when you request deletion.
Persistent Data
Stored for the lifetime of your account or longer.
Deletable on Request
Deleted immediately upon confirmed request
- Account credentials and authentication tokens
- Profile information (contact, address, descriptions, images, social links)
- Community referral codes and milestone attribution. An attribution identifier is remembered in the visitor's browser for up to 30 days. If they connect a Pana account, that attribution stays with the account so account creation, directory submission, and accepted Community Connector membership can each be counted once.
- Mentoring profile (expertise, languages, bio, hourly rate)
- Session notes and mentoring session metadata
- Social graph (follows, followers, likes, group memberships, story views)
- RSVPs and event attendance records
- Events you've saved or hidden, and the reason hidden events were suggested
- Notification preferences
- Intake form submissions
- Nostr identity: your public key and whether it was generated for you or brought your own (your secret key is never sent to us)
- Relay group membership records (which groups your public key belongs to, and when it joined)
- Group invitations you have sent or received (which group, who invited whom, and when it expires)
- Other member data — newsletter signups, engagement/points activity, and volunteer programme commitments
- Social timeline posts (no archive threshold — always fully deleted)
- Cloudflare R2 — uploaded media files
Community Record
Anonymizable but not deletable after archive threshold
- Published articles (archive: 3 months after publication)
- Article peer review comments (archive: follows article)
- Event records (archive: after event completion)
Third-Party Synced
Deletion initiated but subject to provider retention policies
- Stripe — email, payment method, transaction history (7-year legal hold)
- GoHighLevel — contact ID, email, name, mobile number, newsletter membership, and SMS consent status
- Google / Apple OAuth — email, name, profile image (received, not sent)
Moderation Record
Safety records retained independently of the accounts they concern. Not deletable on request: a member cannot erase reports made about them, and a reporter cannot retroactively withdraw a record that moderators relied on.
- Relay abuse reports (NIP-56) — the reporter's and target's public keys, plus a snapshot of the reported content. Retained even after the accounts involved are deleted.
Compliance Record
Records retained after account deletion to meet legal, audit, or operational obligations. Not user-deletable; kept under a legitimate-interest basis, not consent.
- Consent receipts — which policy version you accepted, when, and from what IP. Retained after account deletion as proof consent existed.
- Deletion audit log — a record that your account was deleted and what was removed. Kept as proof the deletion occurred.
- Screenname history — retained after deletion so federated servers get a stable 410 Gone for handles you no longer use.
- Contact Us inquiries, bug reports, and safety reports — your name, email address, the message you wrote, and what it was about. A safety report includes a reason and the reported user or content link, and does not accept attachments. A bug report also includes the page where it happened and basic browser, language, and screen-size details; it can include a screenshot if you choose to attach one. Retained indefinitely as the support record. General inquiries may be routed to our CRM for follow-up; bug reports and safety reports are not automatically forwarded there. A CRM copy may be removed at any time, and the record here is the one that persists.
Temporary Data
Retained only as long as necessary, then automatically purged
- Mentoring session signaling and WebRTC connection metadata
- Whiteboard state (purged 30 min after session ends)
- Real-time chat messages during mentoring sessions
- Session video/audio streams (not recorded server-side)
- OAuth tokens and transient authentication state
- IP addresses and user-agent strings (90-day analytics window)
- Email verification, magic-link, and email-change tokens (expire per config)
- Pending relay group join and leave requests (joins: until an admin acts; leaves: a 24-hour grace period)
Peer Data
Exchanged directly between participants, or propagated to servers we do not operate; not controlled by Pana MIA Club after transmission
In the Wind
Published to an open, unbounded set of servers we do not operate. Deletion requests are advisory only -- a remote server MAY honor them and MAY ignore them. Neither Pana MIA Club nor anyone else can guarantee retraction once content has propagated.
- Social posts, replies, likes, and follows federated via ActivityPub — a best-effort Delete is sent, but remote servers may ignore it
- Anything you publish to Nostr — group chat, profile metadata, RSVPs. We can remove it from our own relay; no one can remove it from Nostr at large.
Seen by Participants
Seen directly by the people you shared it with. We do not retain it; they may.
- Video and audio streams during mentoring sessions (WebRTC peer-to-peer)
- Whiteboard content visible to session participants
- Chat messages seen by the other participant before deletion
- Co-author content shared during article collaboration
- Profile information visible to other users
- Event RSVP and attendance information visible to organizers and attendees
- Information shared at in-person events (verbal, written, photos)
3. The Archive Threshold
Certain content becomes part of the community record after a defined period. Published contributions use the supported Creative Commons license selected for the content. The CC license is irrevocable — once granted, downstream recipients retain their rights regardless of whether the licensor stops distributing.
Published articles become community record three months after publication; event records become community record after the event ends. Before the applicable threshold, the content is eligible for removal. Afterward, you may choose to keep attribution or replace it with Former Member. Private account information is still eligible for deletion. Social timeline posts are eligible for deletion on our service at any age.
A license already granted to another recipient cannot be recalled by removing the source. ActivityPub peers, Nostr relays, and people who have already seen information may retain their own copies. Remote deletion notices are advisory, not a guarantee of removal.
Safety reports, consent receipts, deletion audit records, former-screenname continuity records, and lasting support inquiries may outlive account deletion for the purposes stated in the category listings. Providers may retain legally required financial records. Temporary information follows the limits listed for each category. A failed deletion or provider request can require follow-up; we do not promise that every remote copy disappears immediately.
5. Your Content Is CC-Licensed
All content you publish on Pana MIA Club is licensed under Creative Commons (CC BY 4.0, CC BY-SA 4.0, or CC0 1.0, your choice). This means the grant survives even if the content is later removed from the platform. Under CC BY and CC BY-SA you may ask us to remove your name from archived content; CC0 requires no attribution in the first place, so we simply stop displaying it. See our Terms of Service for details.
6. Your Choices and Rights
You can edit available profile fields and communication preferences in account settings. You can request access, correction, a copy of eligible information, or restriction or objection where applicable law provides those rights. We verify requests and respond according to applicable law. We do not penalize you for exercising applicable privacy rights. If a request cannot be fulfilled, we explain the reason and available follow-up.
Delete Your Pana Mia Account
Visit the account-deletion form, sign in to the account you want removed, and follow the steps. Reinstalling the app is not required: the same form works in a browser. It shows associated records, commitments that must first be cancelled or transferred, and attribution choices for archived content. Confirm the account email and submit the permanent deletion request.
If you cannot sign in or need help, email hola@panamia.club with the subject Pana Mia account deletion. We may ask for information reasonably needed to verify ownership. Do not send a password, authentication token, or payment-card information.
Deletion removes eligible account, profile, social, and associated records and initiates applicable provider and federation requests. Archived community contributions, safety and compliance records, lasting support inquiries, legally retained payment records, and copies on systems we do not control have the limits described above. Upcoming events or scheduled sessions may need to be cancelled or transferred before deletion can complete.
7. How We Protect Your Data
We use HTTPS for connections to our service, authenticated sessions, permission checks, and restricted administrative access. Password credentials, where used, are stored as hashes rather than readable passwords. Payment and identity providers apply their own safeguards to information they handle. No service or transmission method is completely secure. Protect your account, device, and Nostr secret key, and contact us about suspected unauthorized access. Do not send authentication secrets through an ordinary support inquiry.
8. Global Privacy Control (GPC)
We do not sell personal information or share it for cross-context behavioral advertising. When a consent request includes your browser's Sec-GPC: 1 signal, we record it with the consent receipt. The signal does not disable processing necessary to provide a requested feature, authenticate an account, prevent abuse, or comply with law. We do not claim that it disables all hosting logs or third-party processing.
9. Children's Privacy
Pana MIA Club is not directed at children under 18. We do not knowingly collect personal information from minors. If we discover that a user is under 18, their account will be terminated and their eligible data deleted, subject to safety and legal retention obligations. Contact us about a suspected minor's account. Our child-safety standards apply to everyone using the service.
10. International Users
We operate from the United States and focus on South Florida. Infrastructure and service providers may process information in the United States or other locations where they operate. Those locations may have different privacy laws from your own. Applicable legal rights are not waived by using the service. Contact us with questions about a specific provider, processing location, or request. We do not represent that a particular international transfer certification or contractual safeguard is in place unless we have verified it.
11. How to Contact Us
For privacy inquiries, data access requests, or to report a suspected data breach:
Pana MIA Club, Corp. (Pana Mia)
Email: hola@panamia.club
12. How We Notify You of Changes
This page displays the policy version and effective date. We publish revisions at the same URL. For a material change to how information is handled, we provide notice through the service or account contact details as appropriate and obtain renewed consent where required. We do not apply a new consent-based purpose to previously collected information without any consent required by law.