AUTOCONTRACT · PERSONAL / PROFESSIONAL
Privacy policy
Updated: 2 November 2026 · 1.20.5 (73)
1. Scope and contact
AutoContract 1.20.5 (73) prepares Romanian and international vehicle sale contracts on the device. The application provider is publicly identified as Selberg. Application and privacy contact: selberg90@gmail.com. The identity or address entered by an individual app user as their own data controller is not presented as the provider’s legal identity.
2. Documents and data processed
Depending on the selected features, processing can include names, addresses, Romanian personal identification numbers (CNP), identity-document details, vehicle details and VIN, photographs and PDF pages, transaction details, drawn signatures, contracts, drafts and saved person/vehicle profiles. Information is entered manually or extracted by OCR. Users verify the information and establish the appropriate right and lawful basis for processing other people’s data. The in-app notice does not automatically record a client’s consent for every subsequent use.
3. Local OCR, camera and imports
PaddleOCR, running through ONNX Runtime and OpenCV, processes images on the device. The app also includes Google ML Kit components. Its document-reading code does not send photographs or OCR results to an online recognition service or conversational AI service. Camera access is used when you choose to take a photograph; imports use the Android picker. Images/PDFs can be copied into private app storage for processing and preview. Cleaning up these temporary copies does not delete originals from your gallery or destinations you selected.
4. Temporary sessions and the Professional archive
New free and Personal sessions and their OCR copies are temporary; previews remain private and cleanup occurs when finishing/cancelling and after ongoing operations release their file references. An explicitly saved PDF remains at the destination you chose. Personal does not create an in-app archive, client/vehicle database or Drive archive for new sessions. Professional supports explicit archiving; retaining photographs and synchronising with Drive are separate choices. Existing data and archives are not automatically erased when a subscription expires and remain recoverable and deletable.
5. Optional Google Drive
Connecting and synchronising with Drive are optional and require Google authorisation and the relevant in-app choices. Connecting alone does not automatically upload every document. Depending on archiving choices, synchronisation may include PDFs, associated photographs, fields and saved profiles. The local catalogue can contain personal data even when files are downloaded on demand. Drafts remain local. Google provides the connected account’s identifier, name and email address. The drive.file scope covers files created by the app or authorised for it. The app does not request your Google password; access tokens handled by AutoContract code are held in memory. Transfers use HTTPS; no additional end-to-end encryption or unlimited Drive storage is promised.
6. Deletion, retention and disconnection
The user/data controller chooses and manages document retention and their obligations towards data subjects. A retention setting is not a promise that all data is automatically erased after a fixed period. Storage cleanup of eligible files after synchronisation checks can retain the local catalogue. Local deletion does not automatically erase Drive copies. Manage those files and the Drive trash separately. Disconnecting stops use of the selected account but does not delete copies or automatically revoke Google authorisation; revoke access in Google account settings if needed. Uninstalling/clearing app data can remove local data, but does not erase exported or cloud copies. The provider cannot remotely erase data held exclusively on your phone or in your own Drive account.
7. Google Play purchases and technical services
Personal purchases and Pro subscriptions use Google Play Billing, separately from Drive authorisation. The app uses product identifiers, purchase tokens and purchase status to verify, acknowledge and restore entitlements. These checks communicate with Google; local OCR does not mean every app feature is offline. Google Play Billing does not automatically give the app the purchaser’s Gmail address. AutoContract does not receive complete card numbers or card security codes from Billing. Google states that ML Kit SDKs may transmit technical device, app and performance information for diagnostics and usage analytics. This is separate from documents processed locally.
8. Export, printing, sharing and reports
Users initiate export, printing, sharing and backups; documents go to the chosen destinations and apps. Backups may contain personal data and should be stored appropriately. An unexpected closure can create a local technical report containing app/device version and error structure, excluding document content, exception messages, file paths and Logcat. The AutoContract reporting feature does not send it automatically: users choose whether and with whom to share it.
9. Website, language preference and contact
This is a static website hosted on GitHub Pages. It has no document-upload forms, web accounts, payments, analytics scripts or first-party tracking cookies. It stores only the RO/EN language preference locally in the browser (localStorage); clearing site data removes it. That preference is not sent to an AutoContract server. The hosting provider may process technical visitor data, including IP addresses, to operate and secure its service under its own policy. Links to Google Play, Google or email use the selected external services. Contact selberg90@gmail.com about the app or data actually received by the provider; data held exclusively by an app user may require action on the device or in Drive.
10. Google API use and updates
Information obtained through Google APIs is used for the archiving, synchronisation, search and download features requested by users, not data sales, personalised advertising or AI model training. Its use and transfer are subject to the Google API Services User Data Policy, including Limited Use requirements. This description reflects verified features and is not a certification or blanket GDPR compliance guarantee. It is updated when features or processing change.