Skip to main content
Dcycle is designed for enterprise operational data management. This page covers how we protect your data, manage access, and handle security across the platform and API.

API Key Security

Creation, storage, rotation, and revocation

Data Protection

Encryption, residency, and GDPR compliance

Logging & Access

Audit trails, access control, and monitoring

API Key Lifecycle

API keys are the primary credential for programmatic access to Dcycle. For step-by-step instructions on creating and using API keys, see Authentication.
API keys are generated from the Dcycle web application under Company settings → API Keys. Each key is bound to the user who created it — all data uploaded with that key is attributed to that user for audit and compliance purposes.Keys are displayed once at creation time and cannot be retrieved afterward. Only organization admins can create them. Each key has an access (Read and write, or Read only), an expiry (90 days by default, a year at most) and a name to tell it apart, chosen when creating it. A key never reaches further than the person who created it: it has their access, in the organization and in the subsidiaries where they are a member, and only their read access when it is read-only. It stops working in an organization its creator leaves. Test an integration on your own organization, as Testing an integration explains.How to create an API key →
Dcycle stores each key created since 22 October 2026 only as its SHA-256 hash, never the key itself, in a PostgreSQL database hosted on AWS RDS with encryption at rest enabled (AES-256). Replace a key created before that date with a new one, so that every key that still works is stored only as its hash. After creation, the management UI never shows the key again: it lists each key by its name and the first characters of the key, with its access, when it expires, when it was last used and who created it.The database is deployed in a private VPC subnet with no public internet access. Access is restricted to application servers via security groups.
All API communication uses TLS 1.2+ (HTTPS enforced). HTTP requests are rejected at the load balancer level.API keys are transmitted in request headers (x-api-key) over encrypted connections. We recommend storing keys in environment variables or secret managers — never in source code or version control.Security best practices →
Every key expires (90 days by default, a year at most): check its date in the Expires column of Company settings → API Keys (the person who created it is also emailed 14 and 3 days before) and rotate it before then. The rotation process requires no downtime:
  1. Generate a new API key
  2. Update your integrations to use the new key
  3. Verify the new key works correctly
  4. Revoke the old key
Multiple active keys can coexist per organization, enabling zero-downtime rotation.
API keys can be revoked immediately from the management UI (Company settings → API Keys). Once revoked, all requests using that key return 401 Unauthorized instantly. This action cannot be undone.How to revoke an API key →

Data Protection

Encryption in Transit

TLS 1.2+ enforced on all endpoints. HTTP connections are rejected. All data between your systems and Dcycle is encrypted end-to-end.

Encryption at Rest

AES-256 encryption via AWS RDS for all database storage. S3 buckets use server-side encryption (SSE-S3/SSE-KMS) for uploaded files.

Data Residency

EU-hosted — all data is stored and processed in AWS eu-west-1 (Ireland). No data leaves the European Union.

GDPR Compliance

Dcycle acts as data processor under GDPR. Data processing agreements (DPAs) are available on request.
Automated daily backups with 7-day retention via AWS RDS automated snapshots. In case of accidental data deletion, contact contact@dcycle.io within 7 days with your organization ID and a description of the affected data.
Users can delete records at any time via the API or web application. Deleted records are removed from the primary database immediately. Backup copies are purged automatically after the 7-day retention window.
Dcycle runs on AWS (Amazon Web Services) with the following architecture:
  • Compute: ECS Fargate (containerized, serverless)
  • Database: RDS PostgreSQL (encrypted, private subnet)
  • Storage: S3 (server-side encryption)
  • Load balancing: Application Load Balancer with TLS termination
  • Network: VPC with private subnets, no direct internet access to databases
All infrastructure is managed with Infrastructure as Code (AWS CDK) for consistency and auditability.

Access Control

Dcycle uses organization-level access control with role-based permissions. Every API request is scoped to a single organization via the x-organization-id header.

Roles

Organization Isolation

Dataset visualization endpoints (/v1/datasets) require an authenticated member of the organization selected by x-organization-id. This includes catalogue and schema reads. A normal user without an enabled membership receives 403 LOGGED_USER_NOT_MEMBER. Viewer members can preview, query, list filter values, and export dataset results. These read operations use POST to accept the query configuration; they do not grant permission to create or edit visualizations.
  • Users can only access organizations where they have an active membership
  • Each API request is scoped to a single organization — cross-organization data access is not possible without explicit membership
  • Parent organizations (holdings) can view aggregated data from subsidiaries when configured

Permission Model

Permissions are defined as resource:action pairs (e.g., facilities:create, vehicles:read). Available actions are: create, read, update, delete. Administrators can configure custom permission sets per role within their organization.

Logging & Auditability

What Is Logged

Every API request generates a structured log entry containing:

User Attribution

All data created via API is linked to the user who owns the API key. Every record includes:
  • created_by — the user who created the record
  • created_at — timestamp of creation
  • updated_at — timestamp of last modification
This ensures full traceability for compliance and audit purposes.

Request Tracing

Each API response includes tracing headers that can be provided to Dcycle support for incident investigation:
Save these headers when debugging integration issues. Include them when contacting support to speed up investigation.

Integration Patterns

The Dcycle API supports multiple integration approaches depending on your needs:

Network Requirements

The Dcycle API is a public HTTPS endpoint (api.dcycle.io). No VPN, dedicated IP, firewall allowlisting, or special network configuration is required. Any environment with outbound HTTPS access (port 443) can connect.

Rate Limits

Outside logistics, which has limits of its own, every API key has a limit across all routes and every IP address a ceiling shared by the keys behind it. The figures, the limits some routes add and how to read them are in Rate Limits. Rate limit headers are included in every response:
  • X-RateLimit-Limit — the most requests you can make right now (the bucket’s capacity)
  • X-RateLimit-Remaining — requests still available
  • X-RateLimit-Reset — Unix timestamp (seconds) when the bucket is full again
Contact contact@dcycle.io if you need higher limits for your use case. For detailed integration examples, see Automation Overview and Reporting Pipelines.

Incident Response

Reporting Security Issues

Report security concerns to contact@dcycle.io. Include as much detail as possible: what you observed, when it happened, and any relevant request/correlation IDs.

Our Process

Dcycle continuously monitors infrastructure health, application performance, and security events using AWS CloudWatch, automated alerting, and log analysis.

Next Steps

Authentication

Set up API keys, CLI login, and MCP integration

API Reference

Explore all available endpoints

Support

Contact our team for questions