Privacy Policy

EGLA CORP
d/b/a EGLA Communications

Effective Date: August 31, 2026
Last Updated: August 31, 2026

1. Who We Are

EGLA CORP, a Florida corporation doing business as EGLA Communications (“EGLA,” “we,” “us,” or “our”), is a technology company focused on multimedia streaming, wireless and mobile systems, artificial intelligence, Internet of Things, intellectual property, and related software platforms. Our offerings include, without limitation, MEVIA® and related streaming and Smart TV technologies, MEVIA OS / MEVIAVERSE concepts and prototypes, Demolizer and other patented or patent-pending systems, EGLAVATOR incubator-related tools, websites (including eglacorp.com, eglacomm.net, eglavator.com, mevia-related properties, and affiliated domains), software downloads, developer tools, and open-source code repositories.

Principal place of business: 4890 NW 101st Ave, Coral Springs, Florida 33076, United States. Privacy and support contact: privacy@eglacorp.com (or, until that mailbox is provisioned, support@eglacorp.com and hr@eglacorp.com). Telephone: +1 (561) 235-8229.

2. Scope

This Privacy Policy describes how we collect, use, disclose, and protect personal information when you:

  • Visit or use our websites, landing pages, documentation sites, or developer portals;
  • Download, install, or update EGLA software, firmware, SDKs, widgets, apps, or packages;
  • Create an account, register a product, request a license key, join a beta, or subscribe to updates;
  • Access, clone, fork, star, watch, contribute to, or otherwise interact with EGLA open-source repositories (for example on GitHub, GitLab, or similar hosts);
  • Contact us for support, sales, licensing, expert-witness, incubator, or partnership inquiries; or
  • Otherwise interact with EGLA technologies that display or link to this Policy.

This Policy does not apply to third-party websites, app stores, cloud marketplaces, or source-hosting platforms that we do not control. Those services have their own privacy policies. Open-source hosting platforms (such as GitHub) process contributor and visitor data under their own terms; we receive only the information those platforms make available to repository owners or that you send us directly.

By downloading our technology, creating an account, submitting information, or using our Services, you acknowledge this Policy. If you do not agree, do not download, register, or use the Services.

3. Information We Collect

3.1 Information you provide

Depending on how you interact with us, you may provide:

  • Identity and contact data: name, company, title, email address, telephone number, mailing or billing address, country or region;
  • Account credentials: username, password (stored hashed), authentication tokens, and profile details you choose to add;
  • Registration and product data: product or SKU selected, license or evaluation request, organization size, intended use case, and related questionnaire answers;
  • Developer and contributor data: Git handle, public profile URL, affiliation, signed Contributor License Agreement (CLA) or Developer Certificate of Origin (DCO) information, and communications about issues, pull requests, or security reports;
  • Support and correspondence: messages, attachments, screenshots, logs you choose to send, and meeting or call notes;
  • Transactional data: invoices, purchase orders, payment method tokens processed by our payment processor (we do not store full payment-card numbers on EGLA systems when a PCI-compliant processor is used); and
  • Marketing preferences: newsletter opt-in, event registration, and communication choices.

3.2 Information collected automatically

When you download software or visit our sites, we and our service providers may automatically collect:

  • Device and technical data: IP address, approximate location derived from IP, browser type and version, operating system, device identifiers, language, time zone, referring URL, and screen or device class;
  • Usage data: pages viewed, features used, download events, crash or diagnostic reports you enable, session duration, and click-stream data;
  • Download and update telemetry (if enabled in the product or installer): package name and version, success or failure of install/update, and coarse environment metadata needed to serve the correct binary; and
  • Cookies, pixels, and similar technologies as described in Section 8.

Locally installed software may generate logs on your device. Those logs remain on your systems unless you choose to upload them for support or unless you enable optional telemetry in product settings.

3.3 Information from third parties

We may receive limited information from: app stores and package registries; source-code hosts (public contributor activity on our repositories); payment and billing processors; analytics and email-delivery vendors; professional or business directories; and publicly available sources when you contact us about licensing, investment, or litigation-related professional services.

3.4 Information we do not intentionally collect

We do not require government identification numbers, precise geolocation, biometric identifiers, or special-category data (health, race, religion, sexual orientation, political opinions) to download software or register a standard developer or product account. Do not submit such data unless we specifically request it for a lawful purpose and provide a separate notice. Open-source repositories should not be used to post personal data of others.

4. How We Use Personal Information

