Privacy Policy

Contact: contact@pullzeaudio.com

This Privacy Policy explains what PullzeAudio collects, why we collect it, where it is kept, how long we keep it, and the choices and rights you have over it. It applies to the PullzeAudio Windows desktop application and to the pullzeaudio.com storefront and account area.

We do not sell, rent or trade your personal information. The PullzeAudio app carries no third-party advertising or behavioural analytics SDK, and the website sets only the first-party cookies a session and a cart need.

1. What We Collect, And Why

The sections below follow the order in which the app and the website meet you: the account, the device, the reports you choose to send, the licence checks, the settings snapshots, the security reports, the website, support, trial records and session evidence.

1.1 Account Data

An account is created for you by a verified paid purchase, by an administrator grant, or through the secure trial link you request. On that account we hold:

• Your email address, which is the account identifier and the destination for licence delivery, password setup, purchase email and support replies.
• Your password, which is never kept as plain text. It is stored only as a one-way hash, so even our own staff cannot read it.
• The display name you choose, and the full name you type when you sign an agreement electronically, together with the decision you made.
• The country you select at the agreement step, the policy versions you accepted, and the time you accepted them.

Account data lives in the pullzeaudio.com account database, is protected in transit and at rest, and is reachable only by authorised PullzeAudio staff. Agreement records are additionally sealed with authenticated encryption, and a keyed integrity hash lets us prove that a retained record is the record that was written.

1.2 Licence And Hardware-Fingerprint Data

When the app registers a PC or activates a licence, it creates an opaque device identifier and a key pair, and it binds the licence to a hardware fingerprint derived from stable Windows identifiers. We store the device’s public keys, never its private keys. The app may also send a bounded hardware inventory, which can include the machine GUID, the firmware-reported system UUID, board and BIOS serials, processor identifiers, disk serials, network adapter addresses, a TPM endorsement-key hash and the Windows build. That inventory is reduced to printable values, capped in size and depth, kept as operator-only metadata on the device row, and shown only on our licence screens. Nothing in it is a copy of your files, and we do not treat it as proof of who you are.

For each active activation we also record:

• The friendly device name, normally the Windows computer name.
• The public IP address seen at registration or activation.
• A last-seen timestamp, refreshed by the app’s licence checks.
• The activation list for your licence, used to enforce the two-device and single-active-session rules and the New PC Reset credit in the Terms Of Service.

A server-keyed digest of the strongest durable machine identifier decides whether a physical PC has already used its free trial. The raw identifiers are not copied into that trial ledger, and a client that stops sending the inventory cannot clear the digest that way. You can review your bound devices in the account area, and a licence moved with a New PC Reset is recorded in the same place, so an administrator can see which PC replaced which.

1.3 Diagnostic Reports You Choose To Send

The app writes bounded local health and support logs. A diagnostic report is uploaded only when you ask for it from the Support screen, or when you accept an administrator’s recorded request for one, and the app shows you what will be sent before it is sealed. The report is signed by the registered device, encrypted to the server before it leaves the PC, and stored as ciphertext with non-secret metadata such as its envelope identifier, size and digest.

A diagnostic report contains:

• The app version, build and release channel, and the driver and health-log entries support needs.
• The Windows and audio-device configuration that explains a routing or setup problem.
• The bounded security state described in section 1.6.
• The message and reply address you supplied with the request.

Diagnostic reports never contain audio, recordings, typed text outside the message you wrote, or your files. An administrator request is a specific, recorded collection request aimed at the signed-in account and device. It grants no remote desktop control and cannot carry an executable, a URL, a setting change or an arbitrary command. A repeated report with the same envelope identifier is accepted only when its contents match exactly, and the server keeps the ciphertext with a hash of the complete signed envelope so a retry cannot smuggle in a change. There is no public read route for a diagnostic.

1.4 Licence Checks And Signed Access Grants

While you are signed in, the app asks the licence server for a short-lived signed access grant when it starts, when it restores a saved session, and at least once a day. Each request carries your account session token, the device identifier, a fresh request nonce, and the consistency hints the server needs to issue the next grant in sequence. The server answers with a grant that is signed with our release key, bound to your account and device, and limited in time. A failed check retries with a bounded delay.

These checks enforce the licence, activation and trial rules in the Terms Of Service and are what authorises audio processing in the app. A grant states which account and device it belongs to, its sequence number, whether it is a trial, paid or locked grant, when it was issued, when it expires, and how much processing or trial time it covers. Unsigned responses, a replayed sequence, a local clock rollback and a stale file on disk never authorise audio. They carry no audio content and no recording.

1.5 Settings Analytics Linked To Your Account

While you are signed in, the app reports one settings snapshot per UTC day for the account, sent as a signed and encrypted envelope from the registered device. A retry or a second device updates that same account-day record instead of adding one, and the request carries no account identifier of its own: the server takes the account from your authenticated session rather than trusting the app’s copy. The snapshot contains:

• The app version, build identifier and release channel.
• The selected tune and its revision, and the game the tuning was built for.
• The bounded mixer and routing controls, and the selected tune’s control values as small integer buckets.
• Nothing else: arbitrary text, file paths, recordings, device names and client-supplied identifiers are refused by the endpoint.

We use these snapshots to see which features and tuning choices actually get used, to compare releases, and to decide what to improve next. The collection is part of the licensed service and has no per-account off switch. Snapshots are kept for the life of the account and are removed when the account is deleted.

1.6 Integrity And Security Reports

The app keeps a bounded report about its own process so that an authorised administrator can review a confirmed integrity problem. It records the app identity, the collection time, the monitoring coverage, an executable-integrity state, the account access state and, when relevant, a fixed reason code with the phase and signal that produced it. It never records your licence key, your password, your session tokens, tool names, process identifiers or file paths.

Automatic integrity reporting and administrator diagnostic requests stay off until the Support screen has recorded your choices, and you can turn future sharing off again from the app. A recognised process name or an unusual configuration is an observation, not proof that the app was modified, and we keep access decisions such as an expired trial separate from tamper findings. Where evidence shows a modified executable, the current app process can be locked and a protected report sent through the authenticated upload path. Reports are grouped for review by authorised staff, retained for support and dispute handling, and removed by an administrator when they are no longer needed.

1.7 Website Analytics

The pullzeaudio.com website keeps its own standard access records, such as the requested page, the response code, the timestamp and the originating IP address, for security and abuse prevention. The site sets first-party cookies for the account session, the shopping cart and form protection, and nothing else. We run no third-party advertising trackers, no cross-site behavioural advertising, and no session-replay or heatmap service on this site.

Aggregate counts of page and product views help us see which pages work. They are read by authorised staff and are not used to build a profile of you, and you can refuse or clear cookies in your browser, though the account area and the cart need them to work. Where we keep a record to investigate abuse, we keep it for that purpose only and delete it when the investigation closes, and we do not combine website records with your app data to target advertising, because we run none.

1.8 Support Conversations And Requested Diagnostics

Support is a two-sided conversation between your account and an administrator, and it is stored so that both sides see the same transcript. Messages are stored as plain text with markup stripped and control characters removed, size-limited, and escaped again wherever they are displayed. Read markers, closure and per-side hiding are recorded with the message so the transcript stays honest.

When a question cannot be answered from the conversation alone, an authorised administrator may ask the signed-in app for the diagnostic report described in section 1.3. That request is bounded, time-limited and recorded with the requesting administrator, the target account and device, the request time and the delivery state, and it grants no remote desktop access, no command execution and no persistent access to your PC. PullzeAudio does not take remote control of customer machines. A report that is never delivered is recorded as undelivered, and you may decline the request.

1.9 Trial Setup, Eligibility And Agreement Records

When you request a secure trial link we keep the request even if you do not finish: the email address in hashed form, the delivery state of the link and the setup progress recorded against it. Verification of the link is kept as a sealed receipt, which is evidence that the address was reachable rather than merely typed.

The trial account email is fixed, so a later purchase can be matched to it. We retain the trial clock, the first activation and its one-hour window, the device eligibility result, blocked attempts and any verified paid upgrade. Device eligibility uses a server-keyed digest of the activation fingerprint together with the machine identifiers the app supplied. Those records are what stop a second free trial after a reinstall or an account deletion, and they are not proof of anyone’s identity.

An accepted agreement is stored as a sealed record: your account reference, the country you selected, the exact notice and policy versions you were shown, your typed signature name, your decision, and the server timestamp. Request evidence covers the source of the review, the authentication method, the IP address the server saw, the client user agent and the account and device references available at the time. Typing your name and choosing I agree records an electronic signature; our integrity hash shows the record has not changed since, and it does not by itself establish who you are.

After you request a trial link, we may send at most two automatic setup reminders, roughly 24 and 72 hours later, while the setup stays unfinished. Verification plus the current agreement, a trial activation, a purchase, account closure, an email suppression or the reminder’s own one-click stop link ends them. To hold that cap and remember an unsubscribe we keep a blinded hash of the trial email, the attempt times and outcomes, the stop reason and the unsubscribe time, after an account or the plugin is deleted. Signing up again does not clear that ledger.

Account, purchase, activation and usage records may be given to the payment provider to answer a dispute, or to the authorities where we are reporting evidenced suspicion of fraud as the law allows. Trial accounts do not receive support; privacy requests, account-security requests and statutory rights remain available to them.

A marketing or optional follow-up preference is recorded separately and only when you ask for it. Accepting the account agreement is not a marketing opt-in, opening or leaving a page sends no campaign, and an unfinished setup reminder is about the setup you requested rather than a promotion. An administrator can delete an unfinished setup record, and doing so does not delete an account or a licence, reset trial eligibility, or clear the reminder cap.

1.10 Device And Session Evidence

