Privacy Notice

Remove local licensing records

GG_rand Privacy Notice
Notice version: 2026-11-17-publisher-pilot-1
Effective from: 17 November 2026, upon publication for the publisher-only pilot

Current availability: the online service admits only Tamitech's designated
publisher test account for internal activation testing. Outside registration
and paid sales are closed. Public visitors can read these notices; connection
and security processing still applies to visits and attempted requests. The
service checks a hash of the normalised sign-in email against the designated
account. Other submitted email addresses are not stored or sent sign-in mail.

GG_rand processes project content locally. Project content and information about
your work within REAPER are not automatically transmitted to Tamitech. We process
the account, device, security and support information described in this notice
to provide licensing, protect the service and respond to enquiries.

GG_rand contains no advertising and does not collect product-usage analytics.

Normal licence checks are performed locally. Online activation and account
operations use the service described below. Standalone Norm Gain does not
contact the licensing service or require an account. Feedback is optional.

1. Who is responsible and what this notice covers

Tamitech Automation Oy, Finland, is the controller: we decide why and how
personal data is used for GG_rand licensing and our customer support.

Business ID: 2554637-6
Postal address: Kangasrousku 14, 04500 Kellokoski, FINLAND
Privacy and support email: eero.halme@tamitech.fi
Licensing service: https://license.tamitech.fi

This notice explains how GG_rand handles information locally and how we process
personal data for licensing, customer support and feedback. Other websites,
REAPER and third-party plug-ins have their own data practices.

Paid checkout is not currently available. Before paid sales open, we will explain
the seller/payment provider, purchase information we receive and the relevant
accounting retention requirements. GG_rand does not collect payment-card details.
The paid-licence provisions below explain how licensing data is handled when a
paid entitlement exists; they do not announce that sales have opened.

2. What information we process

Account and contact information: your email address, email-verification time,
a random account identifier, and support messages or attachments you send us.
For a beta invitation, Tamitech may enter an address supplied by you or an
authorised contact at your organisation. When someone else supplies your address,
we identify the supplying organisation and, where known, the contact in the
invitation and provide this notice with it. We provide this information within
one month of obtaining your address, and earlier if our first communication or
disclosure occurs first, unless an applicable legal exception applies. You can
also contact us for further information about the source.

Licence information: trial, beta or paid entitlement, licensed major version,
start and expiry dates, trial history, invitations, renewals, activations,
certificate deliveries and computer-retirement records.

Computer information: a device digest, generated computer label, random
registration identifier and registration time. The digest is calculated locally
from the Windows firmware UUID or the Mac's IOPlatformUUID. The request sends
the digest, not the raw identifier. It remains linkable to your account and is
not anonymous. Current builds use a label such as "GG_rand computer 12ab34cd",
derived from the existing digest, instead of reading your OS computer name.
The label helps distinguish registrations; it is not the identifier used to
bind the licence. It is not separately editable in GG_rand. Older builds can
send their OS computer name, which may contain a person's name; use the supplied
pilot build for this test. These records do not include a list of your files,
installed plug-ins or projects.

Security and delivery information: request identifiers and times, hashed sign-in,
session and redemption tokens, records of licence delivery and clock-verification
requests, request-limit counters and records of licence-administration actions
by Tamitech, such as issuing or renewing licences and deleting accounts. Hosting
providers receive your IP address and ordinary connection information when you
visit the website or make an online request. The application uses a hash of the IP address for rate
limiting; the hosting provider still receives the original address. Email
providers process recipient addresses, message contents and delivery/security
information. Sections 5 and 6 explain their roles and retention.

Local information: signed authorisations, device binding, integrity and time
records used to validate licences and detect evaluation-clock rollback. Windows
protects activation records in the current user's Registry storage. GG_rand keeps
an additional clock-integrity record in Windows Credential Manager. On Mac,
licences and a clock witness are stored in the current user's local Keychain;
additional clock and lock files are in the user's Application Support directory.
GG_rand does not request iCloud Keychain synchronisation for these entries.
These clock records support time-limited trial and beta access; paid perpetual
licences do not depend on a trusted evaluation clock. Setup also keeps local
paths, hashes, backups and recovery journals; paths may contain your OS username.
These setup records are not automatically uploaded to the service.

