Privacy Policy

DRAFT. This is not a final document. This privacy text is pending review by qualified counsel. It is not a lawyer-approved final policy, and it is not legal advice. Do not treat it as the operative privacy policy of a production commercial operation of Opalaxy S.A.S.

This document describes, with website-limited scope, how this draft frames personal data, browser storage, and core legal notices for the intended Opalaxy S.A.S. website model: public navigation, a browser-side contact draft, and temporary local storage used to support that flow.

Assumption: the Opalaxy website is not yet published. This draft carries the same website-limited model. It does not report an audit of an Opalaxy codebase, and it does not describe internal delivery, invoicing, contracting, or support processes.

Last updated 22 October 2026

Stated identity for this draft

These are the only identity facts used in this adaptation. They are not a registry extract.

Legal name, as stated: Opalaxy S.A.S.
NIT, as stated: 902118918-6
Place: Cali, Colombia
Email: support@opalaxy.com
WhatsApp: +57 3154694934
WhatsApp: +57 3175270029

No street address, legal representative, chamber of commerce, or other registry field is added. RUES was not confirmed.

Part I: Privacy and Personal Data Treatment

This part explains the personal-data treatment described for the intended website model. Its scope is limited to public website navigation, the contact workflow implemented in the browser, and the temporary local storage used to support that workflow.

It does not claim to describe internal delivery, invoicing, contracting, or support processes. If the website later adds server-side intake, analytics, cookies, or additional integrations, this policy should be updated accordingly.

1.1

Purpose and scope of this policy

Opalaxy S.A.S. publishes this draft to explain how the intended website model handles personal data, browser storage, and outbound third-party interactions. The policy is written with Colombia-first privacy framing, while keeping the description tied to that website model rather than to an audited production site.

The policy applies to visitors who browse the website, use the contact form, open the draft-email preview flow, store theme or language preferences, or follow outbound links to third-party services from this site.

This document is intentionally limited to the website model described here and should not be read as a complete data-processing manual for any broader consulting or managed-services operation.

1.2

Definitions

For this website model, the following terms are used in a practical sense so visitors can understand how the described flow works.

Personal data: information that identifies or can reasonably be associated with a natural person, such as name, email address, phone number, or message content.

Processing: any action performed on personal data, including collection, consultation, organization, storage, use, deletion, or disclosure.

Data subject: the person whose personal data is entered into the website or related contact flow.

Browser storage: information stored locally in the visitor's browser, including localStorage entries used by the described website experience.

Third-party service: an external provider opened by the user from this site, such as Gmail, Outlook, WhatsApp, or Google Maps.

1.3

Applicable principles

Opalaxy S.A.S. seeks to structure the described website experience in a manner consistent with the general principles recognized in the Colombian personal-data protection framework, especially the principles of purpose limitation, freedom, restricted access, accuracy, security, and confidentiality.

Purpose limitation: data should be used only for the specific website functions explained to the visitor.
Data minimization: the website should request only the information needed to prepare the contact draft and related user actions.
Freedom and user control: the visitor chooses whether to fill the form, keep local browser data, or continue to a third-party provider.
Security and confidentiality: reasonable technical measures should be used to avoid improper disclosure within the scope of the described website flow.
Accuracy: visitors should provide current and truthful contact information if they choose to use the form.

1.4

Published responsible-party details

For the purposes of this website draft, the responsible-party reference is limited to the identity facts stated for this adaptation.

Published operator name: Opalaxy S.A.S.

NIT, as stated: 902118918-6

Email: support@opalaxy.com

WhatsApp: +57 3154694934 and +57 3175270029

Reference location: Cali, Colombia

This section uses only those stated facts. It does not add a street address, a named legal representative, a chamber of commerce, or any other registry field. RUES was not confirmed. Stating the NIT is not a registry extract and is not a certification.

1.5

Categories of data handled by the described website model

Based on the website model carried into this draft, the website can handle a narrow set of contact and preference data chosen by the visitor.

Name entered into the contact form.
Company name entered into the contact form.
Email address entered into the contact form.
Phone number entered into the contact form when the visitor chooses to provide it.
Primary service interest selected in the contact form.
Project or consultation context written in the message field.
Theme preference stored locally in the browser.
Language preference stored locally in the browser when the visitor explicitly selects a site locale.
Temporary email-draft data stored locally in the browser, including recipient, subject, body, and draft creation timestamp.

1.6

How data is collected

The described website model does not include a server-side contact submission endpoint. Instead, the contact flow collects data in the browser and uses it to assemble a draft message locally before the visitor decides whether to continue to an external mail provider.

