Security & responsible use
OfficeHelper is designed to keep public productivity resources separate from private credentials and protected integrations. This page explains the practical security boundaries users should understand.
Use the official sign-in flow and keep your account credentials private. Do not share passwords, recovery codes or authentication tokens.
Public pages do not need private provider secrets. Server-side integrations should keep keys and tokens in secure environment or secret storage.
When an integration is configured, authorization should occur through the provider's official consent flow. Never paste a provider password or private API secret into a public form.
Microsoft, Google, OpenAI and other providers have their own security controls and terms. Verify sensitive actions against official documentation.
Safe-use checklist
- Use strong, unique passwords and enable multi-factor authentication where available.
- Review permissions before authorizing an external integration.
- Never publish API keys, access tokens, service-role keys or recovery codes in client-side code.
- Keep browsers, devices and installed OfficeHelper/PWA versions up to date.
- For sensitive or consequential work, verify information with the relevant official source.
Report a security concern
If you discover a security issue affecting OfficeHelper, use the official Contact OfficeHelper page and provide enough detail to reproduce the issue without including passwords, tokens or other secrets.