Everything your security, legal, and procurement teams need to evaluate OffGridFlow.
OffGridFlow enforces role-based permissions at the API layer. Every request is validated against the authenticated user's role before data is returned.
| Capability | Admin | User | Viewer |
|---|---|---|---|
| View dashboard and emissions data | Yes | Yes | Yes |
| Upload CSV / connect data sources | Yes | Yes | No |
| Create and edit activities | Yes | Yes | No |
| Generate compliance reports | Yes | Yes | No |
| Submit reports for approval | Yes | Yes | No |
| Approve or reject reports | Yes | No | No |
| Lock factor snapshots | Yes | No | No |
| Manage users and roles | Yes | No | No |
| Configure billing and subscription | Yes | No | No |
| Export all organization data | Yes | No | No |
| Request data deletion | Yes | No | No |
| View audit logs and change history | Yes | Yes | Yes |
In the integration suite, a second registered tenant authenticates successfully and then calls GET /api/emissions/activities. The response is 200 OK with 0 activities from the first tenant, proving no cross-tenant data leakage through the main emissions activity endpoint.
The login flow supports a second authentication step with a six-digit one-time code. After primary credential verification, users complete /api/auth/verify-2fa using a temporary token and TOTP code before a session token is issued.
OffGridFlow provides self-service data governance endpoints. Admins can export, request deletion, and review retention policies without contacting support.
Admin-only. Returns a JSON package containing all organization data: users, activities, calculation ledger entries, and change log. Response includes exported_at timestamp and tenant_name. Download as a file via Content-Disposition header.
Admin-only. Initiates a 30-day retention window. The request is logged in the change log with the requesting user's ID. Data is retained for 30 days to allow cancellation, then permanently removed. Response includes deletion_date and retention_days.
Returns the organization's data retention schedule:
Export formats: JSON (full dataset), PDF (reports), CSV (activities), XBRL (compliance). All emission data, reports, and uploaded evidence remain the property of the customer.
| Data Type | Classification | Handling |
|---|---|---|
| User credentials (passwords) | Secret | bcrypt hashed, never stored in plaintext, never logged |
| API keys | Secret | SHA-256 hashed at rest, prefix-only display in UI |
| Cloud connector credentials | Confidential | Encrypted at rest (AES-256), tenant-scoped access only |
| Emission activity data | Internal | Tenant-isolated, soft-deleted, exportable, 90-day post-subscription retention |
| Calculation results | Internal | Immutable ledger, 7-year retention for audit compliance |
| Compliance reports | Internal | Versioned, approval-gated, export with checksum verification |
| Audit logs | Internal | Append-only, 7-year retention, includes IP and user agent |
| Email addresses | PII | Used for authentication only, exportable via governance API, deletable on request |
| Emission factors | Public | Sourced from EPA, IEA, DEFRA, IPCC — publicly available data |
Procurement and finance reviewers often start here, then branch into the framework-specific buying pages below.
For security questionnaires, DPA requests, or custom procurement requirements, contact us directly.
Contact Security Team