1. Who operates EasyHelp
EasyHelp at easyhelpsupport.com is operated by STYNGT, United States. This policy covers this deployment’s public support pages, staff workspace, connected mailboxes, support records, and optional integrations.
Questions about privacy, access, correction, or deletion can be sent to styngt@easyhelpsupport.com. If you are contacting another business through a mailbox managed in EasyHelp, that business may also have responsibilities for the information it supplies and the requests it handles.
2. Information we access and collect
- Connected mailbox information: the authorized mailbox’s email address, provider identifiers, OAuth access and refresh tokens, and token-expiration information.
- Email and support content: sender and recipient addresses, names supplied in messages, subjects, timestamps, message bodies, attachments, thread identifiers, and message status or labels available to the integration.
- Customer-service records: contact details, order and product information, warranty or complaint information, uploaded photos and videos, agent notes, tags, replies, and support activity.
- Workspace and technical information: staff account and role information, authentication sessions, request logs, IP addresses, timestamps, processing errors, and task or delivery records.
Information can come from a mailbox authorized by its account holder, a support request or upload, an authorized staff member, an imported record, or a configured business integration.
3. Google authorization and mailbox access
Google OAuth connects a Gmail mailbox to the staff workspace; it is separate from the staff username-and-password login. The current integration requests openid, email, and https://mail.google.com/, including offline access so the server can refresh access after the initial authorization.
The full-mail permission is broad: Google describes it as permitting reading, composing, sending, and permanently deleting Gmail email. It is not a read-only permission. The reviewed integration uses mailbox access to synchronize and display support messages, retrieve message and attachment information, send replies, and update message state such as read status. A permission’s capability should not be confused with a promise that every possible operation is performed.
You choose the account and permissions on Google’s authorization screen. You can decline authorization or remove EasyHelp’s access through Google Account connections. Revocation stops future authorized access once the provider rejects the tokens; it does not itself erase copies already stored in EasyHelp.
Google’s Gmail scope descriptions explain the permission’s extent.
4. How support and Google data are used
The implemented workflows use these records to bring customer requests into a shared inbox, match messages to tickets and orders, show conversation history, assign status and tags, prepare or send replies, manage attachments, and report on customer-service activity.
Optional configured workflows can generate drafts and summaries, assist with ticket questions or classification, synchronize selected complaint or inventory records, and schedule follow-up communications. Enabled automation can act without separate approval of each message; authorized operators are responsible for its settings. Not every integration or automation is enabled in every deployment.
The reviewed EasyHelp workflows do not include selling mailbox data, advertising targeting, or an in-application model-training pipeline. This observation does not establish the data-use practices of external service providers.
5. AI processing and its current limits
When configured and used, AI features send selected support context to DeepSeek’s API. Depending on the feature, this can include email addresses, subjects, message text, text derived from attachments, order or product details, agent questions, and relevant knowledge-base context. The implementation may shorten context, but it does not consistently anonymize it. Google-sourced email can therefore be included when a connected Gmail ticket is used with an AI feature.
The provider processes the submitted prompt and returns a result for the requested support feature. Drafts, summaries, or other generated content can become part of stored support records when saved or used. AI output can be inaccurate and needs appropriate operator review.
Not yet confirmed: STYNGT has not confirmed this API account’s provider retention period, training restrictions, deletion arrangements, or processing regions. This notice does not promise zero retention or that the provider never uses submitted data for training. These matters must be resolved before authorizing processing that depends on such assurances. See DeepSeek’s published privacy information; it is not a substitute for confirming the applicable API-account terms.
7. Where information is stored
Support records and message-related data are stored in a server-side PostgreSQL database and local application files. Attachments and media use server storage. Redis queues, processing caches, task histories, exports, and migration or recovery snapshots may hold additional copies or metadata.
OAuth credentials are stored in server-side configuration records. The application does not implement field-level encryption for all of these credential files. Restricted server access is therefore an important part of their protection.
Staff browsers also use local storage and IndexedDB for authentication tokens, interface preferences, and cached ticket or conversation content. Signing out removes the login token but does not necessarily remove every locally cached record. Clear the site’s browser storage to remove those local copies on a shared device.
8. Retention and deletion
A fixed retention period has not yet been established for all support messages, ticket records, attachments, operational logs, exports, or backups. Some caches and operational records have technical limits, but these do not amount to a complete retention or backup-erasure policy. No exact all-systems deletion deadline is promised here.
Removing a mailbox connection removes its active account credentials from the application’s mailbox-account record and retains a minimal deletion marker. The reviewed disconnect flow does not automatically erase historical messages, tickets, attachments, browser caches, or backup copies, and it does not automatically revoke the app in Google Account settings. To revoke access at Google, use the Google Account connections page.
For access, a copy, correction, or deletion, email styngt@easyhelpsupport.com with the relevant account or ticket identifier. We will review your request and verify that you are entitled to make it. Do not send passwords or OAuth tokens. Complete deletion may require manual work across databases, files, integrations, and retained copies; its procedure and backup-completion timing remain to be confirmed. Copies in an original mailbox, a recipient’s mailbox, or another independently operated system require separate handling.
9. Security measures and limits
The deployed website uses HTTPS. The workspace uses staff authentication and role-based permissions; staff passwords are salted and hashed. Sensitive configuration is kept server-side with restricted file permissions, and saved service secrets are not returned in plaintext by the service-settings response. Private-media access includes authorization or signed-link checks.
These are implemented controls, not a guarantee against every incident. Application-level encryption of every stored record or backup, a particular security certification, and an independent security assessment have not been established by this review.
10. Google data-use requirements
Use of Google APIs is subject to the Google API Services User Data Policy, including Limited Use requirements, and the applicable Google Workspace policies. Google-sourced data must not be used to train general-purpose AI models. The reviewed application has no such training pipeline; third-party API retention and training arrangements still require confirmation.
This policy describes observed application behavior and the unresolved items below. It does not assert that Google has verified EasyHelp or that an outstanding provider-policy review has been completed.
11. Items awaiting confirmation
STYNGT has identified the following open items. They are not completed commitments:
- Retention periods for support data, files, logs, and exports.
- Backup retention, expiry, and the time required to finish a deletion across retained copies.
- A documented complete-deletion procedure and handling of any applicable retention obligations.
- The AI provider’s applicable API-account agreement, training restrictions, retention, deletion process, and processing locations.
- The full infrastructure-provider list and the regions in which hosted and third-party processing takes place.
Questions about these items can be sent to styngt@easyhelpsupport.com. Material changes to the practices described here will require an updated notice and any further notice or authorization required for the changed use.