Data Safety & Lifecycle Policy
Detailed disclosure of file processing, hybrid Cloudinary sync, and automated erasure protocols.
1. Hybrid Storage Architecture
To provide both fast local transformations and collaborative workspaces, RaiseTool implements a secure hybrid storage engine:
Local Server-Side Processing
By default, files are uploaded to secure, isolated directories on our local node server. They are processed in memory or through private local CLI processes (like FFmpeg or Muhammara PDF engines). No external service ever gets access to these files.
Remote Cloudinary Sync
For tools requiring remote accessibility or collaborative active workspaces, files can be securely synchronized with Cloudinary cloud storage. This sync uses encrypted tokens. The files are labeled with anonymous hashes, preventing anyone from reading their content or determining their owner without the session key.
2. Processing Modes and File Lifecycles
Depending on the specific tool you select, RaiseTool processes files and data in one of four distinct modes. Here is exactly what happens to your files in each mode:
Browser-Only Mode (Client-Side)
How it processes: Runs entirely inside your browser's local sandbox (JavaScript memory).
Where files go: Data never leaves your device and never touches any servers.
What you see: Instant results, works 100% offline. Used for JSON tools, base64 encodes, and text transformations.
Server-Only Mode (Sandboxed Server)
How it processes: Executed securely on our sandboxed Node.js server.
Where files go: Written to a secure, private temp directory on the server.
What you see: File processing queues. Files are deleted automatically after 10 minutes of session inactivity. Used for PDF tools and video processing.
Cloudinary Sync Mode (Cloud Persisted)
How it processes: Assets are synchronized with remote Cloudinary cloud directories using cryptographic session tokens.
Where files go: Stored securely as anonymized UUID hashes in the cloud.
What you see: Workspace asset lists that persist across devices and reloads. Purged instantly when session expires (after 10 minutes of inactivity).
Hybrid Mode (Combined Pipeline)
How it processes: Combines browser calculations with server tasks and remote Cloudinary persistence.
Where files go: Stored locally during processing and pushed to the cloud for workspace sync.
What you see: Combined workspace logs indicating client vs server tasks. Deleted completely after 10 minutes.
3. The 10-Minute Inactivity TTL Lifecycle
We enforce a strict data retention limit based on user activity. This is monitored by our database Time-To-Live (TTL) scheduler:
| Phase / State | Retention Details | What the User Sees |
|---|---|---|
| Active Session | Files persist in local temp folders and (if synced) in Cloudinary. The session is renewed with every page navigation or file operation. | The user sees all processed files, compression ratios, metrics, and download links in their Workspace. |
| Idle State (1-9 Mins) | Files remain intact. A background countdown runs silently waiting for new client inputs. | Workspace stays open. A warning banner appears if the session is close to expiring. |
| Expired Session | The session cookie expires. The database triggers a cascade delete, removing the workspace entry, deleting the local temp folder, and purging all files from Cloudinary. | The user is shown a clean slate on their next interaction ("Workspace Expired or Empty") and must start a new session. |
4. Transport & Storage Security
All files are processed behind industrial-grade security layers:
- SSL/TLS Encryption: All uploads and API calls are encrypted using TLS 1.3 protocol.
- Filename Anonymization: Upon upload, files are immediately renamed to cryptographically secure UUIDs. The original filenames are stored in session cookies and are never written to server logs.
- Sandbox Execution: Server-side utilities run inside isolated system scopes with restricted resource constraints, preventing unauthorized access.
5. Offline Mode Handling
When RaiseTool is run inside the PWA standalone wrapper, client-side tools (like JSON tools or calculations) process all data completely offline on your device. During offline status, no data is sent to the server or Cloudinary. All local changes are stored in client memory and synced securely only when connection is restored.