CG Automation
PlansFeaturesHow it worksSign inSign in with Discord

Privacy Policy

Last updated: August 9, 2026

1. Introduction

This policy explains what personal information CG Tech Services LLC (“we”, “us”, “our”) collects when you use cgservices.shop and the CG Automation desktop application, why we collect it, who we share it with, and what control you have over it.

We sell software licences. We do not sell your personal information, and we do not share it for cross-context behavioural advertising.

2. Information we collect

2.1 From Discord, when you sign in

We use Discord for sign-in. When you authorize it, Discord gives us, and we store:

  • your Discord user ID;
  • your Discord username;
  • your email address, as held by Discord; and
  • your avatar reference.

We do not receive or store your Discord password. If you join our Discord server, your membership and the role matching your subscription level are visible within that server as Discord normally shows them.

2.2 Billing information

Payments are handled by Stripe. Stripe collects your payment details directly; we never receive or store your full card number, CVC, or bank credentials. What we store is a Stripe customer reference, a subscription reference, your plan level, your number of seats, and your subscription status — enough to know what you are entitled to.

2.3 Device information, from the desktop application

To enforce the number of machines your subscription covers, the desktop application computes a hardware fingerprint — a value derived from stable characteristics of the computer — and sends it to us. We store it against the seat it occupies, with the time it was bound and the time that seat was last reset.

The application does not read, scan, index, or transmit your files, documents, keystrokes, or your browsing outside the platforms you point it at. The fingerprint identifies a machine; it does not describe what you do on it. What the application does report about its own operation is described in section 2.7.

There is one deliberate exception, and it is never automatic: when you request a capture from your dashboard, the application records what is on screen in the automated browser and sends it to us so we can diagnose a problem. That is described in section 2.8. Nothing is captured unless you ask for it.

2.4 Activity records

We keep a record of licensing and billing events tied to your account — seat binding and resets, device pairing, licence activation, download authorizations, subscription changes, Discord role syncing, and referral lifecycle events — with a timestamp. These exist for support and to detect licence sharing and abuse.

2.5 Referral programme

If you participate in our optional referral programme, we store:

  • your referral code — a random identifier tied to your account, not your name, that you share with others;
  • a record of each person who signed up using your code, including their Discord ID and the status and amount of any credit earned (pending, qualified, credited, or rejected); and
  • if you were yourself referred by someone else, a reference to their code in your account record.

To detect self-referral fraud, we compare the payment card used on a referred account against cards on file for the referrer using a cryptographic fingerprint provided by Stripe. We do not store this fingerprint — it is read for the comparison and then discarded.

The referrer is not told who their referees are by name. They see a referral status row (for example "Credit clears on [date]" or "Not eligible") but not the Discord ID or any other identifier of the person who signed up. Admin users can see both sides for support purposes.

Credit is applied as a Stripe customer balance adjustment, governed by Stripe's privacy policy in addition to ours.

2.6 Technical data

Our servers and content delivery network log standard request data, including IP address, timestamp, and user agent, for security, troubleshooting, and abuse prevention. We use a session cookie to keep you signed in. We do not use advertising or third-party tracking cookies, and we do not run third-party analytics.

2.7 Automation activity, settings, and results

The desktop application reports what it does on your behalf. We collect the actions and interactions it performs on the platforms you point it at, and the results of those actions — for example that a run started and finished, what it attempted, whether it succeeded or failed, and the outcome it recorded. We also store the settings and preferences you configure in the application and on this website.

We use this to deliver features that depend on it, such as the statistics and tracking included with higher plans, to provide support and diagnose problems you report, and to detect abuse.

Credentials for third-party platforms, and any payout or identity details you enter for redemption, are held locally on your own computer. They are not transmitted to us and we cannot access them. We never receive the passwords or account details you use to sign in to those platforms.

We do not sell any of this information, and we do not share it for advertising. See section 4 for the only parties who receive it.

2.8 Problem reports and captures

When something goes wrong, you can send us a problem report from your dashboard. A report contains a description of the fault, details about the machine and the version of the application it is running, and up to the last 500 lines of the application’s own log.

You can also include a capture. A capture is a recording of the automated browser session: it can contain screenshots of what the automated browser had on screen, snapshots of the pages it was on, and records of the network requests and console output from those pages. It is limited to 100 MB.

Captures are only produced when you ask for one from your dashboard. The application does not capture anything on its own, we cannot start a capture on your machine, and there is no automatic crash reporting. Because a capture records the browser the software is driving, it may include whatever was visible in that browser at the time — including details of your account on a third-party platform, if that was on screen.

