Account access / Google user data
How account email handles information.
The ADMIN FRAMEWORK site administrator manages the workspace’s account-mail setup. Support and privacy contact: nhyunipc@gmail.com.
Purpose and operator
ADMIN FRAMEWORK is a procurement workspace with controlled access to sales, inventory, product records, reports and promotional support. The site administrator manages account access and the optional Gmail sending connection.
The workspace processes account names, usernames, email addresses, password hashes, permissions, sessions and security/audit records to provide and protect account access. Connection/IP-derived counters help limit sign-in and account-help requests.
This information site has no forms, sign-in flow, analytics script or application API connection. When viewed online, its hosting service receives the request information needed to serve the page, such as an IP address, requested URL and browser headers. This draft does not assert that optional hosting analytics or account-mail features are enabled.
Google access and outgoing messages
When Gmail account email is enabled, the administrator authorizes the sending mailbox. Workspace users do not connect their Google accounts through this integration. It is separate from website sign-in.
https://www.googleapis.com/auth/gmail.send
The Gmail backend accepts this exact send-only scope. It sends account-verification and password-reset messages; it does not read or search mailbox messages, contacts or Drive.
| Information | Purpose and handling |
|---|---|
| Sending mailbox and OAuth credentials | Identifies and authorizes the administrator’s sender. The backend obtains an access token from Google and uses it for sending. |
| Recipient email and account name | Addresses and personalizes the verification or password-reset message. |
| Subject, message and one-time site link | Sends the account message through Google. Google and the recipient’s mail service process the email. No password is included. |
| Provider acceptance response | Confirms whether Google accepted the request. A staging-only diagnostic can retain a bounded acceptance ID and owner-match flags. Acceptance is not proof of inbox delivery. |
Neither a verification request nor a reset request grants business permissions. Email recovery preserves enrolled owner MFA. The application does not automatically resend an uncertain message.
Storage, access and protection
The Cloudflare backend stores account records, permissions, security/audit records and verification/reset token hashes. The token record also holds its recipient email and expiry. Account audit records can include account identifiers and email addresses.
Passwords use salted PBKDF2 hashes. Normal sign-in cookies are marked HttpOnly, Secure and SameSite=Lax. Owner authenticator seeds are encrypted in the application database; recovery codes are stored as hashes.
The Gmail backend reads sender credentials from Worker configuration. The intended setup installs them as private Worker secrets, outside public pages, browser storage and account tables. The access-token cache is held only in Worker memory, for at most five minutes. This draft does not certify the live deployment’s configuration.
Application roles and assigned permissions control business access. Owner-only administration and authorized system backups can include sensitive account/security/audit records. A backup copy must be protected separately; the static information site provides no account-data download or credential-entry form.
Business records and browser storage
Authorized users can enter operational records, which may include customer-related information. The workspace can hold data in its cloud stores and keep browser preferences and offline transaction drafts on the device. A shared device therefore needs the same care as other business records.
Optional configured backups or mirrors can create additional copies of operational data. Optional product-AI suggestions receive product name, model, category, description and SKU fields; that feature does not obtain Gmail inbox messages. The actual enabled destinations and integrations depend on administrator configuration, which this draft does not certify.
Customer-name redaction is an optional application setting. It preserves transaction and audit facts and is not general account deletion. This notice does not introduce a fixed business-data retention period or promise that every backup copy is erased with a source record.
Link validity, retention and requests
Verification links are valid for two days and password-reset links for one hour. The code checks expiry and includes maintenance cleanup of expired tokens and old account-help requests. Link expiry does not set a deletion date for accounts, audit records, backups or email held by mail providers.
No universal account/audit retention period or general self-service account-deletion process is established by the current account flow. Retention and handling of operational records must follow the administrator’s approved practices; this review draft does not invent those practices or a legal guarantee.
For an account-data question or request, contact nhyunipc@gmail.com. Do not include passwords, MFA codes, private sender credentials or verification/reset links. This information site does not collect or automatically process data requests.
The administrator can withdraw or replace the Gmail authorization and remove the deployment’s sender configuration. Gmail sends require valid sender configuration and authorization. Removing or revoking these does not itself delete account records or copies of messages already processed by Google or a recipient’s provider.