Last updated 4 October 2026
Information we collect
The public website can be read without creating an account. When you request Partner Portal access, we collect your name, email address, reason for requesting access and confirmation that you consent to the request being reviewed.
Approved partners have an account in Amazon Cognito. Account records include a name, email address, account status and authorization groups. If you choose Continue with Google, Google provides an account identifier, name, email address and whether that email is verified. We use this information only to link Google sign-in to an existing, approved account. Google sign-in does not create public self-service accounts.
Security and delivery logs can include an IP address, request time, requested route, response status and browser or device information. These logs help us prevent abuse, investigate errors and protect the website and private content.
How we use information
- Review, approve or reject Partner Portal access requests.
- Create, authenticate, secure and administer approved accounts.
- Deliver private updates to authorized partners.
- Respond to account, privacy and security enquiries.
- Detect abuse and maintain the reliability of our services.
We do not sell personal information or use it for third-party advertising.
Services that process information
We use Amazon Web Services to host the website, store access requests, authenticate users, deliver administrator notifications and retain operational logs. If you choose Google sign-in, Google processes the authentication under your Google account settings and Google's privacy terms. Private updates can contain YouTube videos embedded using YouTube's privacy-enhanced domain; Google can receive request information when you load or play an embedded video. The public Prayer page embeds an interactive map supplied by Joshua Project. Joshua Project can receive standard browser request information when that map loads.
Storage, sessions and security
Access requests and identity records are stored in AWS. Portal access is authorized on the server for every protected request. Browser access and refresh tokens are held in memory rather than persistent browser storage. Temporary sign-in state is kept in session storage and is cleared during the sign-in flow or when you sign out. Cognito and Google can set their own secure sign-in cookies on their domains.
Retention
Partner access-request records are scheduled for deletion after 365 days. Approved account records are retained while access is active and for as long as reasonably needed for security and administration. Operational logs are retained for limited periods configured for the relevant AWS service. Some deletion can be delayed by backups, legal obligations or active security investigations.
Your choices
You can choose password-based sign-in instead of Google sign-in. You can also ask us to access, correct or delete personal information, or withdraw a pending access request. Some records may need to be retained where required for security, legal or administrative reasons.
Contact
For privacy, account-data or Google sign-in enquiries, email maximizedpotential@gmail.com.
Changes to this notice
We may update this notice when the website, authentication process or legal requirements change. The date at the top identifies the latest version.