Scadova Logo Home About Careers Blog & News Contact Us
Legal & Compliance

Privacy Policy

Updated: October 4, 2026 | Version 2.1

Introduction

At Scadova LLC, we engineer enterprise software governed by the principle of absolute data sovereignty. This Privacy Policy details the cryptographic methodologies and operational protocols we employ to secure your organizational data, financial telemetry, and biometric vectors across our entire ecosystem.

1. Information We Collect

We collect deterministic data strictly required to orchestrate our SaaS modules. This includes:

  • Account Telemetry: Organization names, administrator emails, and structural deployment configurations.
  • Financial Ledgers: Transaction metadata integrated via our financial systems (fully tokenized; raw banking credentials are never stored).
  • Operational Metrics: Aggregated system performance and latency metrics utilized to optimize our Copilot engines.

2. Biometric Data Handling (Face Recognition)

Scadova enforces a strict "No Raw Image" policy. When utilizing the AI Face Recognition protocol:

  • Facial topography is instantly converted into irreversible, encrypted mathematical embeddings at the edge device.
  • Source images are permanently deleted from RAM within milliseconds.
  • Biometric vectors cannot be reverse-engineered into human-readable faces.

3. How We Utilize Data

Your data is processed exclusively to maintain and execute your active software modules. We do not—and fundamentally cannot—sell your telemetry to third-party data brokers. Our machine learning models are trained on siloed, anonymized aggregates to protect proprietary operational secrets.

4. Zero-Trust Security Protocols

We deploy military-grade architecture to defend our infrastructure:

  • Encryption: AES-256 encryption at rest and TLS 1.3 for data in transit.
  • Access Control: Cryptographic hashing and mandatory multi-factor authentication (MFA) for all system-level administration.
  • Auditing: Immutable server logs tracking all systemic access points.

5. Your Data Rights

Depending on your jurisdiction (including GDPR and CCPA frameworks), your organization retains the absolute right to access, export, or permanently purge all data nodes hosted within the Scadova environment. Contact your dedicated Deployment Architect to execute a total data wipe.

Scadova Workday Extension Privacy

Effective date: October 4, 2026. Operator: Scadova. Contact: info@scadova.com.

Purpose

Scadova Workday is a browser side-panel companion for employee attendance, time tracking, local productivity tools and private company meeting invitations.

Information used

- Account identity: username/work email, employee name, role and employment profile details supplied by Scadova.

- Authentication: the password is transmitted to the selected server at sign-in; the extension does not intentionally persist it. The session token/cookie is stored to maintain login and synchronize the portal session.

- Attendance: clock-in/out and break actions, timestamps, work durations and timezone. Where required by company attendance settings, precise latitude/longitude and accuracy are requested at the moment of an action. There is no continuous background location watch.

- Server metadata: the configured server receives connection IP and browser/request metadata and may retain attendance/security audit records. Reverse-geocoding services used by the server may receive coordinates to resolve an address.

- Productivity content: task titles/status/priority, note text, reminder text and due dates, plus server and alert preferences are stored locally in the browser profile. These local records are shared between signed-in accounts in that profile.

- Meetings: titles, reasons/agendas, times, selected employee identities and guest email addresses are processed by the Django server and Google Calendar. Invited users receive their meeting details and Meet link in dashboards and the extension. Invitations are sent to selected guests through Google Calendar. Google access/refresh tokens and OAuth client secrets are stored on the server, not in extension packages.

Access and sharing

The extension reads the session cookie only for the chosen Scadova/local server. It checks eligible open portal tabs to obtain attendance location using the portal's browser permission when necessary. It does not collect general browsing history. Company administrators have access according to the portal's employment roles; external guests receive only meeting invitation details. Google processes calendar/meeting data under its own terms. Server reverse geocoding may use a separate provider. No advertising, sale of personal data or analytics tracking is added by this extension.

Storage and retention

Local items remain until deleted or extension storage is cleared. Uninstalling removes extension storage; signing out clears the session token but preserves local productivity items. Server attendance, security and meeting records follow company retention requirements; this release does not impose a fixed automatic deletion period. Contact Scadova for access, correction or deletion requests, subject to required employment record retention. Google Calendar events and organizer tokens remain until removed/revoked by the company organizer.

Controls and security

Location permission may be declined or revoked; location-required attendance actions then cannot proceed. Users may sign out, change the selected server, delete notes/reminders, or uninstall. Cloud traffic uses HTTPS. HTTP is permitted only for same-machine loopback development. Sessions are persistent but can be revoked by logout, account disablement or applicable server checks. A compromised browser profile or server may expose stored tokens; no absolute security or encrypted local-token claim is made.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Such information is used for the user-facing calendar/meeting functionality and is not used for advertising or unrelated purposes.

Changes

Scadova will update this notice when data handling changes. The current notice is available on this page. Material changes to data handling will be reflected here and in the extension disclosures.

Browser permissions

Storage preserves session tokens, settings and local productivity content. Cookies synchronize authentication with the selected company portal. Alarms schedule reminders and work-status checks; notifications display user-created reminder alerts. Side Panel provides the Workday interface. Optional geolocation verifies clock-action locations with permission. Scripting runs packaged location-request code in a matching portal tab when required. Host access is restricted to the declared Scadova domains and localhost/127.0.0.1 development servers. All executable extension code is packaged locally; remote responses supply application data rather than executable code.

6. Contact Our Compliance Team

For legal inquiries, architecture audits, or data sovereignty requests, please contact our global operations center.

Scadova LLC
Birmingham, AL, United States
Email: info@scadova.com