Last updated: 20 August 2026
1. The users' credentials are encrypted and stored locally on the device. The operating system limits the access to the data, making it accessible only to the app. Therefore, the credentials are only accessed and decrypted by the app itself;
2. The users' credentials are only accessed by the app when authentication against the Autoridade Tributária's authentication system is required (available at https://www.acesso.gov.pt/);
3. The authentication process and all the interaction with the e-fatura portal is performed directly between the app and the Autoridade Tributária's system, through an encrypted HTTPS connection;
4. At no other moment the users' credentials are transfered to other system(s) or stored anywhere else, beside what is described at point 1;
5. After the authentication, a session is set up between the device and the e-fatura portal, which is maintained also over an encrypted HTTPS channel.
6. The invoices provided by the e-fatura portal are stored locally on the device, on a database;
7. The invoices' information that is stored in the database is not encrypted. Nevertheless, and considering the architecture of the operating system, only the app can access this information;
8. All the information that is downloaded from the e-fatura portal to the device is handled exclusively by the app (locally on the device). Handling, in this context, means the categorization of the expenses' categories, calculation of benefits and the creation of statistics;
9. The app allows adding and changing invoices' data, that is then communicated to the e-fatura portal, through a communication session established according to point 3.
10. At no moment tributary data is sent to other systems, beside the ones described at point 9.
11. The app communicates with a support server (under hosting) exclusively to access app's configuration data, information on the CAE of the invoices' issuers, and to read and contribute public venue information;
12. Changes to the app's configurations mentioned on point 11 won't change the behaviour of the app, as described through this document;
13. In addition to the configuration data, the support server also stores the relationships between the issuers NIF and the issuers CAE, and the relationships between issuers NIF and other public details about the venues (crowd sourced by the app's users);
14. The support server do not receives nor stores credentials or trbutary information of the users;
15. Once the app gets deleted from the device, all the users' informations are deleted from the device, namely the credentials and tributary data;
16. The users' information is kept localy on the device while they are authenticated in the app and the app is installed;
17. Third-party services — advertising: In addition to the communications described in the points above, the app displays ads provided by Google AdMob. To serve ads, AdMob may collect device identifiers, including the Advertising Identifier (IDFA), as well as usage and diagnostic data;
18. Consent and tracking: Personalized advertising and use of the IDFA occur only after your explicit consent, requested through the iOS App Tracking Transparency permission. You can decline or revoke this consent in iOS Settings;
19. Attribution: The app uses Apple's SKAdNetwork to measure advertising performance without identifying you;
20. Usage analytics: The app uses Google Firebase Analytics to collect aggregated usage data (app interactions and events) in order to improve the app. These events may include parameters of the queries performed, such as the selected date range and activity scope, but do not include tax identification numbers or the contents of your invoices;
21. Crash reporting and notifications: The app uses Google Firebase Crashlytics to collect crash reports and diagnostic data, and Google Firebase Messaging to send you notifications, which involves registering a device identifier with Google;
22. Third-party sharing: The data described in points 17 to 21 is processed by Google as a third-party provider (see Google's Privacy Policy at https://policies.google.com/privacy). This data does not include your credentials, tax identification numbers or the contents of your invoices, which remain on the device as described in the points above;
23. Location and venues: When you use the venue search, the app requests your location and sends the coordinates to the Foursquare service in order to retrieve nearby venues. Your location is not stored on the developers' servers nor associated with your invoices;
By accepting the present PRIVACY POLICY, the user gives his consent to the app for it to use his credentials in order to connect and interact with the e-fatura service, as described on the points 3, 5 and 9;