pTrackly
ENVIJA
Book a Demo
API Limited Use Disclosure

Third-Party API Services, Limited Use Disclosure

Our commitment to responsible and transparent use of data received from Google and other third-party integrations.

Last updated: May 26, 2026

Limited Use Compliance Statement

The use and transfer of information received from Google APIs, and all other third-party platform APIs, to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements, as well as the equivalent data policies of each respective platform.

Connected Platform Integrations

Below is the full list of platforms pTrackly integrates with and the data scopes accessed.

Google Workspace

  • Directory: Users (read-only), view user accounts and profile information
  • Directory: Org Units (read-only), view organizational unit structure
  • Directory: Admin Roles (read-only), view delegated admin roles and assignments
  • Directory: ChromeOS Devices (read-only), view device inventory and metadata
  • Directory: Mobile Devices (read-only), view mobile device inventory and metadata
  • Admin Reports: Audit (read-only), collect audit logs for compliance evidence
Google API Services User Data Policy →

Microsoft 365 / Azure AD

  • Teams (read-only), team names, descriptions, and basic settings
  • Channels (read-only), channel names and descriptions
  • Team Members (read-only), member list and assigned roles
  • User Profile (read-only), signed-in user profile information
Microsoft Graph Data Usage Policy →

GitHub

  • Repositories (read-only), scan repository settings, branch protection, and secrets scanning status
  • Organization (read-only), audit organization members and team permissions
  • User Profile (read-only), read user profile information
GitHub Privacy Statement →

Slack

  • Channels (read-only), list public channels for access scope assessment
  • Workspace Members (read-only), inventory workspace members and roles
  • Files (read-only), identify files shared in channels for data classification
Slack Data Management Policy →

Jira / Atlassian

  • Projects & Issues (read-only), list projects and issues for compliance task tracking
  • Users (read-only), map user accounts for access control compliance
  • Issues (write), create and update issues for compliance task management
Atlassian Privacy Policy →

AWS

  • IAM (read-only), audit user roles, policies, and permissions
  • S3 (read-only), assess bucket encryption and public access settings
  • EC2 (read-only), review instance, volume, and security group configurations
  • RDS (read-only), audit database instance and cluster configurations
AWS Privacy Notice →

How We Use Third-Party Data

Data obtained through any third-party API is used exclusively for the following purposes:

• Providing compliance automation features directly requested by the authenticated user.

• Generating compliance reports, gap analyses, and audit-ready documentation within the pTrackly platform.

• Displaying results to the authenticated user inside their own pTrackly workspace.

We do NOT use third-party user data to:

• Serve advertising or retargeting purposes.

• Build user profiles for any purpose unrelated to the in-product compliance feature.

• Transfer or sell data to any third parties.

• Train AI or machine learning models on the raw content of user data.

Data Sharing and Transfer

pTrackly does not transfer, sell, or share third-party user data except in the following limited circumstances:

• Sub-processors: We may share data with infrastructure sub-processors (e.g., cloud hosting providers) under strict data processing agreements that prohibit further use or sharing.

• Legal requirements: We may disclose data if required by law, court order, or governmental authority.

• User direction: We share data only when explicitly directed to do so by the authenticated user.

Data Storage and Security

All third-party user data is handled with the following security controls:

• Data is encrypted in transit using TLS 1.2+ and at rest using AES-256.

• Access is restricted to the authenticated user and their specific pTrackly workspace.

• We do not store raw third-party data beyond the minimum time needed to generate compliance outputs.

• Cached data is automatically purged when a user revokes OAuth access.

User Control and Revocation

Users retain full control over their connected integrations at all times:

• You may disconnect any integration from within pTrackly's settings at any time.

• You may also revoke access directly from the respective platform's account settings.

• Upon revocation, all cached data for that integration is deleted within 24 hours.

• You may request full deletion of your data by contacting us at hello@ptrackly.dev.

Contact

If you have questions about this disclosure or our handling of third-party API data, please contact us:

• Email: hello@ptrackly.dev

• Phone: +84 33 460 1011

• Address: Lot 9, An Thuong 40, Da Nang City, Vietnam

Book a Demo