Security Overview

EdgeAmplify uses practical safeguards across account access, organization workspaces, payments, and service operations. We revisit those protections as the product and the needs of our customers evolve.

No online service can eliminate every risk. Our goal is to protect the information entrusted to EdgeAmplify while being clear about the shared role customers play in keeping their teams and content secure.

We protect web connections, account access, and user sessions with established security safeguards. Access to organization and program workspaces follows the memberships managed in EdgeAmplify, helping teams control who can see and manage their work.

Organization teams should invite only authorized people, remove access when it is no longer needed, and contact us promptly if an account or invitation may have been misused.

Payment and payout setup happen on Stripe-hosted pages. Full payment card and bank-account details are handled by Stripe rather than stored in EdgeAmplify’s application records.

Other service providers help us operate and support EdgeAmplify. The Privacy Notice explains what information may be shared when those services are used.

Organizations choose what information to keep in their workspaces and what profiles, offers, logos, images, or placements to make public. Review visibility settings before publishing and upload only information needed for the sponsorship workflow.

Do not submit student education records or sensitive student information unless EDGE Operations has agreed to that use in writing.

• Use a unique password and keep email accounts and devices secure.
• Do not forward sign-in links or leave shared devices signed in.
• Review memberships and invitations when staff roles change.
• Check public visibility before publishing content.
• Keep unnecessary sensitive information out of uploads and AI prompts.

If you believe an EdgeAmplify account, workspace, payment flow, or public page has a security issue, email contact@edgeamplify.com. Include a short description and the affected page or feature so we can investigate.

Please do not include passwords, payment details, student information, or other unnecessary sensitive data in the initial message.