Privacy Policy
Last updated: 14 Nov 2026
1. Data Managed
RapiRamp may store account, ramp, supplier, FFB transaction, cash, delivery, mills, partners/DO holders, DO, truck, location, photo, document, activity history, and synchronization history data.
2. Purpose of Data Use
Data is used to run ramp operations, display reports, manage team access, support offline-online synchronization, internal audit, backup, and operational assistance.
3. User Control
Ramp owners and authorized admins are responsible for managing users, roles, ramp access, backups, and retention according to their own business policy.
4. Data Protection
RapiRamp provides access controls, upload limitations, activity history, and private-page protection. Final security still depends on hosting, devices, passwords, connection, and user discipline.
5. Data Sharing
Data must not be shared with other parties without a valid basis, permission, or business need. Users are responsible for reports, downloads, backups, and files shared outside the application.
6. Ecosystem Integrations
Partner API access starts disabled. An authorized ramp owner/manager must deliberately enable it and approve data sharing. Scoped token-based read-only endpoints provide minimized aggregate metrics and FFB lineage references, not supplier identity, coordinates, documents or payment details. Keys are revocable and expire. Users remain responsible for ensuring a valid processing basis and controlling partner use.
7. Contact Form
If you submit a contact inquiry, we retain your name, email, optional phone and organization, topic, message, and a hashed anti-spam signal. We use it to respond to inquiries, demo requests and partnerships. A copy may be emailed to the configured operational recipient, such as info@rapisawit.com. Authorized Superadmins can review and manage leads; send a request through the official contact channel for correction or deletion. Do not send passwords through the contact form.
8. Account Recovery and Email Verification
For account recovery, email verification and invitations, RapiRamp stores the registered address, verification status, hashed one-time links, expiration and use timestamps, and hashed request counters. Links are sent through SMTP configured by Superadmin; neither passwords nor raw tokens are written to audit history. Reset links expire after 30 minutes, while invitations and verification links expire after 24 hours. An optional maintenance CLI job cleans expired tokens. Changing a recovery address requires the account password and confirmation in the new mailbox.
9. Cloud Trial and Data Export
Newly registered ramps on the Cloud service may receive a trial for the duration shown during registration (21 days by default). When it expires, operational access closes until an administrator activates a plan. Expiry does not automatically delete stored data. Authorized ramp owners can request and download a system-prepared ZIP export; its table and file coverage depends on the available export capabilities and should be verified before it is treated as a sole backup. Export files are stored privately and downloads require authentication and authorization.
10. Backup and Retention
Users must create regular backups and define their own data retention. Data loss caused by negligence, device, hosting, connection, or operational errors remains the user's risk.
