Uploaded files

Overview

Website visitors never upload files to Reignat. Only signed-in account users can upload images for their own profile or projects. Analytics events, visitor journeys, and the tracking script do not accept file uploads.

Account avatars

You can upload an avatar from account settings or during onboarding. We accept common image formats (PNG, JPEG, WebP, GIF).

Files are written to Cloudflare R2 under a per-user key such as avatars/{userId}/{uuid}.ext. Reignat stores only the resulting public URL on your account (for example on a custom asset domain). Objects are served with long-lived cache headers because each upload gets a new unique URL.

Avatars are used in the account menu and team surfaces so other members of a workspace can recognize you. They are not used for website-visitor analytics.

Project icons

Projects can optionally use a custom icon. If you do not upload one, Reignat falls back to the domain favicon.

Custom icons are stored on the project record in our PostgreSQL database as an image data URL — not as a separate object in R2. That keeps small branding assets with the project they belong to.

What we do not store

Reignat does not provide document storage, media libraries, CSV imports as persistent files, or visitor file uploads. Do not send passwords, payment card images, or other sensitive documents through avatar or icon uploads.

Deletion and retention

You can replace or remove an avatar and clear a project icon from the dashboard. When you delete a project, its custom icon stored on that project is removed with it. Account deletion removes profile data associated with your user; object storage and backups may retain orphaned avatar objects for a limited operational period before cleanup.

For privacy requests beyond self-serve controls, contact us using the details on the Privacy Policy page.