Who this policy covers
Maximizing Potential is a nonprofit organization that helps people develop and sustain charitable initiatives addressing community needs. This policy explains how we handle personal information through our website, participant accounts, event and project tools, and applications that link to this policy.
Some features described here, including optional social sign-in and LinkedIn Page management, depend on availability and separate authorization. Describing a feature here does not mean it is currently enabled. Our Donor Bill of Rights and Privacy Policy provides additional commitments for donor information received online and offline.
Information we collect and why
- Messages and inquiries. When you contact us, we receive your name, email address, message, and any other information you choose to provide. We use it to respond and manage the relationship or request.
- Accounts and sign-in. We use your email address, display name, verification status, and sign-in records to identify you, secure your account, and connect it to your projects. If you set a password, we store a salted password hash, not the password itself.
- Event registration. Registration is separate from a website account. When you register through Luma or another identified event service, we receive the registration information that service makes available to us, such as your name, email address, registration status, and answers you submit. We use it to organize the event and communicate with participants. The registration form identifies the information requested.
- Projects and judging. We receive project descriptions, team names, participant names supplied for public credit, contact details, links, uploaded app files, submission approvals, and related event records. Authorized judges and organizers provide scores, feedback, and event decisions. We use these records to manage submissions, host approved projects, conduct judging, and maintain event records.
- Technical information. Our website and infrastructure providers process information such as IP addresses, browser and device information, requested pages, timestamps, and error or security events to deliver the service, troubleshoot problems, and prevent abuse. Sign-in protections may use account, email, or network information to limit repeated attempts.
Please provide only information needed for the feature or request. Do not put passwords, access tokens, or sensitive personal information in messages, public project descriptions, or uploaded app files.
LinkedIn and other connected platforms
Optional visitor sign-in
When available, you can choose to sign in with LinkedIn, Google, or GitHub. After you authorize the connection, we receive basic identity information, which can include a provider account identifier, name, email address, email-verification status, and basic profile information. We use the identity and email information needed to create or recognize your account and link your projects to it. We store the provider name and account identifier for future sign-ins.
We receive this information each time you use provider sign-in or link a provider account. The provider’s response may also include a profile-picture URL or locale; we do not retain those fields for participant sign-in. We do not refresh LinkedIn profile information on a background schedule.
LinkedIn and Google sign-in request basic identity, profile, and email permissions. GitHub sign-in uses basic account and email information. Participant sign-in does not request access to your LinkedIn connections, private messages, mailbox, repositories, or permission to publish posts. We do not receive your provider password. Provider sign-in tokens are used to complete authentication and are not stored in your participant account.
LinkedIn Page management
We plan to use a separate, administrator-authorized connection to manage Maximizing Potential’s LinkedIn Page and posts. This feature is not part of visitor sign-in. Before enabling it, we will explain the permissions and information needed for the available functions and update this policy if necessary.
For Page publishing, the intended information includes the authorizing administrator’s account identifier and Page permissions, the Page identifier, post text and media supplied for publication, publication status, and the authorization credentials needed to carry out approved actions. The purpose is to prepare, publish, and manage our organization’s posts. An administrator must separately authorize this access. Signing in as a participant does not authorize posting to a personal profile or managing a Page.
Your control over connections
You can withdraw a platform’s access through its connected-app settings and contact us to remove information held by Maximizing Potential. Revoking platform access stops future authorized access; it does not by itself delete an existing website account or information already received. For LinkedIn data, we will delete API data and any stored authorization credentials immediately upon a verified deletion request or closure of the associated account, except where retention is required by law or a government authority. The privacy-request instructions below explain how to reach us.
Each platform handles its own authorization screens and services under its own privacy policy: LinkedIn, Google, and GitHub.
Public projects and assistant connections
Project drafts are not publicly listed before your approval. New submissions require a public summary: project title, short description, challenge, team name, and the contributor names or aliases you approve. Review the public summary and obtain your teammates’ permission before submitting. Contact us before publication if you need a privacy accommodation.
Longer descriptions, community-benefit and technology details, tags, dependencies, and demo, repository, or video links remain available to authorized judges and organizers. They become public only if you choose to share the additional details. Public demo hosting is a separate choice: approving it makes the listed app files accessible to visitors and allows an automatically generated screenshot of that public demo. Account and contact email fields and individual judge scorecards are excluded from public pages. Information you put inside a public summary, app file, or linked service can still be visible.
We record the User Agreement and Terms of Service versions, approval time, and permissions for each new submission. Previously approved submissions keep their existing permissions; this update does not expand them. Promotion beyond ordinary event results and sharing public project-page links requires separate permission.
During judging, withdrawing an entry removes its public page and hosted app and ends its judging eligibility. Once results are finalized or awards are published, removing it from the showcase hides the page, app, and screenshot without changing an earned award. Ordinary event results may retain the project title and approved credit without a link to the removed project. Contact us about personal information in these records. Limited private approvals and event or judging records may remain, and removal does not close your account. Other people or search engines may retain copies of material that was public.
Connecting a coding assistant, such as Claude Code or Codex, requires separate approval. The connection screen describes its access, such as reading your profile and event details, preparing drafts, uploading app files, or checking submission status. Your assistant cannot approve publication for you. You can revoke assistant connections through your account. The assistant provider handles information it receives under its own terms and privacy policy.
Retention and security
We retain information for the purposes described in this policy, including maintaining accounts, operating events, preserving approved project and judging records, resolving disputes, preventing abuse, and meeting legal or recordkeeping obligations. Retention depends on the record and purpose; there is no single retention period for all information. Temporary codes and sign-in transactions expire, and expired authentication records and certain unused drafts are periodically removed.
You can ask us to delete information using the contact details below. We will review the request, delete information that is no longer needed, and explain any records we must retain. The more specific LinkedIn deletion commitment above applies to LinkedIn API data and authorization credentials. Copies retained by independent platforms, other users, or search engines are outside our control.
We use access controls, encrypted connections, password hashing, and other safeguards appropriate to the service. No system can guarantee absolute security. Our service providers may process information in the United States and other countries where they operate.
Access, corrections, deletion, and other choices
You can close your participant account and remove its connected sign-in information through our account-deletion page. It explains the consequences, requires a recent sign-in or your current password, and asks you to confirm before deleting. For a narrower request, including removing LinkedIn information while keeping independently supplied account or project information, contact us.
To ask about information we hold, request access or a correction, close an account, request deletion, withdraw a connection, or change communication preferences, email maximizing.potential.admin@gmail.com. Please identify the account or service involved and what you would like us to do. For LinkedIn-related requests, mention LinkedIn and the connected account or Page. Do not send passwords, sign-in codes, or access tokens.
We may ask for information reasonably needed to verify that the request concerns your account or that you are authorized to act for someone else. We will respond in accordance with applicable law and platform requirements and explain any limits on fulfilling a request. Rights available under law may vary with your location and circumstances.
You can ask to stop promotional or fundraising messages using an unsubscribe option where provided or by emailing us. We may still need to send messages about your account, an event you registered for, a request you made, or legal obligations. You may also decline optional platform connections and use another available sign-in method.
Children’s information
Our online account and app-connection services are not directed to children under 13, and we do not knowingly collect their personal information through these services. A parent or guardian who believes a child under 13 has provided information should contact us so we can investigate and delete it as appropriate. Event-specific age and participation requirements are provided with the event.
Changes and contact
We will post updates to this policy on this page and change the date at the top. For material changes, we will provide a prominent website notice or contact affected account holders when appropriate. If a new data use requires consent, we will request it before beginning that use.
For privacy questions or requests, contact Josh Williams, President, Maximizing Potential, at maximizing.potential.admin@gmail.com.