Privacy

Privacy

ContactFile runs entirely in your browser. There is no server, no database, and no record of what you paste.

Parsing

Text you paste is parsed by JavaScript running locally on your device. No outbound request is made at parse time. Open your browser's Network tab while you paste — you'll see nothing leave your machine.

Filing to Google

When you file a contact, your browser signs in directly with Google and receives an OAuth token. That token never passes through ContactFile or 9W — it goes straight from Google to your browser, then from your browser to the Google People API. When you file, the only requests go to accounts.google.com and people.googleapis.com. Once data reaches Google, it is governed by Google's Privacy Policy.

Signing in with Google

There is no separate sign-in button. The first time you click "File with Google", Google opens its own sign-in window:

  1. Choose your Google account.
  2. On the permissions screen, tick the box next to "See, edit, download, and permanently delete your contacts". If you leave it unticked, ContactFile can't create the contact. Google user data, below, explains why the wording is so broad.
  3. Click Continue. The contact is filed, and the Google Contacts row shows the account you're connected as.

You stay signed in until you close or refresh the tab. After that, clicking "File with Google" opens the same window again. Google usually remembers your account, so it takes one click.

Google user data

ContactFile asks Google for two things: your email address, to show which account you're connected as, and access to Google Contacts, to create the contacts you choose to file.

ContactFile only creates contacts. It never reads, edits, or deletes the contacts already in your account. Google's permission screen lists the full contacts permission because Google offers no narrower one for creating contacts.

Your access token and email address stay in memory in your browser tab and are discarded when you close or refresh it. ContactFile has no server, so 9W never receives, stores, or sees your Google data.

Your Google data is never sold, never shared with or transferred to anyone else, never used for advertising, and never used to train AI or machine-learning models.

You can remove ContactFile's access at any time from your Google Account: myaccount.google.com/connections

ContactFile's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage

ContactFile uses the minimum browser storage needed, split by kind. Your Google OAuth token lives only in memory and is discarded when you close or refresh the tab. The Recent list is kept in sessionStorage, which clears automatically when the tab closes. UI preferences live in two places: your language choice, a 2-letter code, in a first-party cookie (cf_lang), and your light or dark theme choice in localStorage (contactfile-theme). No identifiers, never sent to any server, not shared with anyone.

Analytics

ContactFile uses Umami, a privacy-first platform that counts anonymous page views. It does not track individuals, does not set cross-site cookies, and cannot see what you paste or which contacts you file. The only data collected is that someone visited the page.

Independent audits

Don't take my word for it. These free public scanners independently grade the site's security and privacy posture. Last verified 22 Apr 2026 — click any to re-run:

  • Mozilla Observatory A+ — overall web security grade (CSP, cookies, HTTPS config).
  • Security Headers A+ — HTTP security header audit (HSTS, CSP, X-Frame-Options).
  • SSL Labs A+ — TLS configuration, certificate chain, cipher suites.
  • Webbkoll — GDPR-relevant properties (trackers, cookies, referrer behavior).
  • Blacklight — live-tests the page for trackers, fingerprinting, and third-party cookies.

To report a security issue, see security.txt.

Disclaimer

ContactFile is provided as-is, without warranty of any kind. 9W accepts no responsibility for errors in parsing, data loss, or any consequences arising from use of this service. You are solely responsible for reviewing contacts before filing them and for your use of the Google Contacts API.

Contact

Built by 9W, New York City. Questions or concerns: [email protected].