Visitors type contact information directly into the browser form.
When the form is submitted, the website creates a draft email locally in the browser.
The draft preview page reads that temporary local data so the visitor can review it.
Theme preferences are stored locally when the visitor changes the site's theme.
Language preference is stored locally when the visitor explicitly changes the site's locale.
If the visitor clicks Gmail, Outlook, WhatsApp, or Google Maps, the relevant data or navigation context may then be handled by that third-party provider under its own terms and privacy practices.

No street address is published in this draft. A location reference, if a later page includes one, is limited to Cali, Colombia.

1.7

Purposes of use

Within the described website flow, Opalaxy S.A.S. uses the data only to support user-requested site functionality and direct outbound communication choices made by the visitor.

Prepare a consultation or contact draft based on the information the visitor enters.
Display the draft preview so the visitor can confirm the content before leaving the site.
Preserve the selected visual theme across visits in the same browser.
Preserve the selected site language across future visits in the same browser when the visitor switches locales manually.
Allow the visitor to continue voluntarily to Gmail, Outlook, WhatsApp, or Google Maps.
Provide a clear, lightweight contact path without transmitting the form automatically to a dedicated Opalaxy S.A.S. backend. No such backend is described in this draft.

1.8

Colombia-first legal framing

Opalaxy S.A.S. interprets this website draft with reference to the Colombian personal-data protection framework, including Law 1581 of 2012 and its applicable regulatory development, in a way that matches the website model described here.

Official text of Law 1581 of 2012: https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=49981

This citation records the framework already used in the source placeholder. It does not add a new processing purpose, a new retention rule, or a certification.

Because the described model performs much of the contact flow inside the visitor's own browser, several operations depend first on the visitor's voluntary action, such as filling the form, keeping local browser data, or continuing to an external provider.

Voluntary entry of contact data functions as the user's own initiation of the contact flow.
Local browser storage is used to support user-requested functionality rather than a hidden profiling or analytics workflow.
If the visitor continues to an external provider, that provider becomes responsible for its own independent processing under its own policies.

1.9

Retention and deletion approach

The described website model keeps only limited local browser data.

Temporary email drafts created by the site are stored in localStorage and are designed to expire after approximately 30 minutes.
Expired email drafts are removed by the website when the draft flow is revisited.
Theme preference remains in the browser until the visitor changes it or clears browser storage.
Language preference remains in the browser until the visitor changes it or clears browser storage.
No dedicated server-side Opalaxy S.A.S. contact database is described in this draft for automatic storage of the form fields themselves.

1.10

Recipients and disclosure scenarios

In the described website model, personal data is not transmitted automatically from the contact form to an Opalaxy S.A.S. server endpoint. Disclosure occurs mainly when the visitor chooses to continue to third-party tools.

The visitor's own browser, through localStorage used for temporary draft, theme, and language persistence.
Gmail or Outlook, if the visitor chooses one of those compose flows.
WhatsApp, if the visitor chooses a direct WhatsApp contact link. The stated WhatsApp numbers are +57 3154694934 and +57 3175270029.
Google Maps, if the visitor opens a location link. This draft does not add a street address.

No first-party analytics platform, CAPTCHA integration, or server-side form-submission service is described in this draft.

1.11

Data of minors

The website model is intended for business and professional contact contexts. It is not designed specifically for minors, and Opalaxy S.A.S. asks users not to submit the personal data of minors through this contact flow without appropriate authorization and legal basis.

If a parent, guardian, or authorized representative believes information related to a minor was entered inappropriately, Opalaxy S.A.S. should be contacted at support@opalaxy.com so the situation can be reviewed.

1.12

Rights of the data subject

Within the Colombian framework and subject to the actual scope of processing performed by the website, visitors may seek to exercise the rights applicable to their personal data.

To know whether personal data is being processed within the website flow described here.
To request access, update, or rectification of data that the visitor has already shared through the contact flow.
To request deletion or revocation where applicable, especially when the request concerns data held or controlled by Opalaxy S.A.S. and not merely stored inside the visitor's own browser.
To ask how the website uses the information described in this policy.
To clear local browser data directly from the browser when the information is stored only in localStorage on the visitor's device.
To submit questions or complaints and, where applicable, seek guidance or file complaints before the Colombian data-protection authority.

1.13

Questions, complaints, and policy updates

Questions about this website privacy draft or the described contact flow may be sent to support@opalaxy.com. Opalaxy S.A.S. may update this document when the website changes its technical behavior, adds integrations, or publishes additional corporate information that has actually been stated.

Nothing in this section should be read as a waiver of mandatory rights or procedures established by applicable Colombian law.

Part II: Cookies and Browser Storage