The paid Offline Recovery License contains a licence identifier, purchased major
version, issuance details and a signature. It contains no email address, computer
name or device digest. Its identifier remains linkable to the licensing account.
Downloading it uses your authenticated account. Importing a saved recovery file
is local: it does not report the import or register a replacement computer with us.

GG_rand does not automatically transmit audio or MIDI data, REAPER project files,
plug-in settings, rendered audio, or records of project editing and audition
decisions, including parameter adjustments and comparison votes. If you choose
to send such information for support, we process it as support correspondence.
Remove information we do not need, other people's personal data and sign-in or
recovery secrets before sending a support example.

3. Why we use information and the legal bases

Providing an individual's requested account, activation, licence delivery,
recovery download, device management and necessary support: performance of the
licensing contract or steps requested before entering it (GDPR Article 6(1)(b)).

Administering access for an organisation's staff or contractors: our and the
organisation's legitimate interests in providing the access it requested
(Article 6(1)(f)). The organisation's contract does not make every employee a
party to it. We do not use these records to monitor staff productivity.

Protecting accounts and the service: our legitimate interests in preventing
account takeover, reuse of authentication requests, email abuse and use beyond
the agreed licence limits (Article 6(1)(f)). We limit the information collected,
apply the retention policy below and provide human review of disputed refusals.

Answering general enquiries and handling feedback you choose to send: our
legitimate interests in responding and improving GG_rand (Article 6(1)(f)), or
contract necessity where support is needed to provide your licence. Feedback
is optional.

Handling privacy requests and specific legal duties: compliance with the
applicable legal obligation (Article 6(1)(c)). Where necessary to establish,
exercise or defend legal claims, we rely on the relevant legitimate interest
and restrict the records to that purpose. This does not permit keeping all
account information indefinitely.

Accepting the License Agreement is not consent to this Privacy Notice. No
marketing permission is bundled with activation. If optional consent-based
processing is introduced, its purpose and withdrawal route will be explained
separately before it starts.

These GDPR legal bases concern processing personal data. They do not replace
any consent required for storing or accessing information on your device.

4. Connections, device storage and cookies

When the extension starts, its licensing component reads the Windows firmware
identifier or Mac platform identifier locally and checks saved records. This can happen
before you start an online activation. Local access does not itself send data
to Tamitech. An online activation or clock-verification request transmits the
device digest and generated computer label described in section 2.

Saved licence records let GG_rand validate access without a routine server
connection. Time records help check the stated trial or beta period without
continuous online verification. Local records remain until removed; they are
not erased automatically when a trial expires or GG_rand is uninstalled.
Section 7 explains how to remove them and the effect on activation.
The current implementation can continue checking and updating local clock
records after an evaluation expires or a paid licence is imported, although
paid access does not depend on them.

The installed extension does not periodically contact the server to validate a
licence. Online activation, renewal, account/device management and clock repair
start with a user action. Visiting the account website also makes a connection.

The website uses two first-party security cookies:

- __Host-gg-confirm: protects email-link confirmation; up to 15 minutes.
- __Host-gg-session: keeps you signed in and protects account actions; up to one
  hour. Signing out removes that session and clears its cookie.

Both are Secure, HttpOnly and SameSite=Lax. Blocking them prevents browser
sign-in from working. They are used for sign-in and security, not advertising.

Email sign-in links expire after 15 minutes. Activation requests normally expire
after ten minutes, with a five-minute retry window after first delivery. These
are validity periods; related records and backups have separate deletion periods.

The account pages use no analytics cookies, tracking pixels or third-party
scripts. Sign-in email is plain text, with open/click tracking disabled.
Provider security screening and delivery records are separate from tracking.

5. Who receives information and where it is processed

Authorised Tamitech personnel and providers may access information needed for
licensing, support, security or recovery. Our selected providers are:

Domainhotelli (Planeetta Internet Oy), Finland: the company support/privacy
mailbox, including correspondence, attachments and delivery information. Its
published processing agreement describes hosted customer data as processing on
our behalf. It describes data centres as principally in Finland but permits
other locations under its transfer provisions. We do not promise Finland-only
or EEA-only processing. This description relies on its published documentation.
Terms and processing agreement: https://www.domainhotelli.fi/kayttoehdot/

Cloudflare, Inc., United States: Workers hosting, connection/security processing
and the D1 licensing database. The database uses EU jurisdiction, but Workers
access and other provider processing can take place internationally.
Processing agreement: https://www.cloudflare.com/cloudflare-customer-dpa/
Privacy policy: https://www.cloudflare.com/privacypolicy/
Subprocessors: https://www.cloudflare.com/gdpr/subprocessors/

