Authenticated workspaces
Dashboards, documents, templates, connected-app data, and billing state are scoped to authenticated user accounts.
Security and trust
Built for sensitive project and business-system context.
Rainfall works with technical docs, uploaded source, CRM metadata, billing state, and integration tokens. The product is designed around authenticated access, account scoping, encrypted tokens, and server-side controls.
Security posture
Authenticated
Workspace data is scoped to the signed-in account.
Encrypted tokens
Integration tokens are stored encrypted server-side.
Scoped snapshots
CRM snapshots belong to the connected account.
Read-only workflow
Connected apps are used for metadata-driven documentation.
Protection layers
Security is part of the workflow, not an afterthought.
Encrypted integration tokens
Connected-app tokens are encrypted before storage and used server-side for supported read-only documentation workflows.
Server-side feature gates
Plan limits and Pro-only features are enforced by backend checks, not only by buttons hidden in the interface.
Verified payments
Payment attempts and plan changes are verified with the provider and stored with verification state for account support.
Controls
How Rainfall handles access and connected apps.
Rainfall separates user access, plan enforcement, integration storage, and app metadata workflows so sensitive context is handled from the server side.
Workspace data is returned only to the authenticated owner.
Templates and uploaded context are scoped to the account that created them.
Usage limits are tracked server-side across chat and documentation routes.
Connected-app workflows use read-only access patterns for metadata-driven documentation.
Disconnecting an integration removes stored connection data and related CRM snapshots.
Payment records keep verification state for auditability and support.
Integration lifecycle
Connected app documentation uses a controlled path.
Pro connected-app workflows are built for documentation from metadata. Rainfall reads what it needs for the product flow, stores connection data securely, and removes stored snapshots when the user disconnects.
1User signs in
Workspace routes and account APIs require authenticated access.
2Connect app
Tokens are handled server-side and encrypted before storage.
3Scan metadata
Rainfall reads supported metadata for documentation workflows.
4Disconnect
Stored connection data and snapshots are removed.
Report a concern
See something that looks wrong?
If you notice account access, billing, integration, or data isolation behavior that does not look right, contact Rainfall directly.