The website model described in this draft uses browser-side storage that is more accurately described as local browser storage than as an extensive cookie program. This part distinguishes those concepts and explains what this draft describes.

2.1

Difference between cookies and local browser storage

Cookies are small data files usually managed by the browser and sent with requests under specific technical rules. localStorage, by contrast, is browser-side storage that remains on the device and is not automatically transmitted with every request in the same way as a cookie.

The described website model uses localStorage for certain convenience functions. This draft does not state that the site actively configures a broader analytics or marketing cookie stack, because no such stack is described here.

2.2

Browser-side storage described for this website model

The website model uses limited local browser storage for user-requested functionality.

Theme preference: stored locally so the site can remember whether the visitor selected the light or dark theme.

Language preference: stored locally when the visitor explicitly changes the site language so future visits to default-language routes can keep that choice.

Temporary email draft: stored locally so the visitor can review a generated draft before continuing to Gmail or Outlook. The draft includes recipient, subject, body, and a creation timestamp, and is designed to expire after about 30 minutes.

2.3

Third-party services and storage outside this site

If the visitor chooses to continue from this site to Gmail, Outlook, WhatsApp, or Google Maps, those external services may use their own cookies, storage technologies, or tracking mechanisms under their own policies.

Opalaxy S.A.S. does not represent those external storage practices as part of this website policy and recommends reviewing the relevant provider policies before using those services.

Gmail compose flow
Outlook compose flow
WhatsApp direct-contact link
Google Maps location link, without a street address added in this draft

2.4

User controls

Visitors may manage browser storage using their own browser controls, privacy modes, or device settings.

Clear local browser storage or site data from the browser settings.
Use private or incognito browsing modes where available.
Disable or restrict site storage through browser privacy controls if the browser allows it.
Avoid continuing to third-party providers if the visitor does not want those services to receive the relevant contact or navigation data.

Restricting local browser storage may affect theme persistence, language persistence, and the draft-email preview experience.

Part III: Website Legal Notice

This part provides a practical legal notice for this website draft using only the identity facts stated above.

3.1

Site identification

The website draft is published under the name Opalaxy S.A.S. and presents the stated business contact channels for technology and consultation-related communications.

Published name: Opalaxy S.A.S.

NIT, as stated: 902118918-6

Email: support@opalaxy.com

WhatsApp: +57 3154694934 and +57 3175270029

Reference location: Cali, Colombia

No street address, legal representative, chamber of commerce, or other registry field is added. RUES was not confirmed.

3.2

Intellectual property

Unless a different owner is expressly identified, the texts, designs, branding, layout decisions, and software elements published on this site should be understood as belonging to Opalaxy S.A.S. or to the respective lawful rights holder.

No part of this website should be reproduced, distributed, altered, or reused beyond the limits allowed by applicable law without prior authorization from the relevant rights holder.

3.3

External links and third-party services

This site model includes links and outbound actions that may take the visitor to external services, including Gmail, Outlook, WhatsApp, and Google Maps. Once the visitor leaves the Opalaxy S.A.S. site environment, the relevant third-party provider controls its own content, terms, privacy practices, and security measures.

Opalaxy S.A.S. does not guarantee the accuracy, availability, or privacy practices of third-party sites that are not under its direct control.

3.4

Availability and reasonable limitation of responsibility

Opalaxy S.A.S. seeks to keep the website available and technically functional, but does not represent that the site will always be uninterrupted, error-free, or free from external failures beyond reasonable control.

To the extent permitted by applicable law, Opalaxy S.A.S. is not responsible for damages arising solely from failures in third-party services, user-side connectivity issues, or unauthorized acts by external parties that fall outside the normal control of this website implementation.

This limitation remains a draft statement. It has not been converted into a counsel-approved liability clause, and no liability cap or indemnity is added here.

3.5

Applicable law and competent authorities

This website draft is written with a Colombia-first legal perspective and should be interpreted in a manner consistent with applicable Colombian law, without disregarding any mandatory rules that may apply in a specific case.

For privacy-related matters, visitors may contact Opalaxy S.A.S. directly first at support@opalaxy.com. Where applicable, visitors may also seek recourse before the Superintendence of Industry and Commerce or the competent judicial or administrative authorities in Colombia.

Review note

Draft legal caution: this privacy policy is a website-limited draft carried from the source placeholder and adapted only for the stated Opalaxy S.A.S. identity. It should still be reviewed by qualified counsel before being treated as the final policy for a production commercial operation.

Legal contact: support@opalaxy.com

WhatsApp: +57 3154694934 and +57 3175270029

Framework reference already named in the source placeholder: Law 1581 of 2012, https://www.funcionpublica.gov.co/eva/gestornormativo/norma.php?i=49981