Plus Five Five, Inc. (Resend), United States: transactional sign-in email. The
sending route is Ireland, but Resend stores customer data in the United States.
Its providers may screen messages for spam or phishing. We do not use Resend's
optional AI email-editing features to prepare these messages.
Processing agreement: https://resend.com/legal/dpa
Privacy policy: https://resend.com/legal/privacy-policy
Subprocessors: https://resend.com/legal/subprocessors

GitHub, Inc., United States: the private automated database-backup job. The
runner temporarily handles readable exports, encrypts them, uploads them, then
downloads and decrypts a copy to verify it. The workflow removes its staging
files. Encryption in backup storage does not mean that GitHub never processes
readable data. Authorised local recovery also requires decryption.
Published data-protection terms:
https://github.com/customer-terms/github-data-protection-agreement
Subprocessors:
https://docs.github.com/en/site-policy/privacy-policies/github-subprocessors

Backblaze, Inc., United States: encrypted database-backup storage in our private
B2 bucket in EU Central (Amsterdam). The storage region does not determine the
location of all provider account, support or service processing.
Terms and processing agreement:
https://www.backblaze.com/company/policy/terms-of-service
Privacy policy: https://www.backblaze.com/company/policy/privacy

The Cloudflare, Resend and Backblaze processing agreements provide
Standard Contractual Clauses for applicable transfers outside the EEA.
GitHub's published DPA contains transfer terms for services within its scope.
Domainhotelli's published transfer provisions are described separately above.
Choosing EU storage does not mean that all processing stays in the EEA. You can
use the links above or contact us for a copy or explanation of the safeguards
relevant to your information, subject to necessary redactions.

Providers also act as independent controllers for certain account, security or
service information under their own policies. We may disclose necessary records
to authorities or advisers where required by law or necessary for legal claims,
with applicable safeguards. We do not sell licensing data or provide it for
targeted advertising.

6. How long information is kept

During the publisher-only pilot, scheduled account/diagnostic cleanup is
disabled and encrypted-backup expiry runs in preview mode without deleting
backups. The periods below are the selected retention policy; those automatic
removals are not yet operating. Test records and backups can remain until the
operator removes them or enables the reviewed cleanup. Sign-in and activation
request validity still expires as stated. Outside registration remains closed
until retention operation and the other launch requirements are completed.

We retain information for the periods and purposes described below. This table
summarises the main periods; the explanations below describe the starting points,
exceptions and the difference between deletion eligibility and actual removal.

Information                         | Retention period or criterion
------------------------------------|---------------------------------------
Active accounts and licences        | While needed to provide/support access
Expired trial/beta-only accounts     | Eligible 90 days after latest expiry
Accounts with no entitlement         | Eligible 90 days after verification
Accepted, unstarted beta accounts    | Eligible 90 days after acceptance
Unaccepted invitations              | Eligible 90 days after invitation expiry
Licence/clock-request diagnostics    | Normally eligible after 90 days
Routine administration records      | Normally eligible after 90 days
Expired sign-in/session/rate records | Next successful applicable cleanup
Support correspondence              | 12 months after final resolution
Encrypted database backups          | 90 days
D1 recovery history                 | 7 days on the selected plan
Resend email/logs; backups           | 30 days; 7 days on the selected plan
Domainhotelli backups; security logs | 2 weeks; 100 days (not all mail logs)
Local licensing records             | Until you remove them

Accounts and licences

We keep account and active entitlement records while needed to provide and
support the licence. A perpetual paid licence can require long-term ownership
evidence; this does not justify keeping every diagnostic or retired-device
record for the same period. Paid accounts are excluded from automatic free-
account cleanup.

Trial/beta-only accounts become eligible for deletion 90 days after the latest
expiry of their access. An account with no entitlement uses 90 days after initial
email verification; an accepted but never activated beta uses 90 days after
invitation acceptance. With several grants, the latest relevant date governs.
Activation or an approved renewal changes the relevant date; ordinary sign-in
does not. Unaccepted invitations become eligible 90 days after invitation expiry.
Account cleanup includes linked trial, device, delivery and audit history.

Security and diagnostic records

