Sign-in and profiles
The app uses Firebase Authentication and links signed-in accounts to an active Funerivo profile. Blocked or unassigned profiles do not receive regular access.
Funerivo combines sign-in, roles, tenant assignments and technical checks. Correct configuration and use by the operator remain essential.
The statements on this page describe features of the reviewed source code. They do not constitute certification or a blanket assurance of legal compliance.
The app uses Firebase Authentication and links signed-in accounts to an active Funerivo profile. Blocked or unassigned profiles do not receive regular access.
Permissions for creation, editing, deletion, document access, upload, export, user management and audit viewing are managed separately.
Cases, users, journeys and audit entries are assigned to a tenant. Database rules check membership and permissions for read and write operations.
Uploads and retrieval use protected server functions. Storage paths are checked against the tenant, file and document ID; confidential files require the relevant permission.
A SHA-256 checksum is stored for uploaded documents. When a file is retrieved, this can be used to check whether its contents still match the stored checksum.
Selected professional actions are logged with the user, role, time and case reference. Existing audit entries cannot be updated or deleted under the Firestore rules.
Uploading a document requires verified retention grounds and a date. The operator must determine the professionally appropriate period for each document type.
Deactivated tenants switch to a restricted archive mode. Deleting cases and tenants requires permissions and additional protective conditions.
Data protection and legal certainty do not come from software alone. Responsibilities, contracts, access policies, deletion processes and actual use must suit the business.
This website uses no analytics, advertising or tracking services and no external web fonts. The enquiry form is used for personal contact.