Updates across product, infrastructure, and market coverage.

Summary

Follow changes in product capabilities, supported regions, intelligence systems, automation surfaces, and platform operations as PropDB evolves.

This page explains how PropDB operates as a product company and platform provider.

If you need a contractual version of these terms, request the latest enterprise addendum from support.

What You Can Do

• Use map-first workflows to draw, save, and refresh areas of interest.
• Review scores, datasets, and supporting evidence directly on the map and in the intelligence rail.
• Generate reports and exports that remain linked to the original area context.
• Run AI-assisted workflows that produce structured, auditable outputs.
• Use automations and scheduled pipelines to keep intelligence current.
• Control access through roles, modules, plan entitlements, and audit trails.

How It Works (High Level)

• Frontend renders map + panels and calls backend APIs over authenticated sessions.
• Backend verifies identity, resolves authorization, and executes workflows via services and queues.
• Saved areas store geometry and metadata so results can be revisited and refreshed.
• Pipelines and jobs emit status updates so the UI can show progress and completion.
• Operational data is stored in PostgreSQL with Redis used for sessions, caching, and pub/sub.

Reliability Expectations

• Long-running work is designed to run as jobs (not in fragile browser-only flows).
• Idempotency keys are used where appropriate to prevent accidental double-charges or double-runs.
• Rate limits protect shared infrastructure and prevent abusive traffic patterns.
• Backpressure and sensible defaults are applied to high-cardinality map layers and markers.

Security Posture

• Authentication is handled via JWT verification and strict issuer/audience checks.
• Authorization is enforced server-side; client claims are not trusted for access decisions.
• Security headers, request size limits, and rate limits are applied at the API layer.
• Sensitive credentials are stored encrypted and only decrypted when required for execution.
• Audit logs capture privileged actions and important workflow events.

Data Handling

• Typical data includes saved geometries, analysis outputs, report metadata, pipeline runs, and audit events.
• Inputs are validated to prevent oversized payloads and unexpected formats.
• Where third-party sources are used, your use must comply with their terms and licensing constraints.
• We minimize data collection to what is needed to operate the platform and support customers.

Retention & Deletion

• Retention periods can vary by plan and by data category (analysis outputs vs. audit logs).
• Enterprise customers can request retention overrides and deletion workflows.
• Where deletion is requested, we aim to remove user-linked content unless retention is required by law or contract.
• Backups and disaster recovery systems may retain data for a limited period after deletion requests.

Support

For questions, requests, or incident reports, email support@propdb.ai.

Include your workspace email, the affected area/run id, and the approximate time of the issue for fastest triage.

FAQ

• Why do I see different counts across layers? Counts may reflect filtered vs. fetched vs. visible markers.
• Can pricing or credits change? Yes, pricing can evolve; the backend is the source of truth for costs.
• Is this page a legal contract? No, this page is an informational overview and may be updated.
• Need something specific? Contact support@propdb.ai for enterprise documentation.

Last Updated

April 28, 2026.