Reports and captures are used to diagnose the problem you reported. They are readable by our staff for that purpose. See section 6 for how long we keep them.

3. How we use your information

  • to create and operate your account and authenticate you;
  • to process payments, manage subscriptions, and issue invoices and receipts;
  • to determine what your subscription entitles you to and to deliver software and updates accordingly;
  • to enforce machine limits and detect licence sharing, fraud, and abuse;
  • to assign and reconcile your role in our Discord server, if you are a member;
  • to record what the application did on your behalf and the results, so we can provide the statistics and tracking your plan includes, support you, and diagnose failures;
  • to provide support and respond to you;
  • to secure the Service and investigate incidents, and to comply with legal obligations.

Where the GDPR or UK GDPR applies to you, we rely on: performance of our contract with you (account, billing, entitlement, delivery); our legitimate interests (security, abuse and fraud prevention, licence enforcement); and legal obligation (tax and accounting records).

4. Who we share it with

We share personal information only with service providers who need it to run the Service, and only for that purpose:

ProviderPurposeWhat they receive
StripePayments and subscription billingYour payment details (directly), email, customer reference
DiscordSign-in and server rolesYour Discord ID, for authentication and role assignment
Amazon Web ServicesHosting, storage, and software deliveryAll data described above, stored and processed in the U.S.

We may also disclose information where required by law or valid legal process, to enforce our Terms of Service, to protect our rights or the safety of others, or in connection with a merger, acquisition, or sale of assets — in which case we will notify you.

We do not sell your personal information and have not done so in the preceding twelve months.

5. Where your data is held

Our infrastructure runs in the United States. If you use the Service from outside the U.S., your information is transferred to and processed there, under laws that may differ from those of your country. Where required for transfers from the UK or EEA, we rely on the European Commission’s standard contractual clauses.

6. How long we keep it

  • Account and subscription records — for as long as your account exists, and afterwards only as long as needed for tax, accounting, and legal purposes.
  • Activity records — automatically deleted after 90 days.
  • Device pairing codes — short-lived, and deleted automatically shortly after they are issued or used.
  • Seat and fingerprint records — until the seat is reset, released, or the account is deleted.
  • Automation activity, results, and settings — for as long as your account exists, and deleted with it.
  • Problem reports — 90 days from the day you send one, then deleted automatically.
  • Captures — kept until we delete them. They are working material for the problem you reported, not a record we keep deliberately; you can ask us to delete one at any time and we will.

7. Security

Data is encrypted in transit and at rest. Software downloads are served only through short-lived signed links issued after we check your entitlement; there is no public path to our files. Access to production systems is restricted and secrets are held in a managed secret store.

No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects your personal information, we will notify you and any regulator as required by law.

8. Your rights

Depending on where you live, you may have the right to access a copy of your personal information, correct it, delete it, restrict or object to certain processing, request portability, and withdraw consent where processing relies on it. You will not be discriminated against for exercising any of these rights.

California residents. Under the CCPA/CPRA you may additionally request disclosure of the categories and specific pieces of personal information we have collected, the sources, the purposes, and the categories of third parties we disclose to; request deletion or correction; and opt out of sale or sharing — though, as stated, we do not sell or share your personal information. You may use an authorized agent.

UK and EEA residents. You also have the right to lodge a complaint with your local supervisory authority.

To exercise any right, email support@cgservices.shop. We will verify your request through the Discord account associated with your subscription and respond within the time the applicable law allows.

Deleting your account ends your subscription and your access to the software. We may retain a minimal record of the transaction where law requires it.

9. Children

The Service is not intended for anyone under 18, and we do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us and we will delete it.

10. Third-party services

Stripe and Discord handle your information under their own privacy policies, which we do not control. Any third-party platform you choose to use the software with is independent of us and governed by its own policies. We have no relationship with those platforms and receive nothing from them directly; what we hold is only what our own application reports, as described in section 2.7.

11. Changes to this policy

We may update this policy. If a change is material, we will give reasonable notice before it takes effect. The “last updated” date above always reflects the current version.

12. Contact

CG Tech Services LLC
support@cgservices.shop


Home · Terms of Service
CG Automation

Subscriptions renew monthly until cancelled. Cancel any time from your dashboard — sign in, open Manage subscription, and click Cancel subscription.

LegalTerms of ServicePrivacy Policy

© 2026 CG Tech Services LLC