Effective 10 September 2026.
Who we are
The Global Peer Financing Association (“GPFA”, “we”, “us”) is a non-profit business association of institutional asset owners. GPFA decides how personal information is used on gpfa.ai, the member portal, the installed web app, and the native mobile app that uses the same member account.
Privacy questions go to members@globalpeerfinancingassociation.org or info@globalpeerfinancingassociation.org.
What this policy covers
This policy covers personal information we handle when you:
- browse the public website
- apply for membership
- create or use a member account, including on the native app
- use working groups, messaging, the directory, events, surveys, the job board, the library, or Ask GPFA
- receive email or push notifications from GPFA
It does not cover third-party sites we link to (for example a job application URL, an external news article, or LinkedIn). Those sites have their own policies.
We do not sell personal information, and we do not use it for cross-context behavioural advertising. This website does not collect payment card numbers.
What we collect and why
Each activity below names a purpose and a legal basis. Where more than one privacy law applies, the named basis is the closest GDPR/UK GDPR ground; we also identify the purpose as required under Canadian PIPEDA and give the notice required under US state privacy laws such as the CCPA/CPRA.
Visiting the public site
Our host (Vercel) records request logs that typically include IP address, URL, user-agent, and timestamps. PostHog, loaded on every page, records page views, clicks, dead clicks, JavaScript exceptions, and session replay, and may show in-product surveys. For people who are not signed in, some server events are stored under an identifier derived from the client IP address.
- Purpose
- Operate, secure, and understand the site.
- Legal basis
- Legitimate interests in running a secure website. Session replay and analytics cookies are not currently gated by a consent banner; see Cookies.
- Who sees it
- GPFA administrators via hosting logs and PostHog.
Membership applications
The join form collects organization name, abbreviation, type, website, and headquarters country; the representative’s name, role, work email, and optional work phone; answers about the annual meeting and quarterly calls; whether you agree to email from GPFA; an acknowledgment that membership includes a member-only directory; and an optional “Why GPFA?” note.
- Purpose
- Review membership interest, contact you, and invite approved representatives to set up access.
- Legal basis
- Steps at your request before a contract (the membership). Email about the application follows from that request.
- Who sees it
- GPFA secretariat and site administrators.
Accounts and sign-in
We store your work email, a hashed password, session tokens, and account status. Invite, setup, and password-reset emails are sent through our email processor. Optional LinkedIn sign-in (OIDC) can supply name and a profile photo URL. The native app signs in with the same account and holds access and refresh tokens in the device’s secure storage.
- Purpose
- Authenticate you and keep the portal limited to active members.
- Legal basis
- Contract (providing member access).
- Who sees it
- You, for your own session. GPFA administrators for lock, invite, and deletion. LinkedIn, if you connect it.
Profiles, directory, and search
A member profile includes name, mention handle, role title, country, optional bio, optional photo, skills, organization, and status. Active members of organizations marked visible in the directory can see those professional fields. Portal search indexes member-visible profile, organization, job, forum, and library text. Blocking hides the other person from directory and messaging for you; it does not erase working-group posts.
- Purpose
- Let members find and work with one another inside the association.
- Legal basis
- Contract (membership includes the directory).
- Who sees it
- Other active members, for directory fields. Work email and phone are not shown in the directory. Ask GPFA can retrieve directory name, title, organization, country, bio, and skills when a member asks.
Messaging
Direct messages and small groups store message text, participant name and photo snapshots, and private read position. Web push, when you opt in, can include a short preview of the message.
- Purpose
- Member-to-member communication.
- Legal basis
- Contract.
- Who sees it
- Current participants. Browser push services see a truncated preview if you enabled alerts. We do not put message bodies into analytics events.
Working groups
Threads, replies, attachments, polls, event RSVPs, @mentions, and resource submissions are stored as member content. Reports include the reason, optional details, and a snapshot of the reported text for co-leads and GPFA administrators. Thread summaries, when requested, send the discussion text to our AI processor.
- Purpose
- Peer discussion, moderation, and group operations.
- Legal basis
- Contract. Reports also serve legitimate interests in safety.
- Who sees it
- Active members can read group discussions. Reports are visible to that group’s co-leads and to GPFA administrators, not to the membership at large.
Surveys, polls, events, and the annual meeting
Survey and poll answers are stored against your member account. Other members see aggregates (and anonymous free-text where that feature is on). GPFA administrators can see identifiable responses when they operate the survey or poll.
Event RSVPs record attending or not attending. The product shows counts, not a public attendee list. Annual meeting registration stores the answers on that year’s form plus a snapshot of your name, email, and organization for the secretariat.
- Purpose
- Run association research, events, and the annual meeting.
- Legal basis
- Contract.
- Who sees it
- You, for your own answers. Other members, for anonymous totals. GPFA administrators, including annual-meeting exports.
Job board
Organization administrators post role title, location, description, requirements, compensation text, and an external apply URL. GPFA does not collect CVs or job applications on this site.
- Purpose
- Circulate roles among members.
- Legal basis
- Contract.
- Who sees it
- Active members. Applications happen off-site.
Security and rate limits
We limit how often some public and member actions can run. Those counters use a hashed IP address or hashed email, or your member id, in Redis. Failed sign-in and application events may also be recorded in PostHog with a reason code, not the password.
- Purpose
- Abuse prevention and service integrity.
- Legal basis
- Legitimate interests in securing the service.
- Who sees it
- GPFA operators and the cache/analytics processors.
Directory and contact details
Membership includes a member-only directory of professional profiles: name, handle, title, organization, country, photo, bio, and skills. Work email and phone collected on the application are for the secretariat and for your account. They are not published in the directory.
There is no per-member “hide me from the directory” control. An organization can be taken out of the directory by a GPFA administrator. You can edit your profile, change your handle, remove your photo, and block another member.
Who we share with
We share personal information with service providers that process it on our instructions, with other members where the product does so, and when the law requires it. We do not sell it to sponsors or data brokers.
- Supabase — authentication, database, file storage, and realtime. Accounts, profiles, applications, forums, messages, surveys, registrations, and files live here.
- Vercel — hosting, HTTPS logs, and scheduled jobs.
- Redis Ltd (Redis Cloud) — short-lived cache and rate-limit counters. Message bodies are not stored there.
- OpenAI — Ask GPFA, conversation titles, working-group thread summaries, avatar image moderation, indexing of published GPFA materials, and the member-news radar (which does not send member profiles).
- Resend — transactional and campaign email, plus unsubscribe state. Delivery events are written back into GPFA.
- PostHog (US cloud) — product analytics, exception capture, session replay, and surveys, including for signed-in members identified by member id, name, organization, role, and country.
- LinkedIn — only if you connect your LinkedIn account. LinkedIn is an independent controller of its own service.
- Browser and operating-system push networks (and, for the native app, Apple/Google/Expo push) — device tokens or web-push endpoints, and a short notification payload.
Other members see what the product is built to show them: directory profiles, working-group posts, poll and survey aggregates, and messages they participate in. GPFA administrators see additional operational data needed to run the association.
Artificial intelligence
Ask GPFA sends your question, recent turns in that conversation, your name and organization (so first-person questions resolve), and retrieved member-visible material — directory fields, catalogue titles, events, and excerpts from indexed GPFA documents — to OpenAI. Those chat calls are configured not to be stored by OpenAI as model training examples. Conversations are stored in GPFA until you delete them. Only you can open your Ask GPFA history in the product.
Working-group summaries send the thread title, opening post, and replies to OpenAI. Avatar uploads are checked with OpenAI’s moderation API. Published GPFA materials may be uploaded to OpenAI vector stores so Ask GPFA can cite them. Direct messages are not indexed there.
The news radar asks OpenAI to search the public web for industry articles. That pipeline does not send member profiles. Those OpenAI runs are configured to be stored on OpenAI’s side.
Ask GPFA answers can be wrong. They are not legal, investment, or compliance advice.
Email and notifications
Members can turn off working-group post, event, announcement, survey, and campaign emails in notification settings. Campaign emails also include a provider unsubscribe link. Operational messages about your account (invites, password reset, access) still need to be sent for the service to work.
Browser push is off until you allow it in the installed web app. Native push uses a device token stored against your account. Message alerts may include a preview of up to 120 characters.
How long we keep information
We do not currently run an automatic deletion schedule for most records. In practice:
- Application, account, profile, forum, survey, and similar records last for as long as they are needed to run the membership, and for a reasonable period after an account is closed.
- GPFA administrators can permanently delete a member account. Forum posts then keep the discussion with the author field cleared; messaging history keeps a “[Deleted user]” snapshot; open annual-meeting registrations are withdrawn but name/email snapshots on the registration can remain.
- You can delete Ask GPFA conversations you own.
- Leaving a message group hides the conversation from you; the history remains for remaining participants.
- Removed working-group posts are hidden from members and kept for moderation audit.
- Organization activity receipts are shown to organization administrators for 90 days; the underlying log is not auto-deleted.
- Rate-limit and cache entries expire on short windows (minutes to a day, depending on the key).
- PostHog and other processors keep data according to their products and our project settings.
International transfers
Members and processors are in more than one country. Personal information is stored and processed in the United States by PostHog (US cloud) and, typically, by OpenAI, Vercel, Supabase, Resend, and Redis Cloud. If you access GPFA from outside those countries, your information is transferred in order to provide the service.
Your rights
Depending on where you are, you may have the right to access, correct, delete, or obtain a copy of personal information, to withdraw consent (for example marketing email or push), to object to or restrict certain processing, and to complain to a supervisory authority (including a Canadian privacy commissioner or a European or UK authority). We honour access, correction, deletion, and marketing-opt-out requests from members and applicants.
In the product you can edit your profile, skills, photo, and handle; manage email categories; disconnect LinkedIn; block members; unsubscribe from groups; delete Ask GPFA conversations; and unsend a message for a short window. There is no self-service data-export or account-deletion button. Email members@globalpeerfinancingassociation.org for access, correction, or deletion requests. We may need to verify that the request comes from the member, and we may retain information where we must (security, dispute, or legal obligation).
We do not sell personal information or share it for cross-context behavioural advertising, so there is no “Do Not Sell or Share” toggle. We do not use sensitive personal information to infer characteristics for advertising.
Children
GPFA is for adult professionals representing institutional members. We do not knowingly collect personal information from anyone under 18.
Changes
We will update this page when the product or our practices change. The effective date at the top will change. Material changes that affect members may also be noted in the portal or by email.
Contact
Global Peer Financing Association
members@globalpeerfinancingassociation.org
info@globalpeerfinancingassociation.org
See our Terms of Service for membership, acceptable use, and competition rules.
