Earmark
Security and data
This page describes the current build. It is not a security certification or an independent audit.
What Earmark does not do
During early access, Earmark does not hold, receive, or move money. You make transfers through your own bank.
What data Earmark stores
The application database stores business details and an account identifier; deposit payers, amounts, dates, and notes; account categories, allocation rules, calculated allocations, and running totals. Business records can include an industry, EIN, revenue estimate, account nickname, last four digits, and routing number.
Other records supported by the build
The database also supports bank-connection and balance records; billing and subscription identifiers and statuses; simulated payment and schedule records, including counterparty account details; tax records; activity records, including changes, actor identifiers, and an IP-address field; financial-document metadata, extracted financial figures, analysis summaries, and suggested allocation rules; and conversation messages. Which records exist depends on the features you use. These data categories do not mean live bank connections or money transfers are available.
Marketing signups
If you submit a marketing signup form, Earmark stores your email, which list you joined, when you joined, and any referral campaign information in the link you used. For early access, it also stores the name, business name, monthly revenue range, industry, and whether you chose to hear about one-tap transfers. One-tap notification signups are stored separately from early-access signups.
How it is protected
Sign-in is handled by Clerk. Deposit and allocation API routes check for a signed-in user and check that the requested business belongs to that user before returning or changing those records. This describes those routes, not a claim that every feature has been independently audited.
Questions
The Contact page describes the current availability of a contact channel.
Contact Earmark