Beyond the daily snapshot, the app reports presence and session evidence while you are signed in. Presence is a bounded contact about once a minute carrying a domain-separated digest of the device identifier, so the service can tell that the app is running, deliver a subscribed account status and record that processing has stopped when access ends. That contact can carry one fixed request only: an authorised administrator may ask the signed-in device for the bounded diagnostic described in section 1.3, and nothing else.

Session evidence is a cumulative report of time spent running and processing, together with counts of actions by category, such as:

• Tune changes, preset and profile work, and audio setup or repair actions.
• Support actions, test tones and recordings started by you.
• Updates applied, and page visits inside the app.
• Which app version, build and release channel produced the sample.

These reports are signed by the registered device and encrypted in transit and at rest, and they are read only by authorised staff. They describe attempts rather than completed operations, and they never contain audio, recordings, typed messages, custom profile names or your device name. Processing-stop observations are the app’s own report that it stopped; they are not proof that a physical audio endpoint disconnected or that all sound on the PC stopped.

1.11 Optional Trial Feedback

Once a trial has ended, you can choose to send trial feedback, either from the desktop app or from My Account. Sending it is entirely optional, and it changes nothing about the trial, the licence, the account agreement or the access you already have.

If you choose Send Feedback, or save changes to a response you already sent, the record holds the 0–10 rating you picked, any written comments you chose to leave, your account and the trial the response refers to, and the server time the response was saved. Your latest response is held with your account and replaces the earlier one when you edit it. Authorised staff can read the rating, the comments, the account, the trial reference and the saved time.

A submitted response is kept for the life of the account. Deleting the account removes the linked feedback record from the live account database, apart from the retention exceptions set out above.

2. What We Do Not Do

• We do not put third-party advertising or behavioural analytics software in the app, and no third-party tracker on this website.
• We do not sell, rent, lease or trade your personal information.
• We do not upload your audio. No recording, capture or game audio ever leaves your PC through PullzeAudio.
• We do not collect the contents of your files, your messages or unrelated browsing. Device, diagnostic and session reporting is limited to the categories described here.
• We do not share your hardware fingerprint or your activations with anyone else, except as needed to process a payment or to comply with the law.

3. Data Retention

• Account and licence records are kept for the life of the account. When an account is deleted we remove the account details, the licence history and the linked device rows, except where tax, accounting or fraud-prevention rules require us to keep a record.
• Daily settings snapshots are kept for the life of the account and removed from the analytics table when the account is deleted.
• Session evidence is kept for 90 days after the most recent accepted sample. Account deletion removes the linked rows, with retries when a request is delayed.
• Presence records are kept for up to one year after the latest contact and are removed with the account.
• Control requests and processing-stop events are cleaned up after 90 days.
• Diagnostic reports and their review index are kept for support, account security and dispute handling. An administrator can remove them when they are no longer needed, so there is no fixed deletion date for them.
• Trial eligibility records outlive trial expiry and account deletion on purpose, because that is what prevents a second free trial. Detailed trial events are kept for 90 days, and the reminder ledger described in section 1.9 is retained to hold the cap and the unsubscribe.
• Support conversations are kept while the account is open and for as long as the dispute and security obligations that touch them require.
• Contact-form messages are kept so we can answer them, and anything the spam filter marks is deleted after 30 days.
• Encrypted agreement records are retained with the account and the transaction history for contract administration, security and dispute handling.

4. Your Rights

At any time, by writing to contact@pullzeaudio.com from the address on your account, you may:

• Access the personal data we hold about you and ask for a copy in a machine-readable form.
• Correct inaccurate account data, and you can edit most of it yourself in the account area.
• Delete your account. Deletion closes the account and revokes the associated licence and its activations.
• Object to a particular use of your data where the law gives you that right.

Deleting an account does not trigger a refund, and it does not remove the trial eligibility records that prevent a repeat trial. Deleting an account does not immediately remove the control audit and diagnostic archives described in sections 1.3 and 1.10 either; those follow their own retention rules. We answer verified requests within a reasonable time, normally within 30 days, and we may ask you to confirm control of the account email before we act, because a request that cannot be verified is a way for someone else to reach your data. Where a request touches another person’s data, a security investigation or a legal duty to retain a record, we explain what we cannot remove and why.

5. Security

We protect your data at rest and in transit with layered controls: HTTPS site-wide, one-way password hashing, sealed agreement and diagnostic records, device-signed and encrypted reports, key material read only from the server configuration, and access controls around our administration screens. No system is perfectly secure. If you think your account has been compromised, email contact@pullzeaudio.com at once and we will help you lock it down and recover it.

6. Children

PullzeAudio is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has given us personal information, email contact@pullzeaudio.com and we will delete it.

7. Changes To This Policy

This Privacy Policy may be revised from time to time. The current version is published at /privacy-policy/, and we give notice of a material change on the website or at the next account agreement. An agreement record keeps the exact policy you were shown when you made your choice, and a later revision does not change what an earlier agreement means.

8. Contact

Privacy questions, rights requests and deletion requests: contact@pullzeaudio.com.