promp2u · COMMUNITY INFORMATION
Privacy policy
What we collect, why we use it, and the choices you have when you join the community.
Last updated 12 October 2026
Who operates this community
promp2u is operated by Alyph, the community owner (@fiborsi8). This policy covers the promp2u website and its account, community and journal features. The owner is the contact for privacy questions and requests.
Google sign-in
With your consent, we request the Google scopes openid and email to verify your identity. Google provides a unique account identifier and email information. Our server checks Google's signed identity token, including its email-verification status, and stores the unique Google identifier linked to your promp2u profile.
The current Google login does not save your Google email address in your community profile, publish it to other members, or request access to Gmail messages, Drive files, contacts or calendars. We do not keep Google access or refresh tokens for ongoing access to your Google account. Google sign-in information is used for authentication and account linking, not advertising or AI model training.
You can revoke the connection in your Google Account settings. This stops future Google sign-ins unless you reconnect; it does not automatically delete your promp2u profile or end an existing website session. Sign out of the website to end that session.
Your account and contributions
We store the profile details you choose to provide, including your display name, username, bio, interests, profile photo and cover image. We also store contributions and interactions such as posts, comments, prompts, saves, likes, prompt-copy records and reports so the community features work.
ChatGPT sign-in supplies an account identity through our hosting service. If you set an optional username password, the server stores a salted password hash rather than the password itself. Existing members can connect Google from Account & security to keep one profile; accounts are not automatically merged by matching email addresses or usernames.
Public and private information
Your profile and public contributions can be viewed by visitors, including people who are not signed in. Prompt-copy counts may be displayed publicly. Saved items, recently copied lists and journal entries are available through the application to their account owner. Public experiment records follow the visibility selected when sharing.
Private visibility restricts normal application access; it is not end-to-end encryption. Service operators and infrastructure providers may process stored information to operate, maintain and secure the service. Avoid uploading account passwords, broker credentials or other information you do not want processed by the service.
AI features and service providers
The website is hosted with OpenAI Sites and uses Cloudflare-backed storage. Google and ChatGPT process their respective sign-in flows under their own privacy policies.
Public posts, related public profile details and moderation reports may be submitted to the owner's configured external AI service for moderation suggestions. These suggestions require owner approval before a moderation action is applied. Private journal entries are not included in that moderation feed. Public news posts from the labelled AI account may be generated and published automatically from external research sources.
Opening a broker, news-source or other external link takes you to a separate service with its own data practices. Broker links may be referral links.
Support requests
Signed-in support requests store your profile reference, topic, messages, review status and timestamps. These conversations are visible through the application only to you and the Owner. They are excluded from the AI moderation queue and research tools. Email support is handled in the Owner’s email account. Do not include passwords, one-time codes, API keys or private trading records. Support records and private backups currently have no automatic deletion schedule; the Owner will explain any retention that applies to your request.
Cookies and security records
Essential secure cookies maintain Google or password sign-in sessions for up to seven days. Short-lived cookies protect the Google sign-in flow. The website also uses browser storage for preferences, drafts and navigation state. Sign-in and request-limiting records help prevent abuse; infrastructure providers may process technical request information such as IP addresses and error logs.
Retention and your choices
The service currently has no general automatic deletion schedule for account and community records. Some records have feature-specific expiry times. Deleting or withdrawing content can remove it from public view while limited audit or moderation records remain. Public experiment withdrawals retain a minimal event and count, and restricted originals may remain for audit.
You can edit your profile and use the available controls to manage your contributions. For an account-data, correction or deletion request, visit Help & support or contact the owner using the address below. We may need to verify account ownership before acting. Revoking Google access and deleting a promp2u account are separate actions.
Updates to this policy
We will update this page when the service's data practices change. The date above identifies the current version. Any new Google permissions will be requested through Google's consent flow.