Skip to content
TQ CORES Isotipo
TQ CORES
|
Back to portfolio

TQCores / Site information

Privacy policy

You can explore this portfolio without an account. This policy explains what data is involved, its purposes, retention and your rights. Optional metrics require your permission.

Last updated: 15 October 2026 · Version 2026-10-15.2

  • Enquiries without marketing
  • Limited retention
  • Metrics disabled by default

On this page

  • Controller and scope
  • Data and sources
  • Contact purpose and authorisation
  • Other uses and legal grounds
  • Recipients and international processing
  • Optional metrics and local storage
  • External resources and links
  • Retention and deletion
  • What you can request and how
  • Procedure until November 2026
  • Procedure from December 2026
  • Minors and automated decisions
  • Security, incidents and changes

Controller and scope

Tomás Ignacio Quiñelén Jiménez, responsible for TQCores and this professional portfolio, in Chile. For privacy and data rights, email contactousr@pm.me; you do not need to use the form.

This policy covers visitors, people enquiring about employment, collaborations or potential services, and people exercising data rights. Browsing does not create visitor accounts or a customer database.

Until 30 November 2026, Law 19.628 applies in its current form. Amendments under Law 21.719 take effect on 1 December 2026. Procedures for each period are distinguished below; future rules are not presented as already in force.

  • Law 19.628 · official text (Spanish)
  • Law 21.719 · reform and commencement (Spanish)

Data and sources

Contact: name, reply email, message and information you voluntarily include. This comes directly from you. Form emails include authorisation and the policy version; the provider supplies date and delivery records. Lists are not purchased and enquiries are not extracted from public registers.

Browsing: your browser communicates data needed to request pages and resources, such as IP address, browser, requested resource and date. Infrastructure providers may log it to deliver and protect the site. Optional metrics add usage and performance information if enabled.

The form does not request national identification numbers, identity documents, passwords, banking, biometric, health or other sensitive data. Avoid including them, confidential information or third-party data you cannot lawfully share. Unnecessary information received will have its use limited and deletion managed where appropriate.

Contact purpose and authorisation

Name, email and message are used to reply, follow up and retain the conversation while needed for that purpose. They are not sold or used to subscribe you to marketing. Providing them is voluntary; a valid reply email and message are needed to process the form.

The basis is informed consent: article 4 of Law 19.628 and, from December 2026, amended article 12. It is requested before sending through an unchecked box, separate from metrics. You can review and cancel. The electronic record documents your declaration; it does not by itself certify identity or constitute an advanced electronic signature.

Withdraw permission at any time by emailing contactousr@pm.me, free of charge and without justification. Processing based solely on that permission will stop, without retroactive effect on previous lawful uses. Any separate legal basis for retaining part of the information will be identified and explained.

Drafts, history and terminal files remain in page memory. Reloading or closing discards that state. Cancelling clears the form, although text may remain in history until reset or closing. A message is transmitted on confirmation; the portfolio does not create a message database.

Other uses and legal grounds

Technical delivery and protection of the site are limited to what those tasks need. They are not used for advertising, cross-site tracking or personal assessment of visitors. The absence of cookies does not by itself mean that no personal data exists.

From 1 December 2026, pre-contractual steps you request or a contract may rely on article 13(c); a specific legal obligation on 13(b); and establishing, exercising or defending rights before courts or public bodies on 13(e). Each requires necessity and a demonstrable basis; they do not authorise indefinite retention of every enquiry.

If technical processing relies on future legitimate interests under article 13(d), the interest —such as site continuity and abuse prevention— must be identified and assessed against your rights. It is not general permission for optional metrics or incompatible uses. You can request information about that basis and object where the law provides.

Recipients and international processing

The controller accesses enquiries. Resend transmits the form; Google through Gmail and Proton Mail receive and reply depending on the channel. Website hosting and execution providers handle connections and the form’s passage. Only necessary information is communicated for each service. Messages and private destination mailbox addresses are not published.

