Privacy Policy
Passport Autofill Browser Extension & Web Platform (autofill.a2zso.com) • Last Updated: October 30, 2026
This Privacy Policy explains how Passport Autofill (“we”, “us”, or “our”), operated via autofill.a2zso.com and the Passport Autofill Chrome Extension, collects, processes, stores, transmits, and protects information when you use our browser extension, web dashboard, and related services.
Single Purpose: Passport Autofill is a browser productivity extension and workflow tool designed to help users, appointment processors, and visa specialists extract machine-readable passport data (MRZ and visual fields) and populate applicant details into online visa, medical booking (such as Wafid/GAMCA), and travel forms upon explicit user initiation.
Depending on which features you use, we collect and process the following categories of information:
A. Account & Profile Information
When you register or sign in, we collect your email address, full name, business/organization name, password credentials (hashed and managed by Supabase Authentication), account approval status, referral code, and notification preferences.
B. Passport Images & Extracted Applicant Information
When you upload, paste, or forward a passport image or MRZ text for scanning, the tool extracts and processes applicant fields required to fill booking forms, including: full name (first, middle, father, and last name), passport number, nationality, date of birth, sex/gender, passport issue date and expiration date, place of birth / issue place, national ID (if present), MRZ lines, and the cropped applicant/passport photo for form upload fields.
C. Scan Usage & Quota Audit Logs
Each time a passport scan is charged against your daily plan quota or scan point balance, our server records a usage log containing your user ID, a masked passport number (for example, EQ1****18 — full passport numbers are masked before logging), the applicant's full name, scan count, charge source (daily plan or points), and timestamp. These records are used to display your recent scan history, calculate daily scan totals, and prevent duplicate or unauthorized quota deductions.
D. User-Configured Form Defaults & Site Settings
You may configure default form values (such as destination country, city, marital status, religion, position applied for, contact email, phone number, national ID, and custom site-specific field rules). These defaults are stored in local browser storage (chrome.storage.local) and synchronized with your account database record so your presets remain available across sessions.
E. Device & Security Metadata
To enforce subscription device limits, prevent unauthorized account sharing, and protect against automated trial abuse, the extension and web server process a random extension-generated device identifier, device label, operating system/platform, browser user-agent string, and IP address.
F. Billing, Subscriptions & Payment Verification Data
When you purchase a subscription plan or scan points, we store your active plan tier, point balance, and transaction records. For international card/checkout payments processed via Polar.sh or Stripe, we store checkout session IDs, order IDs, customer IDs, and payment status (we never receive or store your full credit card number). For local bank or mobile money transfers (such as CBE, Telebirr, or Bank of Abyssinia), we collect the submitted transaction reference ID, payment method, amount, and optional bank/SMS confirmation text to verify payment authenticity.
G. Optional Telegram Integration Data
If you voluntarily link your account to our Telegram Bot, we store your Telegram Chat ID, Telegram username, first name, link timestamp, and notification preferences. When you forward passport photos to the linked Telegram bot, the queued image is delivered to your authenticated browser extension session so it can be processed locally in your browser.
1. Local In-Browser OCR & MRZ Parsing
Passport scanning, optical character recognition (OCR), and Machine Readable Zone (MRZ) parsing are processed locally inside your browser using a client-side recognition engine (WebAssembly). Uploaded candidate passports and extracted field queues remain stored locally in your browser's extension storage (chrome.storage.local, up to 50 queued items in your local upload list) so you can review, edit, and autofill them into target forms directly on your device.
2. Local Photo Cropping & Image Handling
Passport image preprocessing and applicant face-photo cropping are performed locally in your browser using HTML5 Canvas and client-side image processing. Raw passport images are never permanently stored in our database.
3. User-Initiated Form Autofill
Content scripts inspect HTML input, select, date, and file elements on enabled web pages only to match and populate applicant data when you trigger autofill actions (such as clicking Fill All Fields, Go / Open, or Scan Page). We do not harvest or transmit unrelated browsing history or form entries from third-party websites.
The Passport Autofill extension requests the following browser permissions solely to provide its core autofill and workspace synchronization features:
Stores your authentication session token, cached account/quota state, saved default field values, queued candidate passport records, enabled-site rules, and UI preferences in chrome.storage.local.
Renders the persistent Passport Autofill side panel workspace alongside visa and appointment booking forms so you can review extracted fields and trigger autofill without leaving the active tab.
Injects field-detection and autofill helper scripts into the active tab to identify form inputs, dropdown menus, date pickers, and photo upload fields and populate them with applicant data upon user command.
Detects the active tab URL/domain to apply site-specific field mappings (e.g., Wafid medical forms vs. custom portals) and opens or focuses booking or dashboard tabs when requested by the user.
Schedules lightweight periodic background tasks in the extension service worker to keep subscription quota status synchronized and poll queued passport deliveries from your linked Telegram bot.
Required because users run Passport Autofill across numerous regional government e-visa portals, embassy websites, airline systems, and medical appointment domains worldwide, as well as to sync authentication with autofill.a2zso.com.
- Local Browser Storage (chrome.storage.local & localStorage): Uploaded candidate passports in your queue, extracted passport fields, cropped applicant photos, custom field defaults, and session tokens remain stored locally in your browser until you clear the queue, sign out, reset defaults, or uninstall the extension.
- Supabase Database & Server Storage: Account profiles, authentication records, saved form defaults, subscriptions, and payment/point ledger records are stored in our managed Supabase database and server data store for as long as your account remains active, or as needed to comply with financial and tax record obligations.
- Scan Usage & Audit Logs: Masked scan usage logs are retained on a rolling basis (up to the most recent 5 entries per user in the primary usage log records and up to 2,000 rolling entries in server usage logs, alongside aggregated daily scan counts) to enforce daily plan limits and display usage analytics.
- Telegram Queue & Link Tokens: One-time Telegram account linking codes expire automatically after 15 minutes. Passport photos forwarded via the Telegram bot are held in a temporary server memory queue only until fetched by your extension (or up to 24 hours if undelivered, capped at 30 queued items per user) and are removed immediately upon delivery to your extension.
- Email Verification & Password Reset Codes: One-time verification codes (OTPs) expire within 10 to 15 minutes after issuance.
Limited Use Commitment
The use of information received from Google APIs and Chrome extension APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:
- We only collect, use, and transfer user data to provide and improve the user-facing features of Passport Autofill described in this policy.
- We never sell, rent, or trade user data, passport images, or extracted applicant information to third parties, data brokers, or advertisers.
- We never use or transfer user data for personalized, retargeted, or interest-based advertising.
- We never use or transfer user data to determine creditworthiness or for lending purposes.
- We do not allow humans to read your passport or form data unless we first obtain your affirmative agreement for specific support/debugging assistance, or where strictly necessary for security abuse investigation or to comply with applicable law.
We share data only with the following categories of third-party service providers strictly as necessary to operate the platform:
- Supabase: Provides user authentication, session management, and PostgreSQL database hosting for user profiles, subscriptions, and saved defaults.
- Polar.sh & Stripe: Process international subscription and scan-point checkout transactions and billing webhooks.
- Local Payment Verification Endpoints (CBE / Telebirr / Bank of Abyssinia): When you submit a local bank or mobile-money transaction reference, our server queries the corresponding bank receipt verification endpoint solely to confirm the transaction reference, date, and amount.
- Email Delivery Providers (SMTP / Resend): Deliver transactional account verification OTPs, password reset links, and important account/billing notifications.
- Telegram Bot API: Used only if you explicitly link your Telegram account to receive notifications or send passport images from Telegram to your extension queue.
- Encryption in Transit: All communications between the browser extension, the web dashboard, and our APIs are encrypted via HTTPS / TLS.
- Passport Number Masking: Before recording scan usage logs on the server, passport numbers are automatically masked (retaining only the first three and last two characters) to minimize sensitive data exposure.
- Authentication & Access Controls: API endpoints require cryptographically signed Bearer tokens issued via Supabase Auth, and administrative routes are restricted by server-side role verification.
You have full control over your personal data and queued applicant records:
- Delete Queued Passports & Local Extension Data Immediately: You can delete individual candidate passports or click Clear All in the extension's Upload/Candidate list at any time to immediately erase them from chrome.storage.local. Uninstalling the Chrome extension also permanently deletes all local extension storage on your device.
- Modify or Clear Saved Form Defaults: You can view, edit, or reset your saved form defaults at any time from the extension Setup tab or the web dashboard.
- Unlink Telegram: You can disconnect your Telegram account at any time from the web dashboard or via the unlink command in the Telegram bot, which immediately removes your stored Telegram Chat ID and clears any queued images.
- Request Complete Account & Server Data Deletion: You may request access to, correction of, or permanent deletion of your user account, profile, saved defaults, and associated usage logs by contacting us at [email protected]. Verified deletion requests are completed within 7 business days (excluding transaction records required to be retained for legal or accounting compliance).
If you have questions, concerns, or data deletion requests regarding this Privacy Policy or our data handling practices, please contact us through any of the following channels: