Fiyrr Privacy Policy

This Privacy Policy applies to all core domains, tools, and tracking engines hosted under the main platform at fiyrr.com, including the P6 Schedule Analyzer processing terminal at sch.fiyrr.com, material managers, and dashboard inclusion environments. It outlines what information we process, our structural use profiles, and how you can seamlessly manage, export, or delete your workspace parameters.

1. Information Fiyrr Collects

We collect data to engineer faster diagnostic reports, automate logic validations, and deliver precise delay summaries to project controls divisions. The telemetry we ingest depends strictly on how you interface with our calculation tools.

A. Things You Create or Provide Directly

• Account Registry Profiles: When you generate a profile, you provide personal data including user nomenclature, company verification details, email endpoints, and secured password parameters.
• Project Management Assets: We ingest and store the engineering content you upload, route, or evaluate through our execution modules. This includes Oracle Primavera P6 layout spreadsheets, schedule data snapshots, target baseline records, update parameters, delay journals, and tracking summaries.

B. Information Collected Dynamically as You Interface With Our Engine

• App, Browser & Device Profiles: We gather client environment data to maintain structural layout sizing consistency across systems. Ingested assets track browser runtime engines, client viewport resolutions, device classification rules, operating system variables, and unique system session codes.
• Network Telemetry Logs: When your workstation accesses our analyzers, server logs dynamically preserve transaction timestamps, system crash notifications, system request parameters, refer URLs, and server connection IP addresses.

2. Why Fiyrr Processes Your Data

We combine your industrial configuration metrics with computational logic to drive advanced automation and optimization features:

• Deliver Analytical Services: We process your uploaded project files to generate key metrics like elapsed times, remaining durations, critical path slippages, and tracking trends.
• Maintain and Troubleshoot Platform Performance: System crash records and performance metrics let us patch calculation engine bugs and prevent downtime in live dashboard environments.
• Communication Channels: We use your contact address directly to send security triggers, notify you of unscheduled system resets, or confirm automated reporting processing status updates.

Fiyrr maintains strict boundaries: we do not trade, rent, or lease your project files, structural schedule data, or personal profile details with third-party advertising companies under any condition.

3. Security Architecture & Safeguards

Fiyrr environments are built with multi-layered protection rules to safeguard your project data from unauthorized breach vectors:

• We apply transit layer encryption protocols to hide sensitive information while transferring layout files from your terminal into our database engines.
• We run background logic checks to discover and immediately block malicious script execution or corrupted data block threats.
• Access to raw database storage arrays is limited strictly to internal service agents who need it for processing constraints and are subject to rigid NDA restrictions.

4. Exporting and Deleting Your Workspace

You have full, independent choices regarding the structural data we maintain for your platform profile:

• Data Portability: You can export full copies of your generated tracker indexes, variance records, and parsed analysis files directly to save local backups.
• Permanent Deletion: You can instantly wipe specific items from active memory streams, drop complete baseline evaluation records, or delete your entire workspace profile by contacting your administrator.

5. Changes to This Policy

We evaluate and adjust this Privacy Policy as our features evolve. We will never reduce your rights under this agreement without your explicit consent. Major changes will be flagged via prominent notifications inside the primary user workspace terminal.