Privacy Policy
Last updated: 12 October 2026
This page describes how Office Mail Portal handles information when you connect a Microsoft account. The operator should review and adapt this policy to the actual hosting, retention, and support practices before making the service available to the public.
1. Information processed
When you authorize Microsoft, the portal receives OAuth tokens and uses Microsoft Graph permissions requested by the application. The current configuration requests basic profile access (User.Read), mail read/write access (Mail.ReadWrite), mail sending permission (Mail.Send), and sign-in/offline access (openid, profile, email, and offline_access). Microsoft may display the requested permissions during consent.
The portal reads your Microsoft profile to determine the account address and, when you open the portal inbox, retrieves a limited inbox preview including message subject, sender, received time, read status, preview text, and attachment indicator. This starter build does not intentionally save message bodies or inbox results as a local mailbox database. Data may exist temporarily in server memory while a request is handled.
2. OAuth tokens and storage
Access and refresh tokens are stored as JSON files on the server, in the configured token directory. The application attempts to restrict the directory to owner-only access and token files to owner read/write access. These controls reduce risk but do not guarantee security; server administrators, backups, filesystem configuration, and hosting access are also relevant. Keep the token directory and environment file out of public web directories and never share them.
The portal refreshes access tokens when it needs to call Microsoft Graph and a refresh token is available. Microsoft may revoke tokens or require interactive sign-in again. Token storage does not guarantee a permanent Microsoft browser session.
3. Purpose and sharing
Account information and tokens are processed to authenticate the connected account and provide the portal's Microsoft 365 connection and inbox-preview features. The application code is not designed to sell account data or send message content to advertising services. Microsoft processes sign-in and Graph requests under Microsoft's own terms and privacy documentation. The hosting provider may process server and network logs according to its configuration.
4. Logs and retention
The application logs operational errors and status information and is designed not to log access-token or refresh-token values. The connected account's token file remains on the server until it is disconnected or removed by the operator. Review your web server, systemd, hosting, and backup logging/retention settings separately; this policy cannot describe settings that the operator has not configured.
5. Disconnecting and revoking access
Use the portal's Disconnect action to remove the locally saved token file and clear the current browser session. This local action does not itself guarantee that Microsoft consent or all provider-side sessions are revoked. To revoke the application's access, also review and remove the application's permissions in your Microsoft account's app permissions or your organization's Entra settings, as applicable.
6. Security
Use the portal only over HTTPS. The application uses OAuth state validation, PKCE, secure cookie settings when configured for HTTPS, and basic security response headers. No internet service can promise absolute security. Do not connect an account on a device or server you do not trust.
7. Your choices and contact
You can decline consent, disconnect the portal, or revoke access through Microsoft. For questions, data removal requests, or privacy concerns, contact the service operator at privacy@example.com.
Operator action required: replace the example contact address, confirm the data-handling statements against your actual deployment, and obtain any legal review required for your jurisdiction before publishing this service.