Privacy Notice

What personal data the current SiliconJury service processes, why it is used, where essential storage applies and how to make a privacy request.

Last updated:

Scope and responsible publisher

This notice applies to the public SiliconJury website, accounts, authentication, comments and the public concern workflow. SiliconJury is identified here as the publisher and operator responsible for these activities. A separately incorporated legal-entity name, registered address and jurisdiction have not been authoritatively configured for publication, so this notice does not invent them.

If a specific law requires additional controller or representative details for your request, use the privacy category in the monitored concern form. The request can then be assessed in context without exposing sensitive information publicly.

Personal data we process

  • Account and authentication data, such as an account identifier, name, email address, password hash, session and security information.
  • Optional Google sign-in data returned by Google when a user chooses that method, limited to the information needed to authenticate and connect the account.
  • Comments and associated account, moderation and timestamp information when a signed-in user submits a comment.
  • Contact, correction, complaint, rights and privacy submissions, including case details, contact information, evidence supplied and workflow history.
  • Server and security logs, such as IP address, request time, route, device or user-agent information, error and abuse signals.
  • Authenticated administrative interface preferences stored locally on the user’s device.

The ordinary concern form should not be used for identity documents, passwords, confidential legal files or unnecessary sensitive personal data. If verification is genuinely required, a more appropriate follow-up method will be arranged.

Purposes and lawful bases

Data is used to create and secure accounts, provide sign-in, display and moderate comments, receive and investigate concerns, communicate about a case, maintain editorial and rights records, prevent abuse, diagnose failures and operate the service.

The lawful basis depends on the activity and applicable law. It may include providing a service or taking requested steps, legitimate interests in operating a secure publication and responding to concerns, compliance with legal obligations, protection of legal rights, or consent where consent is the appropriate basis. Choosing Google sign-in authorizes that authentication flow; it is not consent to advertising or unrelated profiling.

Cookies and local storage

The current service uses essential authentication or session cookies and locale storage needed to keep a user signed in securely and remember language routing. These are not used for advertising. Authenticated administrative interfaces may use browser local storage to remember workspace or display preferences on that device.

Public playback telemetry does not add cookies or persistent visitor identifiers. Official YouTube players connect your browser to YouTube before playback and may store or process information when you interact with them, as explained below. This notice and the consent interface must be updated before non-essential tracking or similar technology is enabled where consent is required.

Analytics, advertising, newsletters and embeds

Public player update — 8 October 2026

Public episode pages now include official YouTube embeds in privacy-enhanced mode. Loading an episode page connects your browser to YouTube before playback; playback remains your choice. YouTube may process your IP address, device information and viewing activity, and may store information when you interact with the player. You can instead use the Watch on YouTube link. Public playback telemetry records event totals without account identifiers, cookies, IP addresses or persistent visitor IDs. Existing account and concern-form processing is unchanged.

Processors, recipients and international transfers

Personal data may be available to authorized SiliconJury operators and to infrastructure, database, security or authentication providers that support the service. Google receives and returns authentication data only when a user chooses Google sign-in. Information may also be disclosed when reasonably necessary to comply with law, protect users or rights, investigate abuse, or establish or defend legal claims.

Service providers and users may be located in different countries, so processing can involve an international transfer. Where applicable law requires a transfer mechanism or additional safeguard, SiliconJury will assess and apply the mechanism appropriate to the provider, countries and data involved. This notice does not claim a safeguard that has not been verified for a specific transfer.

Retention and deletion

The current application does not apply an automated retention or deletion schedule to account, comment or concern-case records, and no fixed period is published that the operation cannot substantiate. Records may therefore remain in primary storage and backups until an authorized operator completes a case-by-case review.

A deletion or anonymization request is reviewed manually against account and service operation, security, dispute and case history, editorial accountability, rights records, backup integrity, fraud-prevention, legal-hold and applicable legal needs. A valid request may not erase a minimal record needed to document a resolved complaint or comply with law. A documented retention schedule and automated lifecycle remain an operational gap.

Security and access

SiliconJury uses measures intended to reduce unauthorized access, loss and misuse, including encrypted transport, password hashing, authenticated access controls, restricted administrative access, server-side validation, abuse controls and security logging. No internet service can promise absolute security.

Please report a suspected account or data-security issue through the privacy category without publishing credentials, exploit details or personal data in a public comment.

Your choices and privacy rights

Depending on where you live and the law that applies, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent or review of a decision about your personal data. These rights can have legal exceptions and identity verification may be required.

You may also manage local browser storage through your browser, choose password sign-in instead of Google where available, and avoid posting personal data in comments. Withdrawing consent does not invalidate processing that was lawful before withdrawal.

Privacy requests and complaints

Use the privacy category in the monitored concern form. Describe the request, the account or content involved and a safe way to reply; do not send identity documents initially. If identity or authority must be confirmed, a more secure follow-up path will be provided.

You may also have the right to complain to a competent data-protection or privacy authority. Because this notice does not invent a governing jurisdiction, it does not name an authority that may not be relevant to you.

Submit a concern