ID Web Solutions · Eventdor LLC
Privacy Policy
This policy explains the Google Ads and administrator data handled by ID Web Solutions, why the data is needed, how it is protected, how long it is retained, and how an administrator can revoke access or request deletion.
Effective and last updated: October 23, 2026
1. Operator and application
ID Web Solutions is operated by Eventdor LLC. The private administrator workspace is also identified inside the product as 易好用内部应用. The service is restricted to administrators pre-authorized by Eventdor LLC and does not provide public registration.
Eventdor LLC728 Key Route Boulevard
Albany, CA 94706
United States
Phone: +1 510-883-4877
Email: heanrry@gmail.com
2. Google user data we access
The application requests the single OAuth scope https://www.googleapis.com/auth/adwords. It does not request access to Gmail, Google Calendar, Google Drive, Contacts, or Google Workspace documents.
| Google data | Application function | Why it is necessary |
|---|---|---|
| Google Ads manager (MCC) and customer account identifiers, account names, management relationships, currency, time zone, and status | Discover and connect the accounts an administrator is permitted to manage | Required to connect the correct account and apply its currency and time zone |
| Campaigns, ad groups, responsive text ads, keywords, budgets, bids, locations, languages, status, final URLs, tracking settings, and sitelink assets | View, create, validate, pause, resume, and manage text search advertising after administrator confirmation | Required for the application's core Google Ads management functions |
| Impressions, clicks, cost, click-through rate, average CPC, ad strength, policy status, and served text combinations | Display reports, synchronize spend, support merchant reporting, and calculate administrator-entered ROI | Required for campaign monitoring and operational reporting |
| OAuth access token, refresh token, token expiration time, and short-lived OAuth state | Maintain authorized access and perform administrator-confirmed Google Ads operations | Required for OAuth security and continuing access without repeated consent |
Administrators may also upload merchant records, keywords, ad text, revenue figures, and promotional links. These are administrator-provided business records rather than data obtained from a Google user account.
3. How we use Google user data
Google user data is used only to:
- discover manager and customer accounts the administrator can access;
- show account settings, campaign configuration, policy status, and performance reports;
- validate and perform advertising actions expressly initiated or configured by the administrator;
- apply administrator-supplied promotional-link rotation rules;
- pause or restore managed campaigns and verify remote state after interruptions; and
- support deletion, audit, troubleshooting, and recovery of these functions.
We do not use Google user data for unrelated advertising profiles, remarketing audiences, credit or lending decisions, data resale, commercial datasets, or training a general-purpose AI or machine-learning model.
5. How we protect data
- HTTPS protects data in transit.
- OAuth client credentials and tokens are encrypted in a dedicated credential vault using a separately stored master key.
- Business records are stored in an access-controlled SQLite database. We do not claim that every business field is individually encrypted.
- Administrator authentication restricts access to business interfaces and APIs.
- Encrypted backups are retained on a seven-day rolling schedule.
- Ordinary operation logs do not contain OAuth secrets, access or refresh tokens, or complete promotional links.
6. Retention periods
| Record | Retention |
|---|---|
| OAuth state | 10 minutes |
| Administrator session | 12 hours, unless ended sooner |
| Google OAuth access token | Usually about one hour; replaced when refreshed |
| Google OAuth refresh token | Until the Google identity is disconnected or deleted, or Google revokes authorization |
| Google Ads accounts, configuration, and report records | Until the corresponding Google identity is deleted from the application |
| Uploaded import preview | 24 hours |
| Operation logs | 90 days |
| Encrypted backups | Rolling seven days |
7. Authorization revocation and local data deletion
An administrator can review and delete a Google identity from Account Management in the ID Web Solutions workspace. The standard deletion process first attempts to pause managed campaigns and reads them back for confirmation. It then revokes OAuth authorization and deletes the identity's local tokens, accounts, report cache, managed campaigns, links, related operations, logs, and tasks.
If the token has already become invalid, the administrator must first confirm campaign status directly in Google Ads and then use the separately confirmed local-only deletion option. That option removes local data but cannot change data on Google Ads.
Administrators can also revoke authorization in their Google Account connections. Revoking Google authorization prevents new API access, but it does not by itself delete local records and does not automatically pause campaigns that may still be running on Google. Contact heanrry@gmail.com for assistance with access, correction, or deletion.
Deleted records may remain in encrypted rolling backups for up to seven additional days and then expire naturally.
8. Google API Services User Data Policy and prohibited uses
ID Web Solutions' use and transfer to any other application of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
The application manages Google Ads accounts and text search advertising. It does not generate, edit, analyze, or distribute images or videos; does not provide generative AI features; and does not use Google APIs to create, process, promote, or distribute AI-generated non-consensual intimate imagery (AI NCII).
10. Contact
Questions or requests about this policy or Google user data may be sent to heanrry@gmail.com or mailed to Eventdor LLC at the address in Section 1.