Activation-delivery records become eligible for deletion 90 days after issuance;
computer-retirement diagnostics 90 days after retirement; abandoned or clock-
repair requests without an issuance 90 days after creation. A valid delivery or
retry window is preserved. Other routine audit events and free-form publisher
notes become eligible after 90 days. Current grants and active registrations
follow their separate account/licence purpose.

Expired sign-in links, sessions and rate-limit counters are removed by the next
successful scheduled cleanup or applicable later requests. Rate counters expire
according to their hourly or daily security windows. Cleanup uses bounded batches;
backlogs, outages or recovery pauses can delay removal. We monitor and address
those delays rather than treating missed cleanup as completed deletion.

Minimal records may remain to prevent an old licence-administration request from executing
again. After account erasure, these contain only random operation identifiers
and fixed erased markers; the linked account information, request hashes, dates
and details are removed. They remain while the service, including a restored
service, can accept such commands, and are removed when that processing and
recovery end. Separate operator records may still make them linkable and need
their own limited purpose and retention.

Support correspondence

Ordinary correspondence and attachments are kept for 12 months after final
resolution, with monthly review of due cases. A reopened case receives a new
date after final resolution. An ongoing dispute or a specific legal obligation
may justify longer, restricted retention with a documented reason and review date.

Backups and provider copies

Daily encrypted database backups have a 90-day retention policy. Manual archives
and local recovery copies are removed after a successful recovery check. The
selected Cloudflare Free plan also provides seven days of D1 recovery history.
Deleting a live record does not instantly rewrite older backups. Restricted
erasure records are kept separately until every older recoverable copy has gone,
so requested erasures can be reapplied before a restored service resumes.
Automatic expired-account eligibility is also checked again before reopening it.
These recovery records are not used to assess trial eligibility.

Cloudflare's separate network/security/account retention depends on its stated
purposes and legal requirements. Our deployment configuration disables stored
Workers application logs; this does not disable all provider processing.
Sources: https://www.cloudflare.com/privacypolicy/
https://developers.cloudflare.com/d1/platform/limits/

Resend states that email and log data on the selected Free plan is retained for
30 days and its backups persist seven days. Its account-termination rules and
separate account/compliance retention also apply. Earlier removal of sent email
requires contacting Resend. These are not one deadline for every provider record.
Source: https://resend.com/security/gdpr

Domainhotelli publishes a two-week hosting-account backup period and 100-day
intrusion-detection/prevention log retention. It separately lists mail-server
logs as its own controller processing, without specifying a period on that
page. These can include IP addresses, email addresses and usernames. Neither
the 100-day period nor our 12-month support policy defines all mail-log retention.
Source:
https://www.domainhotelli.fi/ohjeet/oma-tili/henkilotietojen-kasittely-webhotelleissa/

7. Deletion, your choices and your rights

Email and device-binding information are necessary for online account creation
and activation. Without them, we cannot provide that activation. You can cancel
before starting an online operation. Existing valid offline authorisations and
standalone Norm Gain do not require routine contact with us.

Retiring a computer frees its activation slot; it does not immediately erase
its diagnostic history. Uninstalling GG_rand does not request server deletion
and leaves local activation/recovery evidence by default. Contact us to request
account erasure. Erasure removes linked trial history and operational account
records; support correspondence, provider records and backups have their
separate procedures. It does not remotely revoke certificates stored offline.

Local removal instructions:
https://license.tamitech.fi/privacy#local-records

Removing local licensing records

Windows

These steps apply to the current Windows user's GG_rand licensing records across
REAPER installations. If you want to use a paid licence again without the service,
keep your Offline Recovery License and compatible installer safely first.

1. Close every REAPER instance. To stop future local licensing reads, also remove
   the extension using the GG_rand installer. Norm Gain can be retained separately.
2. In Windows Credential Manager, open Windows Credentials, then Generic
   Credentials. Remove only the entry with this target, if present:
   GG_rand:clock-witness:v1:software\tamitech\gg_rand\licensing\v1
   This is GG_rand's local clock record, not your Windows or email sign-in.
3. In Registry Editor, navigate to this exact current-user key and delete only
   that key, if present:
   HKEY_CURRENT_USER\Software\Tamitech\GG_rand\Licensing\v1
   Do not delete the Tamitech parent key or other applications' records. If you
   are unsure which entry is correct, contact support before deleting it.
4. Separately remove any licence or recovery files you saved elsewhere if you
   also want those copies deleted. Windows backups, synced folders and other
   Windows user profiles may retain separate copies.

