paryx.uk

Privacy Policy

Last updated: 1 November 2026

This policy explains what information is processed when you use paryx.uk, why it is processed, and the choices and rights you may have. The site is designed to collect as little information about visitors as reasonably possible.

The short version

paryx.uk does not have user accounts, advertising, behavioural profiling, or a contact form. It does not sell or rent personal data. Cloudflare sits in front of Vercel to secure, deliver, and optimise site traffic, basic site-usage and real-world performance analytics are provided through Cloudflare Web Analytics, and Sentry is used only for error monitoring. I have opted out of all optional Vercel data-sharing and model-training settings under my control.

Who is responsible for the site

I operate paryx.uk. I decide how personal data that I directly control through this website or direct email contact is used.

Privacy questions, data-rights requests, or privacy concerns can be sent to privacy@paryx.uk. General enquiries can be sent to paryx@paryx.uk.

Information that may be processed

Analytics and performance measurement

paryx.uk uses Cloudflare Web Analytics / Real User Measurement (RUM) to understand aggregate site usage, diagnose problems, and measure how pages perform for real visitors. I do not use this information for advertising, cross-site behavioural profiling, data brokerage, or AI or machine-learning model training.

Depending on the feature, analytics and performance information can include page views and visits, referrer information, approximate location, browser, operating system and device type, and page-load or Core Web Vitals performance metrics.

Cloudflare Web Analytics / RUM measures page usage and real-world loading performance using browser performance APIs. Cloudflare states that its RUM beacon does not use cookies or browser storage, does not track visitors across Cloudflare customer sites, and discards the source IP address received by the RUM request at the nearest Cloudflare data centre rather than storing it in the RUM service's core databases or logs. This RUM handling is separate from normal Cloudflare proxy, security, and infrastructure request processing described elsewhere in this policy.

Error monitoring

The API, blog, and main website use Sentry, provided by Functional Software, Inc., to report application errors and diagnose failures. Sentry receives an event when an uncaught browser error or unhandled promise rejection occurs, when an API handler throws, or when an API failure is explicitly reported by the application.

Each event is limited to an event identifier, timestamp, severity, platform, exception type and message, stack frames (source filename, function, and line and column numbers), application name, and Sentry SDK name and version. Where configured, it also includes the deployment environment and release identifier. Browser events additionally include the browser's user-agent string, the browser-reported platform string, and the current page path. API events additionally include the Node runtime name and version, operating-system platform name and version, and a fixed endpoint label, not the full request URL.

The SDK removes query strings and fragments from source filenames and does not send request or response bodies, request headers, cookies, account identifiers, console output, clicks or other interaction breadcrumbs, session replays, or performance traces. It does not attach an IP address to an event. Functional Software may process connection metadata, including the source IP address, to receive and deliver telemetry. Common credential patterns, email addresses, and IPv4 addresses in exception text are redacted before an event is sent; other text included by an unexpected exception may still appear in its error message or stack.

Error events are used only to investigate and fix technical problems. Functional Software processes the telemetry on our behalf under its own Privacy Policy. Sentry is not used for user analytics, advertising, session replay, or performance measurement.

How information is used

Information is used only where reasonably needed to:

I do not use analytics or personal data for advertising, data brokerage, behavioural profiling, or AI or machine-learning model training.

Lawful basis

Where UK data protection law applies, processing needed to run, secure, maintain, and provide the site is generally carried out on the basis of legitimate interests. Those interests are operating a reliable personal website, protecting it from abuse, and providing the features visitors request.

Information you send by email is processed as necessary to respond to your request and manage the resulting correspondence. If a future feature requires consent, consent will be requested before that processing begins where required by law.

Cookies and similar storage

paryx.uk does not intentionally set advertising cookies. Cloudflare Web Analytics / RUM is designed to provide analytics without analytics cookies, and Cloudflare's RUM beacon does not use browser storage. The homepage uses browser localStorage only to cache public GitHub repository data as described above.

Third-party services used by the site operate under their own privacy and storage practices. You can clear local storage and cookies through your browser settings at any time.

Optional data collection and sharing

I have opted out of all optional Vercel data-sharing and AI or machine-learning model-training settings under my control. Cloudflare Web Analytics / RUM is the visitor analytics and performance-measurement feature I intentionally enabled. Sentry is separately enabled for error-only diagnostics as described above.

This does not disable technical processing that is necessary to host, secure, deliver, and troubleshoot the website, because that processing is required for the service to operate.

Third-party services

The site currently relies on or connects to the following services for specific features. Where a dedicated privacy notice is available, it is linked directly:

These providers may process technical information independently under their own privacy practices. paryx.uk is not responsible for the privacy practices of external websites you choose to visit through links on the site.

Sharing and sale of data

Personal data is not sold, rented, or shared with advertisers or data brokers. I do not use analytics and performance data for advertising, cross-site behavioural profiling, or AI or machine-learning model training. I have opted out of optional Vercel data-sharing and model-training settings under my control. Information is shared only with service providers such as Sentry, Cloudflare, and Vercel where needed to secure, deliver, optimise, operate and analyse the site, respond to communications, comply with a legal obligation, or protect the site and its users.

International processing

Some service providers I use operate internationally. As a result, technical information may be processed outside the United Kingdom. Where applicable, those providers are responsible for using appropriate legal safeguards for their processing and transfers.

How long information is kept

paryx.uk does not maintain its own visitor-profile database. Browser-side repository cache entries are treated as current for up to one hour but may remain on your device until they are refreshed or cleared. Vercel states that the temporary visitor identifier used by Web Analytics is discarded after 24 hours. Cloudflare states that the source IP received by its RUM beacon is discarded at the nearest Cloudflare data centre and is not stored in the RUM service's core databases or logs. Aggregated analytics and provider infrastructure, security, and operational data are retained according to the relevant service settings and privacy practices.

For information I directly control, ordinary enquiry emails are retained for up to 12 months after the last relevant message. Correspondence relating to privacy or data-rights requests is retained for up to 24 months after the request is closed so I have a record of how I handled it. Information may be kept longer where reasonably necessary for an ongoing issue, security investigation, legal obligation, or legal claim, and may be deleted earlier when it is no longer needed.

Your rights

Depending on the circumstances and applicable law, you may have rights to request access to personal data, correction, deletion, restriction of processing, data portability, or other information about how your data is used.

You may also have the right to object to processing based on legitimate interests. To make a privacy or data-rights request, email privacy@paryx.uk.

If you are in the UK and believe your data protection rights have been breached, you can also complain to the Information Commissioner's Office.

Children's privacy

The site is a general personal developer website and is not designed to collect personal information from children through accounts, forms, advertising, or profiling. If someone contacts Paryx directly, only the information they choose to provide is received and it is handled as described in this policy.

Security

Reasonable technical and organisational measures are used to reduce the risk of unauthorised access, alteration, loss, or misuse. No internet service can guarantee absolute security, so only send information by email that you are comfortable providing.

Changes to this policy

This policy may be updated when the website, its integrations, or legal requirements change. The latest version will always be published at this address with the updated date shown near the top.

Contact

For privacy questions, data-rights requests, or privacy concerns, contact privacy@paryx.uk. For general enquiries, contact paryx@paryx.uk.