3. Data We Collect

App Config.json collects data only to the extent necessary to provide, maintain, and improve our configuration management services. We categorize the data we collect based on its purpose and source. Below is a detailed breakdown of the information we process.

👤 Account & Identity Data

When you create an account or authenticate with App Config.json, we collect information necessary to manage your identity and access rights.

📧 Contact Information

Name, email address, and phone number provided during registration or updated in your profile settings.

🏢 Organization Details

Company name, team structure, and role assignments associated with your workspace.

🔐 Authentication

Secure hashes of passwords or tokens from third-party Identity Providers (e.g., GitHub, Okta, Google) used for Single Sign-On (SSO).

⚙️ Configuration Data

The core of our service revolves around storing and syncing your application configurations. This data is strictly segregated by workspace and encrypted at rest.

                    Example Config Payload
                    JSON
                

// We store the JSON structure you define.
// Sensitive values are encrypted in transit and at rest.
{
  "app_id": "prod-service-alpha",
  "version": "v2.4.1",
  "features": {
    "enable_beta": true,
    "timeout_ms": 3000
  },
  "secrets": {
    "DB_PASS": "[ENCRYPTED_VALUE]"
  }
}
                

Configuration Payloads: The actual JSON/YAML data you upload, including keys, values, and schemas.
Environment Variables: Secrets and sensitive values stored within your workspace.
Version History: Snapshots of configuration changes over time for rollback capabilities.
Schema Definitions: Validation rules and data types defined for your configs.

🔒 Encryption Note

All Configuration Data, including secrets, is encrypted using AES-256-GCM. We employ field-level encryption for secrets, ensuring that even database administrators cannot view sensitive values without the decryption keys.

📊 Usage & Activity Data

We collect data regarding how you interact with our platform to improve performance, billing, and security.

Dashboard Interactions: Pages viewed, clicks, and feature usage within the App Config.json UI.
API Requests: Metadata regarding API calls made by your SDKs, including endpoint, response code, and latency. We do not log the full body of configuration responses in standard logs to minimize exposure.
Sync Events: Timestamps and status of configuration syncs across your environments.
Billing Metrics: Consumption data such as number of syncs, active instances, and storage used for plan enforcement.

💻 Technical & Device Data

To ensure security and optimize the service, we collect standard technical information from your devices and browsers.

🌐 IP Address

Your public IP address for geolocation, fraud prevention, and rate limiting.

📱 Device Info

Browser type, operating system, and device model.

📝 Logs

Server access logs and error logs generated during your session.

🔗 Third-Party Integrations

If you connect external services to App Config.json, we may receive data from those providers based on the permissions you grant.

Git Providers: If you import configs via GitHub/GitLab, we receive repository metadata and file contents associated with the scopes you authorize.
CI/CD Pipelines: Webhook data from tools like Jenkins or CircleCI to trigger config validations.
Analytics Tools: We use anonymized data with services like Google Analytics and Datadog to track platform health.

🍪 Cookies & Local Storage

We use cookies and similar technologies to facilitate functionality and analyze traffic.

Essential Cookies: Required for authentication and security (e.g., session tokens).
Functional Cookies: Remember your preferences (e.g., dark mode, default environment).
Analytics Cookies: Help us understand aggregate user behavior on our website.

📢 Data Minimization

We adhere to the principle of data minimization. We only collect data that is strictly necessary for the purposes described. You can review or export your data at any time via the Data Settings panel.