Privacy notice.

• Account data: your email address and name. Clerk handles sign-in, so we never see your password. If you sign in with Google, Clerk receives your Google account identity.
• Filing data: what the files you upload contain. That includes payer and payee names, taxpayer identification numbers (EIN, SSN or ITIN), addresses, phone numbers, account numbers, 1099 amounts and state filing details.
• Client details that you enter for each payer, such as name, EIN, address and phone.
• Help requests: the questions you type into the help assistant, and the support messages you send. A support message can name a file, its status and its counts. It doesn’t attach the file or its records.
• Billing data: a Stripe customer ID, what you bought, and the payment status. Card details stay with Stripe. We don’t receive or store any part of your card number.
• Get Notified sign-ups: your email address, and the name, firm and notes you choose to add.
• Operational logs: IP addresses, browser type, the pages you request, timestamps, and IRS acknowledgements. We use them to fix problems, limit abuse and keep an audit trail of IRS submissions.
• Usage analytics on our public pages. See Cookies and analytics.

• To convert your files, check them for errors, and produce IRIS XML, IRIS Portal CSV files, recipient copies and Massachusetts state files.
• To file returns with the IRS on your behalf.
• To bill you for licenses and filed forms.
• To send service email, such as a notice when a conversion fails, filing deadline reminders and replies to your support requests.
• To answer support questions, fix problems and prevent abuse.
• To understand how visitors use our public pages.

We don’t sell or rent your data. We don’t share it with advertising networks. We don’t use it to train AI models. We do send some data to Anthropic so that its Claude models can write answers for you and for our support team. The next section says what Anthropic receives.

These vendors and recipients process data to run their part of IRISfile:

• Internal Revenue Service: the returns you file, with all the payer and payee data in them.
• Vercel: hosting. It receives every request to irisfile.co, including uploads in transit, and keeps request logs.
• Neon: our Postgres database. It holds account, client, filing and billing records.
• Cloudflare: file storage (R2) for original uploads and generated files. Its Turnstile bot check on the Get Notified form receives browser signals and your IP address.
• Clerk: sign-in and sessions. It receives your email, name, password and session data.
• Google: sign-in with Google if you choose it, our business email (Google Workspace), and Google Analytics.
• Microsoft Clarity: session replay on our public pages.
• Stripe: payments. It receives your card details, your email, your organization name and what you bought.
• Resend: service email. It receives your email address, the file name and error counts of a conversion, deadline reminder content, and support messages.
• Notion: our list of Get Notified sign-ups. It receives the email, name, firm and notes you submit.
• Anthropic: AI answers. The help assistant sends Anthropic only the question you type, never your files or records, and we don’t store the question or the answer. Our support team also uses Anthropic’s Claude to read support messages and the files you share with us, and to draft replies. Those files can contain full 1099 data.
• Slack: our support workspace. It holds the messages and files you post there.

We also send data where you direct us, such as a webhook endpoint you set up. Webhook events carry IDs, statuses and counts only, never TINs, names, addresses or amounts. IRISfile doesn’t file with Massachusetts. You upload the state file yourself.

• Sign-in cookies. Clerk sets cookies such as __session and __client_uat to keep you signed in. The app doesn’t work without them.
• Google Analytics. Our public pages use Google Analytics 4, which sets the _ga and _ga_<id> cookies. It counts page views and clicks on our calls to action. In the European Economic Area, the UK and Switzerland, analytics storage is off by default. Ad storage is off for everyone.
• Microsoft Clarity. Our public pages also use Clarity, which sets cookies and records session replays: clicks, scrolls and page structure. Clarity masks what you type into form fields.
• Where they don’t run. Neither tool starts in the signed-in dashboard, in the FIRE file validator, or on the sign-in and sign-up pages. Google Analytics stops sending data when you move into those pages from a public page. If Clarity started on a public page first, it masks all content in the dashboard and the validator.
• Server-side events. When you submit the Get Notified form, or start or finish a checkout, our server tells Google Analytics that the event happened. Checkout events carry the amount, the number of forms and the tax year. These events never carry a TIN, a name, an email address or an account ID.

• Original files. Some uploads go to a background queue: files over 2 MB, files sent through the API, files with more than 10 payers, and files that need column mapping. We store the original file with the submission until you delete it. A file that waits for column mapping more than 30 days is deleted. A small file that converts at once isn’t stored in its original form.
• Records and generated files. Parsed records, IRIS XML, Portal CSV files, recipient copies and state files stay with the submission until you delete it.
• Filed returns. You can’t delete a submission after the IRS gives it a receipt. We keep it as the record of what we transmitted.
• Account data. Kept while your account exists. Deleting your account turns off your API keys and webhooks. It doesn’t delete your filing data. Write to us if you want that deleted too.
• Billing records. Kept in our database. Stripe keeps its own records under its policies.
• Get Notified sign-ups. Kept until you ask us to remove them.

We don’t delete data on a timer, except for the unmapped files above and a few short-lived system files. Uploads that never finish are deleted after 24 hours. XML made through our MCP server is deleted about 20 minutes after we make its download link.

You can access, correct, or delete your data at any time by writing to privacy@irisfile.co. We respond within 30 days. You can also delete a submission yourself in the dashboard until the IRS gives it a receipt. California, EU, and UK residents have additional rights under CCPA / GDPR / UK GDPR; we honor those on request.

Our security page describes how we protect your data.

IRISfile is a business tool. It isn’t directed to children under 13.

PIXELCOVE, LLC operates IRISfile from Andover, Massachusetts. Questions: privacy@irisfile.co.