We use personal information to:

  • Provide, operate, secure, and improve websites, downloads, registration, licensing, and support;
  • Create and administer accounts, authenticate users, and issue or revoke access credentials and license keys;
  • Deliver software packages, documentation, updates, security patches, and compatibility notices;
  • Process contributions to open-source projects, review pull requests, credit authors, and enforce contribution agreements and codes of conduct;
  • Respond to inquiries, provide technical support, and diagnose defects you report;
  • Communicate product, security, and legal notices that are not marketing (for example, a vulnerability affecting a package you downloaded);
  • Send optional newsletters, event invitations, and product announcements where permitted by law and your preferences;
  • Prevent fraud, abuse, reverse-engineering that violates license terms, unauthorized redistribution, and security incidents;
  • Comply with law, enforce agreements, protect intellectual property and trade secrets, and establish, exercise, or defend legal claims; and
  • Analyze aggregated or de-identified usage to improve performance, documentation, and roadmap decisions.

We do not sell personal information as “sale” is commonly understood in a commercial data-broker sense. See Section 11 for U.S. state-law definitions of “sale” and “share.”

5. Legal Bases (EEA, UK, and Similar Laws)

Where the GDPR or comparable law applies, we process personal data on one or more of these bases:

  • Contract: to perform our agreement with you (account, license, download delivery, support you request);
  • Legitimate interests: to secure our systems, improve products, understand how downloads are used at an aggregate level, communicate with business contacts, and protect our IP—balanced against your rights;
  • Consent: for non-essential cookies, optional telemetry, and marketing emails where consent is required; you may withdraw consent at any time; and
  • Legal obligation: to comply with tax, accounting, export-control, lawful process, and record-keeping duties.

6. Open-Source Code and Developer Interactions

EGLA may publish selected code, samples, SDKs, schemas, or documentation under an open-source license specified in the applicable repository (for example MIT, Apache-2.0, BSD, or another license stated in the LICENSE file). That license governs use of the code. This Privacy Policy governs personal information associated with obtaining or contributing to that code.

6.1 What public contribution implies

If you open an issue, submit a pull request, comment, or otherwise contribute, your Git username, avatar, public profile information, and the content of your contribution are public by design of the hosting platform. Do not include passwords, private keys, personal data of third parties, customer data, or confidential business information in public issues or commits. We may retain contribution records indefinitely as part of the project history, attribution, and license compliance.

6.2 Private channels

Security vulnerabilities should be reported privately to security@eglacorp.com (or support@eglacorp.com if that alias is not yet live), not in a public issue tracker, unless we publish a different coordinated-disclosure process. CLA or contributor identity information submitted off-platform is used only to confirm rights to the contribution and is retained as long as the project exists plus any legally required period.

6.3 Telemetry in open-source builds

Default open-source builds should not phone home with personal data. If a binary or sample includes optional analytics, crash reporting, or license-check features, that fact will be documented in the README or product settings and will be off by default unless clearly disclosed at download or first run.

6.4 Third-party dependencies

Open-source packages may include third-party libraries. Those libraries are subject to their own licenses. We are not responsible for privacy practices of dependency authors or of package registries (npm, PyPI, Maven, crates.io, Docker Hub, and similar).

7. How We Share Information

We disclose personal information only as follows:

  • Service providers (processors): hosting, email delivery, analytics, payment processing, customer-relationship tools, error monitoring, and professional advisors (legal, accounting) under contracts that limit use to our instructions;
  • Source-code and package hosts: GitHub and similar platforms, solely as needed to operate public or private repositories;
  • Corporate transactions: if we negotiate or complete a merger, financing, or sale of assets, information may be disclosed to counterparties under confidentiality obligations;
  • Legal and safety: when we believe disclosure is required by law, court order, or government request, or is necessary to protect rights, property, users, or the public;
  • With your direction or consent; and
  • Aggregated or de-identified data that does not reasonably identify you.

We do not rent email lists. We do not authorize service providers to use your information for their own independent marketing.

8. Cookies and Similar Technologies

Our websites may use:

  • Strictly necessary cookies for security, load balancing, and session management;
  • Preference cookies to remember language or dismissed notices; and
  • Analytics cookies or similar tools (for example first-party analytics or a vendor such as Matomo or an equivalent) to understand traffic and download funnels.

Where required, we will present a cookie banner and honor opt-out for non-essential cookies. You can also control cookies through your browser. Blocking cookies may limit certain site features but will not prevent a manual software download in most cases.

9. Retention

We retain personal information only as long as needed for the purposes described, including:

  • Account data: for the life of the account and a reasonable period thereafter (typically up to 24 months of inactivity, unless a longer period is required);
  • Download and server logs: commonly 12–24 months, longer if needed for security investigations;
  • Transactional and tax records: as required by U.S. federal and Florida law (often seven years);
  • Support tickets: for the support relationship plus a period needed to analyze recurring defects;
  • Legal hold: for the duration of any dispute, investigation, or litigation; and
  • Public open-source contribution history: for the life of the repository.