Processing may occur outside Chile. Resend states that it processes data in the United States; Google uses international infrastructure. Proton Mail reports servers in Switzerland, Germany and Norway. Web infrastructure and subprocessors may operate from other countries. These references are not a complete inventory of every copy or an exclusive route guarantee.

No adequacy under Chilean law or specific contractual safeguards are claimed without verification. From December 2026, habitual transfers need a basis under articles 27 and 28 and destination and safeguards information. The contact checkbox does not replace that basis or generally authorise every international transfer.

Request information about recipients, origin and destination using the privacy email. Using providers does not remove responsibility for processing decisions made in this portfolio. Their policies also explain processing for which they are independently responsible.

  • Resend privacy
  • Google privacy
  • Proton Mail privacy

Optional metrics and local storage

Usage and performance metrics are disabled by default and enabled only when you check this section’s control. They help understand visited pages, general interactions, performance, browser, device and approximate country; precise location is not requested. Refusing or withdrawing permission does not prevent browsing or contact.

Custom terminal events include only recognised command names or “other” and the general sending result. Names, emails, messages and private arguments are deliberately excluded. Query strings and fragments are removed from measured URLs. This does not guarantee absolute anonymity of every connection.

Withdraw permission by unchecking the same control. Global Privacy Control and Do Not Track keep metrics disabled while active. The control prevents new events; it does not retroactively delete events already sent or necessary hosting logs.

The preference is saved as tqcores_metrics with the permission version. Old or unknown preferences do not enable metrics. If saving fails, your choice lasts only until reloading or closing the page; returning reads any preference the browser previously retained. Language may be saved as tqcores_lang. These are not advertising cookies; clear both through your browser’s site data settings to return metrics to their disabled state.

Disabled in this browser. Contact remains available.

If your browser cannot save changes, the choice lasts until reloading or closing this page. Returning uses any previously saved preference.

External resources and links

The site loads Google Fonts, jsDelivr and Simple Icons resources, and a Transparent Textures image. Your browser communicates connection data such as IP address and browser to them, including when metrics are off. The cryptocurrency panel requests public Binance prices only on opening that workspace; this also connects to that provider.

GitHub, LinkedIn, certificates, demonstrations and other external links have their own policies. Clicking a link takes you to that service. Contact details are not deliberately sent to those sites as part of browsing.

Retention and deletion

An enquiry is retained while open and necessary. Closed enquiries have a maximum retention of 12 months after the last interaction. This is a portfolio limit, not a statutory minimum: data will be deleted earlier if no longer needed, a request requires it or you withdraw the only processing basis.

For a contract, specific legal obligation or claim, only necessary information is retained for the applicable period with limited access. Restrictions on deletion will be explained. From December 2026, the specific duty under article 14(d) to delete or anonymise data collected for pre-contractual steps also applies; the 12-month maximum will not automatically apply to that data.

Deletion is managed in mailboxes and services; this website does not run an email deletion task. Delivery, security and metrics logs have provider cycles requiring verification against actual configuration. They are not assigned the enquiries’ period, and a dashboard reporting window is not treated as deletion of every copy.

Backups do not necessarily disappear when a message is deleted. Proton Mail states backups last up to 30 days; other services may have different cycles and legal obligations. Requests are managed with providers where appropriate. Drafts last for the open page; local preferences remain until changed or cleared.

What you can request and how

Email contactousr@pm.me with your name, a reply channel and request. To locate an enquiry, include the email used and an approximate date. Access needs no justification. Identify your authority if representing another person. Only necessary and proportionate identity checks will be requested, without routinely requiring a full identity document.

Access and information: what data exists, its source, purpose and recipients. Rectification: correct inaccurate, incomplete or outdated data, specifying changes and relevant evidence. Erasure or cancellation: request deletion for lack of basis, expiry or an ended purpose, among other legal grounds. Blocking: temporarily prevent use in applicable cases.

From December 2026, objection is broadened under article 8 and portability is introduced under article 9. Portability requires data supplied by you, automated processing and consent: it allows a structured, commonly used copy and direct transmission where technically feasible; it does not itself erase the original. For erasure or objection, identify the processing and applicable reason with supporting information where relevant.

