Privacy Policy
Effective date: October 7, 2026
PipSocial is a community for discussing forex and other financial markets. This policy explains what information is handled when you browse, create an account, use Google sign-in, or contribute to the community.
Who operates PipSocial
PipSocial is operated by Dayo Babatunde. For privacy questions, access requests, corrections, or deletion requests, email temibabs5050@gmail.com.
Information we collect
- Account information: your email address, account identifier, authentication status, and the display name you choose. Supabase manages email/password credentials and authentication sessions. PipSocial does not store your password in its community database.
- Google sign-in: when you choose Google, Google and Supabase provide account identity information, including your email address, name, and available profile information such as a profile image. PipSocial currently uses your verified email and account identifier for authentication, and may use your name to initialize your public display name. A Google profile image may be handled by the authentication provider even though PipSocial does not currently display it.
- Community activity: profile bios, ideas, price levels and explanations, uploaded chart images, replies, discussions, polls and votes, likes, followed traders, watchlists, saved ideas, notifications, and reports.
- Private features: journal entries and trader mute/block settings associated with your account.
- Technical information: the hosting and authentication services may process IP addresses, browser information, request details, security events, and service logs to deliver and protect the site.
How information is used
We use information to authenticate accounts, maintain profiles and preferences, display community contributions, provide private features and notifications, send account confirmation and password recovery emails, moderate content, investigate abuse, and keep the service working.
Google user data
Google sign-in requests only basic identity scopes: OpenID, email, and profile. It does not give PipSocial access to your Gmail messages, Google Drive files, contacts, or calendar. We use Google account information for account creation, authentication, and related profile display. We do not sell Google user data or use it for advertising or AI model training. PipSocial's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Public and private information
Your display name, bio, community posts, chart uploads attached to visible posts, replies, and other public contributions may be viewed by visitors and members. Your sign-in email is not displayed on community posts. Aggregate poll results are public; voter identities are not shown in the poll results interface.
Your private journal, saved ideas, watchlist, and mute/block controls are restricted to your account through the site's interface. Authorized service operators and infrastructure providers may process stored information for support, security, or service maintenance. These features are not a promise of end-to-end encryption. Avoid posting account credentials or confidential financial records.
Calculators and shared links
Calculator calculations run in your browser. Calculator inputs and results are not automatically saved as community records. If you choose to share a calculation link, the link includes the calculation assumptions, including any amounts you entered; anyone with that link can read those assumptions. Downloaded spreadsheets and CSV files are saved on your device.
Services that process information
- Supabase provides account authentication and related account storage. Google provides Google sign-in when you select it.
- Resend delivers account emails through the configured Supabase email service.
- OpenAI Sites and Cloudflare provide website hosting, community database and file storage infrastructure. Earlier ChatGPT-authenticated accounts may still use OpenAI's authentication service.
- TradingView supplies embedded charts and calendar widgets. Loading these widgets connects your browser to TradingView, which may process technical information and use cookies under its own policies.
These providers process information under their own policies and service arrangements. Information may be processed in countries other than your own. We may also disclose information when required by law or reasonably necessary to protect users, investigate abuse, or maintain service security.
Cookies and security
PipSocial uses authentication cookies to maintain sessions. Its Supabase session cookies are Secure and HttpOnly. Embedded third-party services may use additional cookies. Blocking authentication cookies can prevent sign-in. We restrict member actions using server-side account verification, but no internet service can guarantee absolute security.
Retention and deletion
Account and community records are retained while needed to operate the service. You can edit your profile and use available content and journal controls. To request access to your information, corrections, account deletion, or removal of other stored information, contact the email above. We may need to verify your identity before acting. Some records may be retained where necessary for security, legal obligations, or dispute resolution, and removal from backups or provider systems may take additional time. Other users may retain copies of previously public content.
Your choices
You can browse public content without signing in, choose email/password instead of Google, change your display name, sign out, or request deletion. You can also revoke PipSocial's Google access through your Google account's third-party connections settings. Revoking that connection does not by itself delete your PipSocial profile or contributions.
Children
PipSocial is intended for adults and is not directed to children. If you believe a child has supplied personal information, contact us so we can investigate and address it.
Changes to this policy
We may update this policy as the service changes. The effective date above will reflect the latest update. Material changes will be communicated through the site or another appropriate channel.