Build the boundary into your integration.

Keep secrets on the server

Store API keys in a secret manager. Use separate credentials for each integration, grant only necessary assignments and permissions, and rotate keys after exposure. Never include secrets in browser code, URLs, logs or support messages.

Protect account changes

Console access requires a verified second factor. Sensitive changes require recent verification. Assign people distinct roles and review access when responsibilities change. Emergency revoke stops keys; it can interrupt every integration in the workspace.

Respect the person behind the conversation

Use stable pseudonymous identifiers. Collect only the data your product needs, provide the required AI and privacy notices, and verify authority before exporting or erasing end-user data. Education, children and companion uses require an agreement. Health use is unavailable under self-service.

Make escalation explicit

ForeverLearning does not staff per-event monitoring or contact your end users without a specific agreement. Your application needs its own appropriate human escalation path. An optional safety signal is not a guarantee that every risk has been detected.

Report a concern

For security reports, contact security@foreverlearning.ai. For abuse, contact safety@foreverlearning.ai. Include a request ID and a description; omit keys and private conversation content.

This page does not claim a certification, verified support response time or a completed production security review.