Privacy Policy

What We Collect

• To create an account we collect your email address and a password, which our sign-in provider stores. During setup we collect your name. To set up cards we also collect the cardholder's legal name, date of birth, and billing address, which our card platform requires, and we record when and from which IP address the cardholder terms were accepted.
• To verify a business we collect its legal name, tax ID, business type, and address. For an individual account we collect the applicant's full name, date of birth, address, and the last four digits of their Social Security number. We do not ask for a full Social Security number or for copies of identity documents.
• When you add funds or save a payment method, you enter the card or bank details on our payment processor's hosted page. We keep a reference to the payment method, its brand or bank name, and its last four digits.
• For the virtual cards on your Layne account, we never receive or store the full card number or security code. We keep a card reference, the last four digits, the expiry date, and the name on the card. When you reveal a card in the app, the number renders inside our card platform's own secure frame.
• Spend data: transactions made on the cards issued for your account, the budgets you set, and the vendor connections you configure.
• Vendor API keys other than an AI provider admin key, and vendor sign-in tokens, that you connect are stored encrypted in a secrets vault, and we use them only to read billing and usage information, never to make changes to your vendor accounts. If you connect an AI provider admin key, it is stored in the same vault, and we use it only to read one entry from your organization's list of keys, to check that the admin key works, never to make changes to your provider account. From that entry we keep only identifiers, never a key's name or any part of a key. If you connect QuickBooks or Xero, their sign-in tokens are stored in our database rather than the vault, and are used to add your expenses to your books.
• If you connect a mailbox to find bills, we read your recent messages to find the ones that look like bills, send those to our AI model provider to read the vendor, amount, and date, and keep a reference to each message we read. For each message that turns out to be a bill, we keep the extracted bill along with the email's subject and the first 2,000 characters of its text. We do not keep the rest of your mail.
• If a Google Workspace admin allows it, we read which third-party apps your people sign into, who uses each one, and when, so we can suggest vendors to track. Discovery never creates a vendor or a card on its own.
• If you upload a card statement from your Dashboard or Vendors page to find your subscriptions, the file is held in private storage only while we process it. Card numbers we find in it are redacted before any of it is sent to our AI model provider or saved to your account, and the file is then deleted, and the deletion checked, before you see the results. A daily cleanup also removes any statement file older than 24 hours, in case a deletion was interrupted.
• For PDF statements, only the redacted transaction lines are sent to our AI model provider to read them.
• Bills you upload or forward to Layne are sent to our AI model provider to read the vendor, amount, and date. For a forwarded bill we also keep the email's subject and the first 2,000 characters of its text.
• On our public pages we record page views with a shortened hash of your IP address rather than the address itself, along with your browser's user agent, the referring site, and a random visit ID that your browser keeps for that tab only. The hash lets us count distinct visitors, but it is not anonymous. If your browser sends Do Not Track or Global Privacy Control, we do not record these page views. Our hosting provider also counts page views on these pages for us.
• When you are signed in, we record each session: your account, workspace, and email, when the session started and was last active, how many pages you viewed, your browser's user agent, your approximate location (country, region, and city) as reported by our hosting provider, and a shortened hash of your IP address. We use this to understand how Layne is used and who is signing in.
• To prevent abuse, page-view records on our public pages and sandbox sign-ins are counted against your IP address. Those counters hold the address itself, and a daily cleanup deletes them, usually within about two days of your last such request.

How We Use It

Who We Share It With

• Stripe: payments, the card program, and the cardholder details it requires
• Supabase: our database, sign-in, and file storage
• Vercel: hosting the app and this site, and counting page views on our public pages
• Resend: sending email such as alerts, digests, and invites
• Postmark: receiving forwarded bills, only where invoice forwarding is turned on
• Anthropic: the AI model that reads bills, bill-like emails from a mailbox you connect, and redacted statement lines
• Sentry: error monitoring
• logo.dev: vendor logos, which your browser loads by the vendor's web address
• Slack and Microsoft Teams: the alerts you choose to send there, only when you connect them
• QuickBooks and Xero: syncing expenses to your books, only when you connect them
• Helcim: card payments, only for accounts that saved a card with it before we moved to our current payment processor
• Google and Microsoft: mailbox and Workspace access, only when you connect them

AI Assistant Connections

If you connect Layne to an AI assistant such as Claude or ChatGPT, either through our hosted connector or by running our agent connector with an agent key, the Layne data the assistant looks up for you is sent to that assistant's provider so it can answer you, and is handled under that provider's privacy policy. We store only hashes of connection tokens and agent keys, never the tokens or keys themselves. For the hosted connector, we record each tool the assistant uses, with who used it, the outcome and, for some tools, the status the tool returned (such as issued or paused), in your activity log, without the other values it sent or received. Some tools, on either connector, also record what they did in your activity log the way the web app does: a spend request is recorded with its amount and merchant, and a new card with its vendor and last four digits.

How Long We Keep It

Your Choices

Contact

Questions about this policy: email support@layne.ai.