Candeia service privacy
This page describes the current operation of the portal, the account and the Candeia identity application flow. Last updated: September 7, 2026.
Who provides the service
Candeia is an institutional and technological project in formation. The account provides access to the system, but it is not equivalent to citizenship or to a civil identity issued by Candeia. See the institutional status.
Contact for the project administration regarding questions and data requests: govcandeia@gmail.com.
Account by email or Google
The service uses Google Firebase Authentication to create and authenticate accounts, confirm email addresses, recover access and offer two-step verification. This flow may process the account identifier, email address, sign-in method and data required for authentication security. When Google is selected, the provider may share basic profile data used for access, such as name and photo. The portal does not request access to Gmail, Drive or contacts.
When creating a password for Candeia, use a unique password. Authentication is processed by the Firebase service; GOV.CANDEIA does not maintain its own database containing the password in readable plaintext. When signing in with Google, authentication takes place through Google itself.
Session and data in this browser
Authentication uses browser-session persistence. Appearance preferences and public files may also be stored locally or in cache. Signing out ends the active session; closing the tab does not delete data that has already been sent to Candeia services.
Identity application
For verified accounts, the current identity flow may register an application in connected Candeia services. When a person submits the application, civil data provided in the form — such as name and date of birth — and, where requested by the flow, a photograph and signature may be sent for processing. Media are stored in Firebase Storage at server-authorised paths, and the connected service maintains the status of the application and its validations.
Submitting an application does not mean that a CIC has been issued. The flow itself distinguishes preparation, validation and later stages of issuance. Do not submit an RG, CPF, passport or other documents that the screen does not request.
Security and providers
Firebase Hosting serves the portal; Firebase Authentication processes authentication; Firebase Storage may store media submitted through the identity flow; and processing services on Google Cloud infrastructure handle connected operations. The portal also uses Firebase App Check mechanisms (abuse protection) and reCAPTCHA to reduce abuse and protect requests, which may involve technical security signals from the device, browser or connection in accordance with provider policies.
See Firebase privacy and security and the Google Privacy Policy.
Retention, access and deletion
The service does not yet publish a single automatic deletion period for an account, application or submitted media, nor does it currently offer a complete self-service interface for these requests. Closing the tab or signing out does not delete records kept by connected services. To request access, correction or deletion, use the contact above. Confirmation that you control the account may be required.
Never send a password, authentication code, TOTP code or personal documents that were not requested by email to prove control of the account.
Security reports
Use the contact above and describe the page and the observed behaviour without including credentials or third-party data.
The principles in the constitutional proposal are set out in Privacy, private life and communications; they do not replace this description of the current service. The Terms of Use explain the conditions for accessing and using the portal and the available functions.