Objection allows you to ask for specific processing to stop. Future article 8 covers legitimate interests, direct marketing and public-source data without another basis. For legitimate interests, use must stop unless overriding compelling legitimate grounds apply or processing is needed to establish, exercise or defend claims. Withdrawing consent is a separate route and does not require justifying an objection.

The portfolio does not charge for handling these requests. A full or partial refusal will explain its grounds and evidence in writing. Recipients will be informed of corrections, deletions or restrictions where required. Visiting, accepting this notice or enquiring does not waive your rights.

Procedure until November 2026

Current Law 19.628 provides information and access, amendment, deletion or cancellation and blocking under articles 12 and 13. Article 3 also allows objection to advertising, market research or opinion surveys, although this portfolio does not use your enquiries for those purposes. Article 16 allows an application to the civil court at the controller’s domicile if no decision is given within 2 business days or a request is refused, with special rules for national security or national interest grounds.

The 2-business-day period must not be confused with the future 30-calendar-day period. Complaints to the new Agency belong to the December regime; a future administrative procedure is not required to exercise current rights.

  • Law 19.628 · articles 12, 13 and 16 (Spanish)

Procedure from December 2026

Amended articles 10 and 11 provide acknowledgement and a written response within 30 calendar days of receipt. They allow one extension of up to another 30 calendar days. If used, it will be communicated and explained; it is not automatic. The necessary record of the response’s content and dispatch is retained.

Following refusal or expiry without a response, you may complain to the Personal Data Protection Agency within 30 business days of the response or deadline, under articles 11 and 41. A refusal must inform you of that route and period.

Reasoned temporary blocking accompanying rectification, erasure or objection has a separate deadline: 2 business days after receipt. Covered data will not be processed while that blocking request is resolved; blocking does not prevent storage. A refusal must be reasoned and electronically communicated to the Agency, and you may complain.

  • Reform · articles 8 ter, 10, 11 and 41 (Spanish)

Minors and automated decisions

The site has a professional purpose and is not directed at children. It does not ask for or documentarily verify age. For an enquiry concerning a minor, avoid unnecessary data and use the privacy email to address appropriate representation.

From December 2026, article 16 quáter generally requires consent from a parent, legal representative or person with personal care for children under 14, unless authorised by law. Adolescents aged 14–17 follow general authorisation rules; sensitive data concerning those under 16 requires consent from those persons unless a legal exception applies. This does not authorise requesting sensitive data in the form.

No solely automated decisions with legal or similarly significant effects are made about visitors, nor personal profiles for employment, credit or engagements. Format checks and sending limits do not assess your personal situation. If they prevent contact, use the public email. Introducing such decisions would require prior explanation of their logic, effects and safeguards, including human intervention.

Security, incidents and changes

The service validates types, length and format, requires current authorisation on the server and limits bursts per instance without recording IPs in that counter. The public site uses HTTPS. Form data is deliberately excluded from metrics events. Email passes through providers and is not end-to-end encrypted between visitor and controller: do not send information needing another channel.

Confidentiality and limited access continue after closure. An incident requires assessment of its scope and affected data to contain it and meet applicable obligations. From December 2026, article 14 sexies requires reporting to the Agency without undue delay where there is reasonable risk to rights and freedoms, recording its nature, effects, affected data and people, and measures taken. It also requires notification to affected people for sensitive data, data about children under 14 or economic, financial, banking or commercial obligations, clearly explaining affected data, consequences and protective measures. This is not replaced by a universal 72-hour period.

Material changes will be published with a date and version. New purposes requiring permission will be requested separately; browsing or silence is not authorisation. This policy does not certify compliance or replace contracts, account security or actual deletion.

  • Reform · transparency, security and incidents (Spanish)

A direct point of contact

For privacy requests, permissions or questions about this site:

contactousr@pm.me
PrivacyUse and authorship

© 2026 Tomás Quiñelén · TQCores