Privacy Policy
Contents
1. The short version
Patch runs its Hub, Runners and agents on hardware you control, using your own AI-agent accounts. We operate the website, access-request, licence-issuing, online activation and app-update services, the service that receives problem reports, and hosting for public media, including Guide clips, website films and trailers, and blog audio.
What reaches us: your access request, if you send one; contact details our operator enters to issue you a licence; our access decisions; licence and key-email records; activation requests and records; the Mac app's update checks; and any problem report you choose to send us. Section 3 explains these records. Requests to our services also expose ordinary network metadata. Google Analytics measures visits to patchcove.com only under the conditions in section 11; it does not run in the Patch software.
Your work: we do not receive your files, prompts, agent output, conversation history or account credentials through the ordinary operation of your agents. You may include some of them in a problem report or show them to us during set-up help (sections 3 and 4). Agents can send data to their AI providers and connected services under those services' own terms and privacy notices. Patch also contacts a public provider-status service as described in section 4. Builds that enforce activation contact activate.patchcove.com at activation and normally once a day afterwards; licence checks are not entirely offline. The Mac app also asks activate.patchcove.com about every 6 hours whether an update is available, as described in section 4.
2. Who we are
The controller of the personal data described here is Native Records LLC, a California limited liability company, of 3705 W Pico Boulevard #1, Los Angeles, California 90019, United States. It operates the Patch software and the patchcove.com website. Contact details are in section 14.
3. What we collect
| Data | When | Why |
|---|---|---|
| Access request: a request identifier and submission time; your name and email address; any company, use-case choice and note you provide; and the request's closure time. | You submit the Request access form; we record closure when we decide it. | To consider and answer your request. We store it in our database and email a copy to our mailbox. |
| Operator-entered licence details: your name and email address, licence type and term, a direct-issuance chain identifier, the licence's request or direct origin, and the issuing operator's email address. | Our operator enters details to issue a licence directly, including for someone who never submitted Request access. The details come from you or the person arranging your access. The key email explains that source; we do not create a public-form submission or store the arranger's identity as a separate licence field. | To arrange and deliver access and administer the licence. Direct entry does not mean you submitted the public form, accepted the Terms or agreed to marketing. |
| Access decision: the request identifier, approval or decline, decision time, the deciding operator's email address, a snapshot of your name and email address, and, for an approval, the associated licence identifier. | We approve or decline a submitted request. A decline creates a decision record even though no key is issued. Direct issuance without a request does not create an access-decision record. | To record the outcome, avoid duplicate decisions and administer access. |
| Licence record: the licence and request or direct-issuance identifiers and source; your name and email address at issue; the signed key; licence type (Single machine or Hub); term in months; issue and expiry times; the identifier of a previous licence if this is a renewal; and the issuing operator's email address. | We issue or renew a key, following an access request or a direct arrangement. | To deliver, resend and renew your licence, record your entitlement and prevent duplicate issuance. |
| Key-email attempts: an attempt identifier, the linked licence identifier, purpose (issue, resend or renew), sent or failed status, any recorded error, the sending operator's email address and the attempt time. | We attempt to email a licence key. | To establish whether delivery succeeded and to investigate or retry a failure. The linked licence identifies the recipient. Declining a request does not itself send a licence-key email. |
| Activation requests: the signed licence key, a random installation identifier, the Patch version, and whether the request is to activate/check in or release the installation. The key contains the name, email address and entitlement fields described below. | An activation-enforcing build starts with a key, the key changes, a periodic check runs, or you request a check or release. | To verify the key, enforce the installation allowance and apply revocation. We receive the full key to check its signature; this request is not just a key identifier. |
| Activation records: the renewal-chain identifier, the key identifier last presented, the random installation identifier, first and last successful check-in times, Patch version, the expiry time of the key last presented (or that it has no expiry), and any time the operator freed the installation or you released it; freeing also records the operator's email address. | An installation successfully activates or checks in, is freed by the operator, or is released. | To show which installation holds the licence and let you move it. The random identifier is not a hardware fingerprint; linked to your licence, it is pseudonymous personal data. |
| Activation refusals: the renewal-chain identifier, the cumulative count and latest time of attempts refused because another installation holds the licence, and up to 20 recent, distinct refused installation identifiers. | An otherwise valid activation finds another installation holding the licence. | To enforce the installation allowance and investigate licence sharing or activation problems. A 20-identifier limit is a list-size limit, not a deletion period. |
| Revocations and operator actions: the renewal-chain identifier, revocation time and operator email and, for a key without a licence record, its expiry time if known; and an action identifier, action (free, revoke or undo revoke), time, operator email and, for freeing, installation identifier. | The operator frees an installation, revokes a licence or undoes a revocation. | To enforce and explain changes to licence status. Undoing revocation removes the current revocation entry but leaves the action history until its retention deadline. |
| Update checks: the signed licence key, the random installation identifier, the Patch app and service versions, the Mac's processor architecture (arch) and its macOS version. | A compatible Mac app checks for an update as described in section 4, after this installation has accepted the Risk Notice and the update-check disclosure has been shown. | To decide whether an update is offered to your licence and, if one is, to issue a short-lived download ticket. We use the check only to answer it: the update service writes nothing about it to our databases and logs no key, ticket or download link. |
| Network and abuse-prevention data: ordinary request metadata, including the connection's IP address, reaches Cloudflare when you use our services. With an access request we store the browser's user-agent string and a keyed one-way IP hash; with a problem report we store a keyed IP hash. The activation service uses the caller's IP address (an IPv6 network prefix for IPv6 callers) and the key identifier as Cloudflare rate-limit keys. It does not write IP addresses, user-agent strings or location to its activation tables, and it does not deliberately include those fields in application log messages. Cloudflare may separately process or retain request metadata in platform logs, security analytics and rate-limit systems, as explained in section 7. | You visit the website, request public media, including Guide clips, website films and trailers, and blog audio, submit an access request or problem report, make an activation or release request, or the Mac app checks for an update. | To deliver resources, secure the services, limit repeated requests and investigate failures. IP hashes and identifiers linked to a licence are pseudonymous, not anonymous. Edge processing and rate-limit counters are separate from our activation database. |
| Website analytics: through Google Analytics, the pages you view on patchcove.com, the referring page or site, browser, device, screen size and language, visit duration and approximate location derived by Google from your IP address, under a random cookie identifier. For public videos, we also collect playback starts, progress at 25%, 50% and 75%, and completion, together with the film's identifier, its duration and the page where it plays, under the same random cookie identifier. We do not associate that identifier with your access-request, licence or problem-report records. | You visit patchcove.com where section 11 permits Analytics to load. | To understand which pages and public videos people use, how people find the site, and whether video playback starts, reaches those milestones or finishes. |
What is inside a key. A signed licence key contains its format version, licence identifier, kind, issue and expiry times, machine allowance, and the licensee's name and email address. Its payload is encoded, not encrypted: someone who has the key can read those fields. The signature protects against alteration; it does not conceal the contents. Treat your key as confidential.
Problem reports. If you use Report a problem to send a report to the Patch team, your Hub sends it to reports.patchcove.com only when you press Send. It contains your description, your email address if supplied, and the diagnostic sections you select. You can read each section in full and change its selection before sending.
The sections selected by default include software and machine facts, the browser's user-agent string and display information, connection events, and a recent click trail of up to 200 interface events. The trail contains control identifiers, the view and surface, and event times; it does not contain the text you type. Sections that can carry work content, including logs, errors, messages, machine and project names, and a desktop screenshot, start unselected. Default selection does not send a report: you still choose whether to press Send.
Before sending, Patch applies its secret-recognition and file-path redaction rules. These rules cannot guarantee that every secret or personal detail is removed, so review the selected sections. We store the report in our Cloudflare database and email a copy, including the attached diagnostic bundle, to our Google Workspace mailbox. The app-generated browser user-agent in structured diagnostics follows the 30-day clearing rule in section 7; the other retained diagnostic content, including the selected click trail, follows the report's period. This is not a promise to recognise and redact every personal detail you paste into logs or free text. A report sent to a thread in your own installation does not reach the Patch team. We use personal data about other people included in a report only to investigate the reported problem.
Payments. The current access-request and licence-issuing services have no card checkout or automated payment-notification integration. If we agree fees separately, your commercial terms identify the payment arrangement. We will update this notice before introducing an online payment flow that collects additional personal data.
4. Data in your installation and network requests
Your files, source code, prompts, agent output, conversation history and credentials remain outside the services we operate during ordinary agent operation. The exceptions are information you choose to send in a problem report and information you show or send during set-up help. The network requests below do not make us the host of your agents or their conversations.
Licence verification and online activation. The software checks the signature and expiry locally, using the corresponding verification public key. A production key needs a compatible release configured with that public key; an earlier or development build may not accept it. In a build that enforces activation, the installation also sends the activation request in section 3 to activate.patchcove.com when it starts with a key, when the key changes, and normally once a day, with a small scheduling variation. Additional requests can follow a supported Check now action or a retry, and releasing an installation sends a release request.
The service checks which installation holds the licence and whether the licence has been revoked. One installation holds a renewal chain at a time. A successfully activated installation can keep using its still-valid key while the service is unreachable for up to 30 days after its last successful activation check. That grace does not override a refusal the installation has received, expiry or termination, and a never-activated key needs its first successful check. Releasing or freeing an installation, or 30 days without a successful check-in, makes its seat available; a retained database row is not deleted merely because its seat becomes available. The service receives no project files, prompts, conversations or agent output in these activation requests, and the random installation identifier is not derived from your hardware.
Update checks. The acceptance and timing safeguards below describe Mac app releases that implement the update-check disclosure. Earlier releases can send update-check requests before Risk Notice acceptance. Publishing this policy does not change those releases or retrospectively authorise earlier collection. The Patch Mac app asks activate.patchcove.com whether an update is available for your licence. Each check sends the signed licence key, the random installation identifier, the Patch app and service versions, the Mac's processor architecture (arch) and its macOS version. The app sends no update check before this installation has accepted Patch's Risk Notice and the update-check disclosure has been shown. On the first launch that completes these steps, the app schedules its first automatic check 2 minutes after both are complete. On later launches where these steps are already complete, the schedule starts again with a 2-minute delay. Later automatic checks normally run every 6 hours; after a failed check, the retry delay can increase to 24 hours. Pressing Check or Update can also send a check after these steps are complete.
We use the check to decide whether an update is offered to your licence and, if one is, to issue a short-lived download ticket the app uses to fetch it. The update service only reads our records to answer: it writes nothing about the check to our databases, and it logs no key, ticket or download link. Cloudflare receives ordinary request metadata, including the connection's IP address, the time and the app's user agent, and the service uses the IP address and the key identifier as rate-limit keys, as described in sections 3 and 7. A check is not a record of your agents' work or interface actions.
Public media. We host public Guide clips, website films and trailers, and blog audio at media.patchcove.com. Opening a page may request media files or a poster image; starting playback requests the audio or video. Our media host and Cloudflare receive ordinary request metadata, including the connection's IP address, requested resource, time and browser information. These media requests do not include licence keys, prompts, messages or project files.
Provider status. The Hub periodically requests the public summary at status.claude.com to display Claude service status. That service receives the Hub connection's IP address and request metadata, including Patch's status-poller user-agent. The status request does not include your prompts, project content, licence key or AI-provider credentials. The status service is a third-party service governed by its own privacy terms.
Usage information. The activation service receives licence-related check-in information, and the update checks described above; both can indicate that an installation is running and which version it runs, and neither is a record of your agents' work or interface actions. Apart from that activation and update-check information, Patch does not automatically send us usage telemetry. The interface click trail described in section 3 is included only if its section is selected in a problem report you choose to send. Google Analytics runs on patchcove.com, not in the Patch software.
Claude account labels. About every five minutes, your Patch router runs the official Claude Code sign-in status command. From its answer, Patch reads the signed-in account's email address, organisation identifier and organisation name to identify the account shown with its usage reading. On that machine, Patch keeps the email address and organisation name with the most recently saved usage reading in claude-stream-usage.json. It sends those labels with the reading through your installation's own hub to your connected Patch viewer. The organisation identifier itself never leaves the router. This feature does not send the account labels or usage reading to Native Records.
Services you connect. Agents can send what they read to your AI provider and exchange data with tools and services you connect. That traffic goes between your machines and those services, under their terms and privacy notices. We do not receive it merely because Patch starts the agent. For personal data processed entirely in your installation or by services you select, you decide the purposes and means; we do not become your processor merely by supplying this self-hosted software.
Set-up help. If we help you set Patch up, on a call, by screen share, or with access you grant us to your machine, we may see files, messages or personal data while we do. We use what we see only to set Patch up for you, keep no copy unless you send it to us, and stop using any access you gave us when the set-up is done or you withdraw it.
5. Why we use it, and our legal basis
Where the UK GDPR or EU GDPR applies, we rely on these bases:
- Performance of a contract: arranging, issuing, delivering, resending, renewing and activating your licence and providing the agreed entitlement where you are a party to that contract.
- Legitimate interests: considering and answering access requests; arranging access for a person through their organisation or another authorised contact; recording approvals and declines; administering activation, installation limits, releases and revocations; offering app updates to licensed installations; preventing duplicate decisions and licence issuance; maintaining delivery records; investigating reports; delivering public media, including Guide clips, website films and trailers, and blog audio; keeping our services secure; and understanding aggregate website traffic. We assess these interests against your rights and use only data reasonably needed for the purpose.
- Legal obligation: retaining any invoicing, accounting or other records that applicable law requires.
- Consent: any marketing email for which consent is required. You can withdraw it at any time. We do not load Google Analytics where section 11 excludes it.
Access approvals and declines are made by the operator, not by an automated scoring system. Activation checks automatically apply technical licence conditions, including validity, expiry, the installation allowance and recorded revocation; a refusal can prevent new agent work from starting. These checks do not score your work or profile your personal characteristics. Contact us using section 14 if you think a licence or activation decision is wrong so that we can investigate. We do not sell personal data.
6. Who we share it with
We use the following providers for the purposes described here. They handle information under their applicable service terms, data-protection terms and privacy notices. Some processing, such as a provider's own account-security records, is for that provider's purposes rather than solely on our instructions:
- Cloudflare: hosting the website, licence control plane, activation and app-update service and report receiver, and public media, including Guide clips, website films and trailers, and blog audio; storing access requests, directly entered licence details, licence records, decisions, key-email attempts, activation/refusal/revocation/action records, replay-prevention markers and reports; processing activation and update-check traffic and rate-limit keys; routing access-request and problem-report emails; and protecting the operator's control-plane login.
- Resend: sending licence-key emails. It receives the recipient's email address and the email content, including the licensee's name, signed key, licence type and dates. Because the key's payload is readable, sending it also discloses the fields described in section 3 to the email-delivery service.
- Google Workspace: hosting our business mailbox, which receives a copy of each access request and problem report, including any diagnostic attachment. It processes the sender or reply-to details, message metadata, message content and attachments, and correspondence we exchange with you.
- Google Analytics: measuring use of patchcove.com as described in section 11, separately from Google Workspace. We have turned off Google signals, advertising features and every data-sharing setting Google Analytics offers. Google's privacy policy is at https://policies.google.com/privacy.
The public status service contacted directly by your Hub and the providers or tools you connect are described in section 4. Naming them here or there does not make them our processors for all of their activities. Your own email provider also receives a key email delivered to your address under your arrangements with it.
We may disclose data where legally required or reasonably necessary to establish or defend legal claims. If the business is sold or reorganised, data may transfer to the acquirer subject to this policy.
7. How long we keep it
| Record | Retention |
|---|---|
| Access requests | While the request is open, then 12 months after we offer access or tell you we cannot. If it is still open after 24 months, we ask whether you want us to keep it; if you do not reply within 30 days, we delete it. The same schedule applies to the request copy in our mailbox. If access is approved, the separate licence and approval records follow their own schedule below. Direct issuance creates no access-request row and does not enter the 24-month request review. Its licence and key-email records follow their own schedules below. |
| Declined decisions | 12 months after the decline, including the name, email address, request identifier and operator details in that decision. A failed attempt to close the original request does not extend this period. Related copies in our mailbox follow the same deadline. |
| Licence records and approved decisions | While a key in the linked renewal chain remains current, then four years after the last key in that chain expires. This includes the stored signed keys, identity snapshots, issue and renewal links, and operator details. We use the period after expiry for licence administration and evidence of the agreement. |
| Key-email attempt records | No more than 12 months after each attempt, whether it succeeded or failed, and earlier if the linked licence records reach their own deletion deadline. Renewing the licence does not restart the attempt's period. |
| Problem reports | 12 months after receipt for the description, contact details and retained diagnostic content, including a selected click trail, and the matching mailbox copy and attachment. The structured app-generated user-agent diagnostics are cleared under the shorter rule below. You can ask for earlier deletion under section 10. |
| Abuse-prevention fields and structured user-agent diagnostics | The IP hashes stored with requests and reports, the separate access-request user-agent field, and the app-generated browser user-agent in structured report diagnostics are cleared within 30 days of receipt. This includes matching emailed diagnostics and local copies we retain. If a copy cannot be scrubbed, we delete that copy rather than keep that diagnostic information beyond its deadline. |
| Activation, refusal and revocation records linked to an issued licence | No longer than the licence-record schedule above: while a key in the linked renewal chain remains current, then four years after the last key in that chain expires. Freeing, releasing or lapsing a seat does not itself erase its history. The revoking operator's identity in every revocation entry is cleared 12 months after revocation, or sooner if the whole entry is deleted. Undoing a revocation removes the current revocation entry; the separate action history follows its own 12-month deadline. |
| Operator-action records (freeing an installation, revoking a licence, undoing a revocation) | 12 months after each action, whether or not the key has a licence record, and earlier if the linked licence records reach their own deletion deadline. |
| Activation records for trials or other keys without a matching licence record | For an installation record, 12 months after the later of its last successful check-in and its release. For a refusal record, 12 months after the latest refused attempt for that renewal chain; the entire row and its up to 20 recent identifiers go together, so an identifier can remain longer than 12 months after that installation's own attempt if later valid attempts concern the same chain. Freeing a seat does not reset the installation record's check-in clock. A revocation entry is deleted 12 months after the later of revocation and the key's expiry. If the key has no expiry, or its expiry is unknown, the denial entry has no fixed deletion date and can remain indefinitely while needed to refuse the key. The revoking operator's identity is cleared 12 months after revocation, including for a key with no known expiry. An entry kept after that contains only the renewal-chain identifier, the revocation time and the key's expiry if known. These fields may remain linkable to other records; we do not treat them as anonymous. Malformed requests and requests using an unverifiable, expired or revoked key do not update these database records or extend these periods. This does not mean Cloudflare receives no request metadata. |
| Retired-request replay-prevention markers | After a request-origin access decision's personal records are deleted, we retain only its opaque request identifier permanently to prevent a delayed or repeated approval from issuing a key. No name, email, operator, signed key or retirement timestamp is kept in the marker. It may remain linkable through surviving records or copies; we do not treat it as anonymous. It is used only for replay prevention, with restricted access and a necessity review at least yearly, and remains subject to applicable privacy rights. Direct-issuance chain identifiers are not added to this permanent fence. |
| Update checks | Not kept. The update service answers each check without writing it to our databases or our application logs. Cloudflare edge and rate-limit data follow the next row. |
| Cloudflare edge and rate-limit data | Cloudflare receives IP addresses or network prefixes, key-identifier rate-limit keys and other request metadata. The configured rate-limit window is 60 seconds; it is not a deletion deadline for the keys or counters. Cloudflare does not publish a fixed maximum for every edge-data store. Its published retention criteria include delivering and securing its services, the sensitivity and amount of data, whether less data would suffice, and applicable legal obligations. Security analytics can remain available for at least 31 days; this is not a universal maximum. We do not copy these address-based counters into the activation tables. Cloudflare's privacy notice explains its processing. |
| Application logs we retain for operating our services | No more than 30 days, then deleted or aggregated so that they no longer identify you. Cloudflare's separate platform, edge-security, analytics and recovery records follow the provider criteria below and are not all subject to this application-log deadline. This does not set the retention policy of the third-party status service or of services you connect. |
| Analytics | Google keeps visit-level data under the random identifier for two months, then deletes it. Aggregate reports that identify no visitor remain while we keep the Analytics account. Analytics cookies expire 13 months after your last visit; you can delete them sooner. |
Our working copies. The schedules above govern our active database records and the mailbox, attachment, sent, trash and device copies we use for ordinary business. We remove or scrub those working copies at their deadline, including emptying the relevant trash rather than merely moving a message there. A database deletion does not delete its emailed or downloaded copies. Restricted provider recovery or preservation copies can remain after that action as described below. If we restore data, we reapply completed deletions and clearing before using the restored data for ordinary business.
Cloudflare recovery and email routing. D1's customer-accessible point-in-time recovery window is seven days on Workers Free or 30 days on Workers Paid, measured against past database states, so a pre-deletion or pre-clearing state can remain recoverable during that window. A deleted database also has a separate seven-day recovery facility. These are recovery windows, not assurances about physical erasure from every Cloudflare system. Cloudflare's internal recovery copies follow its applicable service and data-protection terms, tied to the need to provide its services and applicable legal requirements; no single fixed deletion period for all such copies is published. If Cloudflare's email-preview storage is enabled for routed messages, previews may retain request or report content for about seven days; delivery metadata follows its service/security retention criteria. See D1 recovery and Cloudflare's data-protection terms.
Resend. Resend publishes a 30-day retention period for email content, metadata, delivery events, logs and metrics on Free, Pro and Scale; Enterprise or custom arrangements can differ. It also documents seven-day point-in-time backups. Those are separate descriptions, not our promise of a combined 37-day erasure deadline or a verified start event. Delivery and recovery copies follow the applicable service's deletion process; security, account and legal records can follow different purpose-based periods. See Resend's retention description, security information and privacy notice. We do not treat deleting our send-attempt record as deleting Resend's copy.
Google Workspace recovery and preservation. Gmail normally retains a trashed message for up to 30 days unless it is permanently deleted sooner, and Workspace administrators may recover permanently deleted messages for a further 25 days. Google's published processing terms allow up to 180 days for system deletion after deleted data is no longer recoverable by the customer, subject to legal-storage exceptions; that is not a deadline measured from when we first receive a report. If Vault retention rules or holds apply, messages and attachments can remain after deletion from the ordinary mailbox, including indefinitely under an indefinite rule or until a hold is released. The retention criterion for those preserved copies is expiry of the applicable rule or lawful preservation need, release of the hold where applicable, and completion of Google's deletion process. We restrict their use to recovery or a justified preservation purpose, rather than continuing ordinary business use, and do not use an unnecessary rule or hold to extend our stated working-copy periods. See Google's processing terms and Vault retention information. Edition-dependent recovery and preservation features do not mean every account has Vault or that every message is on hold.
The scheduled automatic clears and deletions may run up to 24 elapsed hours before the stated deadline, including at month-end and around leap days, to meet that deadline. This is a maximum early window, not permission to shorten periods arbitrarily or retain data late. It does not move the 24-month open-request review forward, extend a period, or delete retained report content merely because its identifiers are due to be cleared.
For data collected under an earlier version of this notice, we honour any shorter retention period we promised when it was collected. This notice does not retroactively authorise new uses or cure a missed deletion deadline.
Where a specific legal obligation or an actual legal claim requires longer retention, we keep only the relevant minimum for that purpose, restrict its use and delete it when that need ends. That exception is not a routine extension of every request, declined decision or problem report. Any invoicing or accounting record required by law is kept for the applicable statutory period.
8. International transfers
We are based in the United States. We and the providers identified in section 6 process data in the United States and other countries where their services operate. Where applicable law requires safeguards for a transfer from the UK or EEA, we use an applicable adequacy decision or appropriate contractual safeguards, such as Standard Contractual Clauses and the applicable UK transfer instrument. We rely on a provider's Data Privacy Framework certification only for transfers covered by a current, applicable certification. Contact us for information about the safeguards relevant to your data.
Google Analytics does not load for visitors in the places listed in section 11.
9. Security
We limit access to production data to people who need it for the purposes in this policy. Licence-signing and IP-hashing secrets are kept in Cloudflare's managed secret storage, outside the source repository, and backup copies of those secrets are encrypted. A verification public key is public; a signed licence key is confidential but is not an encrypted container for the licensee's name and email address.
No system is perfectly secure. If a breach affects your personal data and the law requires it, we will notify you and the relevant supervisory authority without undue delay.
10. Your rights
Depending on where you live, you may have the right to access the personal data we hold about you, to have it corrected or erased, to restrict or object to its processing, to receive it in a portable format, and to withdraw consent where processing relies on it. Exercise any of them using the contact details in section 14; we will respond within the time the law allows, and we may need to verify your identity first.
California residents. We do not sell or share your personal information, as the California Consumer Privacy Act defines those terms. We do not ask you to include sensitive personal information in an access request or problem report. If you choose to include it in a report, we use it only to investigate that problem, not to infer characteristics about you. You can use the rights in this section whether or not that law applies to us, and we will not treat you differently for using them.
Erasure can be limited where applicable law allows or requires us to keep data for a specific purpose, such as a legal retention obligation or a necessary, proportionate security record. If we cannot erase a record, we explain the applicable basis and keep only the relevant minimum. The replay-prevention marker in section 7 is not automatically exempt from your rights merely because its identifier is opaque.
If you are unhappy with how we have handled your data you may complain to the data-protection authority where you live or work — in the UK, the Information Commissioner's Office.
12. Children
Patch is a business tool for adults and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us their data, contact us and we will delete it.
13. Changes to this policy
We may update this policy. The version date at the top always reflects the current text, and we will give notice by email at least 30 days before a change that materially affects how we use data you have already given us.
14. Contact
Privacy questions and rights requests go to privacy@patchcove.com, or by post to 3705 W Pico Boulevard #1, Los Angeles, California 90019, United States.
See also the Terms of Service.