When retention expires, we delete or de-identify data, except where backup media are overwritten on a rolling cycle.

10. Security

We implement administrative, technical, and physical safeguards appropriate to the nature of the information, including access controls, encryption in transit for our websites (TLS), hashed passwords, least-privilege administration, and vendor due diligence. No method of transmission or storage is 100% secure. You are responsible for safeguarding credentials, API keys, and private keys associated with your account or forks of our code. Notify us promptly at support@eglacorp.com if you believe an account or repository credential has been compromised.

11. Your Privacy Rights and Choices

11.1 All users

You may:

  • Update account profile information through your account settings, if offered, or by emailing us;
  • Unsubscribe from marketing emails using the link in the message (transactional and security notices will still be sent);
  • Disable optional telemetry in product settings where that control exists;
  • Request access to, correction of, or deletion of personal information we hold, subject to legal exceptions; and
  • Close your account by contacting privacy@eglacorp.com or support@eglacorp.com.

11.2 United States state privacy laws

If you are a resident of California or another U.S. state that grants consumer privacy rights (including, as applicable, Colorado, Connecticut, Virginia, Texas, Oregon, Florida’s FDBR where applicable, and similar statutes), you may have the right to: know/access categories and specific pieces of personal information; correct inaccuracies; delete; obtain a portable copy; opt out of “sale” or “sharing” for cross-context behavioral advertising; opt out of certain profiling; and limit use of sensitive personal information. EGLA does not use sensitive personal information for purposes that require a “limit use” control in ordinary download and registration flows.

We do not have actual knowledge that we sell or share the personal information of consumers under 16 years of age. To exercise rights, email privacy@eglacorp.com with the subject line “Privacy Request” and sufficient detail to verify your identity. You may use an authorized agent as permitted by law. We will not discriminate against you for exercising privacy rights.

California “Notice at Collection.” Categories we collect include identifiers, commercial information (downloads and license requests), internet or electronic activity, professional information, and inferences drawn from those categories for product improvement. Sources, purposes, and disclosures are described in this Policy. Retention is described in Section 9.

11.3 EEA, UK, and Switzerland

You may have rights of access, rectification, erasure, restriction, portability, and objection, and the right to withdraw consent. You may lodge a complaint with your local supervisory authority. Because EGLA is established in the United States, transfers of personal data from the EEA/UK/Switzerland to the U.S. are made using appropriate safeguards such as Standard Contractual Clauses where required, plus supplementary measures we consider appropriate.

12. International Transfers

EGLA is based in Florida, United States. Information is processed and stored in the United States and may be processed by service providers in other countries. Those countries may have data-protection laws different from your home jurisdiction. Where legally required, we use contractual and technical measures to protect transferred data.

13. Children’s Privacy

Our technologies, developer tools, and open-source projects are intended for adults and for organizations. They are not directed to children under 13 (or under 16 in jurisdictions that set that threshold for information-society services). We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will delete it.

14. Intellectual Property, Telemetry, and License Compliance

Registration and download records may be used to administer licenses, prevent unauthorized redistribution of proprietary (non-open-source) components, and support EGLA’s intellectual-property enforcement. Open-source components remain subject to their stated licenses. Nothing in this Policy grants a patent, trademark, or trade-secret license beyond what the applicable software license expressly grants. Product names MEVIA, EGLAVATOR, Demolizer, and related marks are trademarks of EGLA CORP or its affiliates.

15. Third-Party Links and Embedded Services

Sites and documentation may link to YouTube, LinkedIn, X, payment pages, app stores, or documentation hosts. Your use of those services is governed by their policies. Embedded players or widgets may set third-party cookies.

16. Automated Decision-Making

We do not use automated decision-making, including profiling, that produces legal or similarly significant effects on individuals in connection with software download or standard registration. Abuse-prevention systems may automatically flag or throttle suspicious download or login activity; you may contact us to contest an adverse automated security action.

17. Changes to This Policy

We may update this Policy from time to time. The “Last Updated” date will change, and material changes will be posted on the applicable website or communicated by email to registered users when required. Continued use after the effective date constitutes acceptance of the updated Policy to the extent permitted by law.

18. Contact Us

Questions, requests, or complaints about this Policy or our privacy practices:

EGLA CORP d/b/a EGLA Communications
Attn: Privacy
4890 NW 101st Ave
Coral Springs, FL 33076
United States

Email: privacy@eglacorp.com | support@eglacorp.com | hr@eglacorp.com
Phone: +1 (561) 235-8229

Please do not send passwords, private keys, or complete payment-card numbers by unencrypted email.

19. Governing Language

This Policy is prepared in English. If we provide a translation, the English version controls in the event of a conflict, except where local law requires otherwise.

© 2026 EGLA CORP. All rights reserved.