A little clarity about your data

Your client’s details
deserve thoughtful handling.

Here is how the current Reqelio workflow handles access, files, and client requests, along with the things you should know before using it.

This page describes our current product behavior. Reqelio is in early access. We do not claim security certifications, an uptime SLA, or enterprise compliance features that have not been established.

Who can access a client request?

Workspace owners sign in to manage their projects. Clients access an individual request through a secure, unguessable link, without creating an account. That link grants access to the request, so anyone it is forwarded to can use it. Share it privately with the intended recipient and avoid placing it in public documents or posts.

How files and answers are stored

Project answers are stored in the application database. Uploaded files are held in private object storage and retrieved using temporary signed access links. The storage bucket is not publicly browsable. The application and client request pages use HTTPS to protect data in transit.

  • Project access is checked against the signed-in workspace or the client’s request link.
  • Account passwords are stored as password hashes, not readable passwords.
  • The client workflow saves answers as work progresses, before the final brief is approved.

What to collect — and what to leave out

Use Reqelio for project goals, written answers, brand assets, supporting files, and brief approval. Do not ask clients to enter passwords, payment card numbers, recovery codes, or other account credentials. For access to a client’s tools, use those tools’ own invitation and permission systems.

Make sure you have permission to collect and use any personal information or copyrighted materials included in a client request. Only request what your project needs.

Cookies and the marketing website

The marketing site does not currently add advertising pixels or third-party analytics scripts. Fonts are served with the site. The platform uses a necessary session cookie to keep workspace users signed in. Infrastructure may process request metadata, such as IP addresses, to deliver and protect the service.

Retention and early-access limitations

Completed or archived projects remain accessible in the workspace; marking a project complete is not a data deletion request. Database backups are maintained for operational recovery. Enterprise retention controls, SSO, audit log packages, and contractual service guarantees are not part of the current public offer.

If your project requires a particular contractual, retention, or compliance commitment, confirm those requirements before uploading the relevant information. This product overview does not substitute for a signed data-processing agreement.

Product behavior reviewed September 8, 2026.

Your next project starts here

A clear brief.
A fresh start.

Bring the answers, the assets, and the approval together.
Then get back to the work you love.

Make room for good workFree early access · No credit card needed