Privacy Policy

1Introduction

This Privacy Policy explains how Explyra collects, processes, stores, and shares data across the active product ecosystem, including Expense, Attendance, Booking, Google integrations, AI features, and Health modules where used.

By creating an account or using Explyra services, you agree to this policy. If you do not agree, please discontinue use of the platform.

2Information We Collect

Depending on modules and features enabled, we may collect:

• Account identity data: name, email, user role, organization/company mapping, and profile metadata.
• Expense and reimbursement data: claims, receipt attachments/links, notes, amount/currency data, workflow status, payment mode, transaction reference, payment dates, and payment issue/dispute records.
• Financial account details submitted by users: account category, bank/wallet label, and entered account identifier values for payout/reimbursement workflows.
• Operations data: attendance records, salary/payroll-related fields, booking details, calendar activity, and internal workflow logs.
• Health data (if Health module is used): body metrics, diet/sleep/condition fields, water/food/exercise logs, blood pressure, heart rate, medicine schedules, and AI-generated plans.
• Technical and analytics data: browser/device characteristics, diagnostic traces, and analytics events.

3Google Workspace and API Data

When users connect Google, Explyra requests authorization for integration scopes used by product flows:

• https://www.googleapis.com/auth/drive.file for user-initiated Drive uploads.
• https://www.googleapis.com/auth/spreadsheets for export to Google Sheets.
• https://www.googleapis.com/auth/calendar.events for calendar event creation and meeting scheduling.

Meeting-link generation may create Google Calendar events with conference metadata to produce Google Meet links. Any additional Google-connected feature (including Gmail-oriented feature variants) requires explicit authorization in that specific flow.

4How We Use Your Data

We use personal and operational data to provide service functionality, including:

• Secure sign-in, account continuity, and role-based access.
• Expense lifecycle operations from submission to approval/review/export.
• Attendance/payroll/booking workflows and analytics dashboards.
• Integration actions triggered by users (Drive uploads, Sheets exports, Calendar/Meet creation).
• AI-assisted product features, summaries, and recommendation outputs.
• Payment verification, webhook reconciliation, support, fraud checks, and legal obligations.

5Data Storage and Retention

Explyra uses cloud-backed infrastructure and may use browser-side persistence for operational UX state (for example theme preferences, integration status flags, and temporary session cues). Data is retained for service delivery, security, dispute handling, and legal/business obligations. Different categories may have different retention periods.

6Third-Party Services

Our services may involve trusted providers such as:

• Firebase/Google Cloud for authentication and structured cloud data handling.
• Google APIs for Drive, Sheets, Calendar, and account authorization.
• Cloudflare/Vercel/related hosting layers for delivery, routing, and uptime support.
• Payment service integrations including NOWPayments workflows where enabled.
• Analytics providers for usage and performance monitoring.

7AI and Sensitive Data Boundaries

AI features are assistive, not authoritative. You must verify outputs before relying on them for financial, legal, HR, or medical decisions. Health and finance-related records are treated as high-sensitivity data in our product context.

8User Rights

Subject to applicable law and account context, you may request:

• Access to personal data associated with your account.
• Correction of inaccurate profile/workspace information.
• Deletion of eligible account data.
• Export of eligible records.
• Revocation/disconnection of linked Google integrations.

9Cookies and Tracking

Explyra uses cookies and similar technologies for session continuity, security hardening, and analytics. You can control cookie behavior through browser settings, though certain features may be impacted.

10Policy Updates and Contact

We may revise this policy as features evolve. Updates are published on this page with an updated date.