Mac

1. Close every REAPER instance and remove the GG_rand extension if you want to
   stop future local licensing reads. Norm Gain can be retained separately.
2. In Keychain Access, locate the generic-password items whose service is
   com.tamitech.GG_rand.licensing.v1 and whose account is certificates or
   clock-witness. Remove only those two GG_rand items, if present. Do not remove
   the Keychain itself or other applications' items.
3. In Finder, use Go > Go to Folder and open:
   ~/Library/Application Support/Tamitech/GG_rand/Licensing/
   Remove only its v1 folder, if present, which contains local clock and lock
   records. Do not remove the Tamitech or GG_rand parent folders. Contact support
   if you cannot identify the exact items.
4. Separately remove any saved licence/recovery files if you want those copies
   deleted too. Backups, synced folders and other Mac user accounts may retain
   separate copies.

Removing these records removes local activation for the affected OS user. New
GG_rand panel work then requires activation again or import of a valid saved
paid recovery file. Removing only part of the clock data can require online
clock verification for trial/beta use. Removal does not extend an evaluation,
free a server-side activation slot or erase your online account. Normal project
playback and standalone Norm Gain remain available. These steps do not remove
REAPER projects, GG_rand preferences, installer journals or system backups.

For a paid account, we explain the loss of online activation and account-based
recovery and offer help saving the Offline Recovery License and a compatible
installer first. You can decline that help without losing your right to request
erasure. Deleting the account does not itself cancel your perpetual permission
for the purchased major version. Records required by a specific legal obligation
are handled separately, and we explain any resulting restriction on erasure.

Depending on the applicable conditions, you may request access, correction,
erasure, restriction or portability. You may object to processing based on
legitimate interests because of your particular situation. Where processing
relies on consent, you may withdraw it without affecting earlier lawful processing.

Contact eero.halme@tamitech.fi. We may ask for proportionate identity verification.
We respond without undue delay and within one month, unless a permitted extension
applies. If complexity or the number of requests requires up to two additional
months, we explain the extension within the first month. If we cannot fulfil a
request, we explain the reasons and complaint options. We coordinate applicable
requests with providers where necessary; local deletion alone does not prove
that all provider copies have disappeared.

You may complain to the competent supervisory authority, including the Finnish
Office of the Data Protection Ombudsman: https://tietosuoja.fi/en

8. Automated checks and human review

Licence checks automatically examine signature validity, entitlement type and
major version, device binding and active-device capacity. Trial and beta checks
also examine expiry and time integrity; paid perpetual licences do not expire
or depend on those evaluation-clock checks.
They can refuse activation or new GG_rand panel work. Security rate limits can
temporarily refuse requests. These checks use licensing and security information.
They do not analyse project content or monitor your work within REAPER. Expiry
does not disable normal project playback or standalone Norm Gain; continuing
permissions are set out in the License Agreement.

Routine sign-in failures and short request limits do not cancel a licence.
However, a refusal can prevent use of an otherwise valid licence. This can
affect an individual's contractual access or, for example, significantly affect
their ability to carry out professional work, including when the organisation
holds the licence. Such consequential refusals require the protections of GDPR
Article 22; the rules do not make every technical licensing check a decision
with that level of effect.

If you believe a refusal is wrong, contact eero.halme@tamitech.fi, describe what
happened and request human review. A person at Tamitech will consider your
explanation, review the relevant records, explain the outcome and arrange a
correction where a mistake is established. You can express your view and contest
the result. Do not send passwords, sign-in links or recovery files. Human review
does not automatically extend a trial or beta entitlement.

GDPR Article 22 restricts solely automated decisions with legal or similarly
significant effects unless an applicable exception and its safeguards are met.
Our legitimate interests and a contract with your organisation do not, by
themselves, provide such an exception. A later appeal does not replace it.
This notice does not ask you to waive that protection or give blanket consent
to automated decisions.

9. Security and changes

We protect licensing data through encrypted network connections, signed licence
and time-verification responses, protected Windows and Mac activation storage, restricted
account actions and encrypted database backups. No measure eliminates every risk.
Protect your email account, sign-in links and saved recovery materials.

Material changes to processing will be explained before they take effect. A new
notice does not by itself authorise an incompatible new use of existing data.
The version and effective date identify the notice you can retain with your
software. The current notice and contact route will remain accessible from the
account service and with the distributed software.