Privacy Policy

Mailbox authorization

Gmail and Microsoft mailboxes are connected only after the mailbox owner completes the provider’s OAuth consent process. Account Workspace Mail Hub never receives or stores the normal Gmail or Microsoft password. Yahoo/Ymail uses a Yahoo-generated app password and does not accept the normal Yahoo password.

Mail data processed

The Mailbox Hub requests messages likely to be related to LinkedIn, including verification codes, password resets, email confirmations, security alerts, and LinkedIn notifications. It does not intentionally synchronize unrelated personal or business email. Candidate message headers and content are processed to confirm the sender, classify the message, detect a verification code, and present the message to authorized workspace users.

Data stored

The application may store the mailbox address, provider account identifier, encrypted OAuth tokens or encrypted Yahoo app password, granted scopes, connection and synchronization status, LinkedIn-related sender details, subject, message snippet, encrypted message text, encrypted verification code, timestamps, account-mailbox mappings, and audit records. Attachments are not downloaded or stored by default.

Retention

Administrators configure the LinkedIn-message and verification-code retention periods. The default is 30 days for LinkedIn messages and 24 hours for verification codes. Expired codes and messages are removed automatically. Mailbox credentials remain until authorization is revoked, expires, or the mailbox is disconnected.

Team access and auditing

Workspace access is limited to named users with Owner, Administrator, Operator, or Viewer roles. Code access and mailbox-management permissions depend on role. The application records security-relevant events such as connection changes, synchronization, message actions, and verification-code copying.

Use and sharing

Mail data is used only to operate the authorized Mailbox Hub and related LinkedIn login-support workflow. It is not sold, used for advertising, or shared with unrelated third parties. Hosting and identity providers process data only as required to deliver and secure their services.

Security

Provider credentials, stored message bodies, and verification codes are encrypted with the installation key. The application uses authenticated access, CSRF protection, role permissions, sender-domain checks, sender-authentication validation before revealing codes, rate controls, and audit logs.

Deletion and revocation

An authorized administrator can disconnect a mailbox in Mailbox Hub. Provider access can also be revoked from the relevant Google, Microsoft, or Yahoo account-security settings. See Mail Data Deletion for details.

Contact

Privacy questions may be sent to rizingtech@gmail.com.

Google API data and Limited Use

Account Workspace Mail Hub’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Gmail data is used only to provide the user-authorized Mail Hub functionality and is not used for advertising, profiling, sale or unrelated purposes.

The Google permission requested is gmail.readonly. It is used to read the subject and body of authorized messages so the application can identify verification codes, password resets, confirmations and security alerts. This permission does not allow Account Workspace Mail Hub to send, modify or delete Gmail messages.