AdsEasy.net / Privacy policy

Privacy policy

Information processed by the website and private account management preview.

Last updated: 2026-10-25. This policy applies to AdsEasy.net at adseasy.net, operated by Razis Bedes. Contact: razisbedes5224@gmail.com.

Website visitors

Cloudflare hosts the website, executes its application code and provides the D1 database. It may process IP addresses, requested URLs, browser information, timestamps and security events to operate and protect the service. See Cloudflare’s privacy policy. We do not embed advertising pixels or third-party analytics.

Google connection data

When an invited user authorizes the preview, we obtain their Google identity, verified email, OAuth access token and, when provided, refresh token. We use these only to authenticate the user, enforce access restrictions, retrieve the Google Ads accounts they can access, and carry out their selected account and campaign creation requests.

We retrieve account IDs, names, manager relationships, status, currency and time zone to display them to the signed-in user. Account lists are not retained in the application database. When you submit a campaign, we process the settings, ad texts, landing-page URL and images you provide and send them to Google. We do not store uploaded image files or full campaign payloads in our database. Google retains created advertising assets under its own policies. This release does not retrieve campaign performance, billing details or conversion reports.

Cookies and storage

The connection flow uses Secure, HttpOnly, SameSite=Lax cookies: an authorization-state cookie lasting up to ten minutes and a session cookie lasting up to eight hours. These are necessary for sign-in and are not used for advertising. Session IDs are stored in the database as hashes. Email and access/refresh tokens are encrypted using AES-GCM before being stored in Cloudflare D1. The encryption key and OAuth client secret are stored separately in Worker secrets.

Operation records

To prevent duplicate creations and report results, we store a hashed identity identifier, operation ID, request hash, operation type, timestamp, status and a compact result (created account or campaign identifiers, names, currency, time zone or budget, and safe error codes). These records expire after 30 days and are deleted by hourly cleanup. A request fingerprint and operation ID are also kept in browser session storage for repeat-submission protection; no OAuth tokens are stored there.

Retention and deletion

Authorization attempts expire after ten minutes; sessions expire after eight hours and are rejected immediately after expiry. An hourly cleanup removes expired active database rows. Disconnecting deletes the identity’s active session and operation records immediately and requests Google token revocation. Provider backups and infrastructure records follow Cloudflare’s retention policies and may outlast active-record deletion. Session expiry alone does not revoke the Google grant.

We do not enable application request logs or intentionally log authorization codes or tokens. Infrastructure providers may process operational and security records. See deletion and access-removal instructions.

Purpose and sharing

Google data is used only for the account management functionality authorized by the user. Google receives authorization and API requests; Cloudflare processes the application and encrypted storage. We do not sell Google user data, use it for unrelated advertising, or use it to train general-purpose AI models. Use and transfer of Google API data comply with the Google API Services User Data Policy, including its Limited Use requirements.

Support messages

If you contact razisbedes5224@gmail.com, we use the information you send to answer the request and maintain necessary correspondence. Email providers process that correspondence. Please do not send passwords, tokens or client secrets. You can request deletion of correspondence; we will explain any necessary retention exceptions.

Your choices and changes

You can browse the public site without signing in. You can disconnect in the workspace or revoke access in your Google Account. Revocation does not pause existing ads. Material changes to access or processing will be disclosed before the relevant functionality is enabled.