Passport data and sync

Passport profiles are stored locally in your browser by default. eVisaFlow does not store passport images or OCR-recognized passport data on its servers. If you enable Google Drive sync, backups are stored in your own Google Drive.

Passport profiles are stored locally in the current browser by default. They are not uploaded to eVisaFlow just because you save a profile. If you turn on Google Drive sync, backup and restore files are stored in your own Google Drive.

Normal autofill uses the passport profile stored in your browser and fills supported fields on the official website from the extension. It does not need to send the saved passport profile to eVisaFlow servers. Data is sent to eVisaFlow only for account services such as sign-in, subscription checks, and optional OCR requests. See the Privacy Policy for the full data handling description.

Google Drive sync is optional. By default, passport profiles stay local in the current browser and are not uploaded to Google Drive. Only when you enable Google Drive sync in the eVisaFlow extension does the extension request Drive authorization and save backup and restore files in your own Google Drive. You can then use the same passport profiles across devices. You can turn off Drive sync in the extension at any time, or revoke eVisaFlow's Drive access from your Google account.

When you connect Google Drive, eVisaFlow creates or uses an eVisaFlow Passport Backups folder in your Drive. Passport profile data is stored in a passport_data.json file, and passport images may be stored as separate image files if you use image backup. Sync merges local and Drive records and keeps the newer record when both sides have the same passport.

No. Disconnecting Google Drive in eVisaFlow removes the connection used by the extension, but it does not delete files already stored in your Google Drive. To remove those backups, delete them directly from your Drive or revoke eVisaFlow access from your Google account.

Yes. Google Drive sync is optional. Without it, passport profiles stay in the current browser and can still be used for autofill on supported official sites. You only need Drive sync if you want backup and restore across devices.

When you use OCR, the passport image you choose is sent for OCR processing for that request. eVisaFlow does not keep passport images or OCR-recognized passport data on its servers after processing.

You can delete saved passport profiles inside the eVisaFlow extension. Local profiles are removed from your browser storage. If Google Drive is connected, eVisaFlow also tries to remove the matching Drive backup for that passport. If Drive is disconnected, or if you use bulk clear, review your Google Drive backup folder manually.

Yes. The extension data manager can export saved passport profiles to a local JSON file and import a compatible export later. Exporting passport images is optional because image files can make the export much larger. Always keep exported files in a safe place because they may contain passport data.

Account deletion removes the eVisaFlow account and server-side user data tied to that account. Passport profiles stored locally in the browser, or backup files stored in your own Google Drive, are controlled from the extension, browser, or Google Drive.

Uninstalling a Chrome extension usually removes that extension's local browser storage from that browser. If you enabled Google Drive sync, backup files in your Google Drive are not removed by uninstalling the extension.

You can turn off Drive sync in the eVisaFlow extension and revoke eVisaFlow's Drive access from your Google account's third-party app access settings. Existing backup files in Google Drive remain under your control and can be deleted from Drive if you no longer want them.