Skip to content

Terms of use and privacy

Last updated 2026-11-03. Beta software.

What Memoline is

Memoline is a back-office tool for money on Arc. It builds transactions that you sign with your own wallet, and it keeps a ledger of what happened on-chain. Memoline’s software is proprietary. The few files that show how it calls Arc’s contracts, and the Memoline MCP client (MIT licence, in its mcp folder), are published at github.com/vijaygopalbalasa/memoline. Memoline is operated by its author, Vijaygopal Balasa (the “Operator”). How to reach the Operator is under Changes and contact.

Non-custodial: we never hold your money or keys

Memoline’s servers hold no private keys and no wallet. Every payment is signed in your wallet and moves directly from your address to the recipients through Arc’s public Memo and Multicall3From contracts. Memoline cannot move, freeze, or recover funds, and it cannot undo a transaction you have signed. Nothing here is a bank, a payment service, a custodian, or a money transmitter.

Receiving at a one-time address: Memoline cannot make, recover or replace your keys, and cannot move a payment at a one-time address. Your keys come only from your wallet’s signature on /receive: if you lose that wallet, the payments at your one-time addresses are lost. If you register other keys, payments already made to the earlier keys can be moved only with those keys.

Plans and limits

Each workspace has the limits of its plan, shown on the Pricing page and in Settings: on Free, 5 members. No plan limits how many payouts a workspace makes or how many people it pays. Paid plans are sold by Dodo Payments as merchant of record, which handles card details, receipts and sales tax; the Pricing page says which plans are on sale. Memoline keeps only the plan, its status, its renewal date and Dodo's reference for it. Where pay per call is offered, a program can buy one answer at a time (an address screened, or an address's books over about the last day) in USDC on Arc through Circle Gateway, at the price the answer's 402 reply states. It is charged only when the answer is served; one payment buys that one answer, and the same payment fetches it again, up to three times within an hour, if the reply was lost.

API keys: Memoline keeps a key's name, its first characters, a one-way fingerprint of it (never the key), what it may do, for a key that prepares payouts its budget and the payees it may pay, who made or revoked it and when, when it was last used, and how many calls it made each month. A key acts only in its own workspace, and what it does is in the activity log.

Two-step sign-in: Memoline keeps, for your wallet address, the authenticator secret encrypted under a key only the server holds, one-way fingerprints of your unused recovery codes, and the time of the last code used. It is yours, not a workspace's: deleting a workspace keeps it, and turning it off in Settings deletes all of it.

Referrals: a workspace started through a referral link records which workspace sent it. The link is kept in the visitor's browser for 30 days. A referrer earns months of Pro, never money.

You are responsible for what you sign

Before your wallet prompts, Memoline checks every transaction of a payout on Arc and shows you the exact recipients and amounts. Read them. On-chain transfers are final; a payment to a wrong or unreachable address cannot be recovered by anyone. Memoline sets aside payments that the check predicts will fail, that Circle’s blocklist names or that one of three sanctions lists names (the US Treasury’s sanctions list (OFAC), the UK Sanctions List and the EU’s financial sanctions list), and shows each payee by name and whole address with anything worth a second look, but it cannot know whether an address belongs to who you think it does. It screens against those three lists only, never other lists, and when one of them was not read in the last 7 days it says so rather than calling a payee clear: an old list still sets aside the addresses it names, but a payee added to it since then is not caught.

When a payment into one of your links is recorded, Memoline checks the wallet that paid against the same lists. The payment is recorded whatever the lists say, because the money has already moved on Arc: a payment from an address a list names is marked on the link’s page with the lists that named it, you are told, and Memoline will not send a refund to that address. A split link that pays a wallet a list has named since the link was made cannot be paid until you change it. What to do with money from such an address is yours to decide, with your adviser.

You must have the legal right to make the payments you send, and you are responsible for any tax, sanctions, licensing, or reporting obligations that apply to you.

Beta, as-is, no warranty

Memoline is early software provided “as is” without any warranty, express or implied, including fitness for a particular purpose. Amounts are computed as exact integers and every ledger line is tied to an on-chain event, and the code is tested against Arc itself. Even so, you use it at your own risk. To the fullest extent the law allows, the Operator is not liable for any loss arising from your use of Memoline, including loss of funds, lost profits, or data loss. Where liability cannot be excluded, it is limited to what you paid for Memoline in the preceding twelve months, through Dodo Payments or as Memoline’s fee or per call.

What we store

Anonymous reconciliation (the form on the home page): nothing in a database. The address you enter is queried against Arc and the result, which is public chain data, is returned to your browser. The server keeps that result in memory for up to five minutes so a repeat request answers at once, then discards it.

Checking a payout file (no sign-in): nothing. The file and the paying address are used for one check and discarded: the paying address and the payees are compared with the three sanctions lists Memoline keeps (the US Treasury’s (OFAC), the UK’s and the EU’s), Circle’s blocklist is read from the token contract on Arc, and the payments are sent to Arc's RPC provider as a dry-run call, the same way any read of Arc is. Nothing is signed and no money moves.

Paying per call (no sign-in): for each payment, the paying address, the payment's nonce and a fingerprint of the signed payment, what it bought (its path, which names the address asked about), the price, Gateway's transfer id and when, kept as Memoline's record of what it sold. The answers themselves are not kept. Paid reads are counted per paying address for an hour, keyed by an HMAC as other limits are.

Signed-in workspaces: what you put in and what Arc shows for it, so that your books persist. That is:

  • your wallet address, from Sign-In with Ethereum;
  • which version of these terms your wallet address accepted when it signed in, and when;
  • when every session of your wallet address was last ended (by End every session, or by turning on two-step sign-in, which keeps the session that turned it on), so sessions made before then stay ended;
  • the payout files you upload (recipient addresses, amounts and the reference text you type), the name you give each payout, whether you chose “Private payroll: one payee per transaction” for each, and the transactions that result;
  • the recurring payout schedules you save: each schedule’s name, the paying wallet, the currency, its payments (addresses, amounts and references), whether its payouts are private payroll, and whether they go to one-time addresses, how often it repeats and until when, which payouts were skipped, whether and why it is paused, and who saved or last changed it; a deleted schedule is kept, marked deleted, so the payouts it made still name it;
  • for a one-time payout, each payment’s one-time address, its ephemeral public key and view tag, a hash of the payee’s registered keys and a seal only this server can make; never the payee’s keys or a payment’s private key;
  • the checks shown for each payee before signing (a first payment, an address that looks like another, a name set recently or shared, a contract), and who looked at them and when;
  • the addresses you choose to import, and the ledger built from all of it, including references decoded from the public on-chain memos of those addresses;
  • the names and kinds you give addresses in your address book;
  • your chart of accounts and booking rules, and for each line the account it is booked to, with who changed it, when and why;
  • each month you lock: its report (every statement, the totals by account and every line), the report’s SHA-256, who locked or unlocked it, when, and the reason given for unlocking;
  • your payment links (the amount, the reference, the description and the name you show to payers; for a split link, each wallet it pays, its part and the name you give it; for a link priced in another currency, that price and each quote given to a payer: the rate, where and when it was read, the amount in USDC or EURC and until when it holds), the payments found for them and the refunds you send;
  • the addresses of any webhook endpoints you add, with their signing secrets stored encrypted;
  • your workspace settings (name, legal name, business address and tax number, default currency, usual paying address, reporting currency, time zone) and the notification channels you add: Slack and Discord webhook addresses stored encrypted, and email addresses, which receive nothing until confirmed;
  • a record of what happened in the workspace (payments, settled links, refunds, finished payouts and imports, payouts waiting for approval and overdue invoices) for the notification list, kept until the workspace is deleted, and its deliveries, removed 30 days after they arrive or are given up. To limit confirmation emails, a keyed hash of an address is counted for a day and deleted within three days; the address itself is not stored for that.
  • the wallet addresses and roles of everyone added to the workspace, and the invite links made for it (who made each, its role, when it expires and who used it; only a fingerprint of the link itself);
  • who approved or rejected each payout, when, and the reason given for a rejection;
  • changes waiting for a second person: what each would change and the value before it, who asked, who decided, when, and any reason given;
  • the auditor links an admin or the owner makes: the label, the accounts, the currency and the dates each shows, when it ends, who made or ended it and when, and only a one-way fingerprint of the link itself; and every opening of a link, with its time and a one-way fingerprint of where it was opened from, never the address itself;
  • the Circle Gateway transfer files you upload, kept only for transfers to or from your accounts: status, addresses, amount, nonce and the Arc transaction of each batch;
  • the customers you invoice (name, and if you add them an email address for reminders, a billing address and a tax id), your invoices and their lines, with your business’s name, address and tax number as they were when each was issued, your recurring invoices, and a record of each reminder sent;
  • where the direct sync with Xero or QuickBooks is turned on and you connect it: the company connected, its sign-in stored encrypted, how your accounts and names map to its own, and what was sent to it and when;
  • an activity log of who did what in the workspace (payouts, payee checks looked at, links, refunds, invoices, members, settings, auditor links, changes asked and decided, months locked, imports and downloads), kept until the workspace is deleted, with email addresses masked and secrets left out.

Names and descriptions stay in your workspace, in the files you export, in what you send to Xero or QuickBooks, on an invoice’s pay page, and in the auditor links you make (a link shows your address book’s names for the counterparties, the workspace’s legal name, and where each line is booked: the account of your chart and why, which can name one of your rules); they are never written to Arc. An invoice’s pay page shows anyone with its link the invoice as issued, including your customer’s name, billing address and tax id. A link’s reference is written on Arc with every payment. A monthly statement reads your address’s balances and transaction count from Arc at the edges of the month each time you open it, and does not store them. Anyone holding an auditor link can read what it shows until it ends: 30 days after it is made unless another span is chosen (90 days at most), or sooner when an admin or the owner ends it; a link opens at most 30 times an hour, and downloading its CSV counts as an opening. An admin or the owner can download everything from Settings, and the owner can then delete the workspace there, which removes its records from Memoline's database; copies in the database host's backups expire on the host's schedule. You can also write to the Operator at hello@memolinepay.com to do it. Payments on Arc stay on Arc.

Memoline also keeps, for all of Arc, public data it reads itself: the names agents gave themselves in Arc’s ERC-8004 identity registry, read every hour; the exchange rates ExchangeRate-API and the European Central Bank publish, read at most once an hour; the addresses the US Treasury’s sanctions list (OFAC), the UK Sanctions List and the EU’s financial sanctions list name, with the date of each list, each read from its publisher once a day; one-time payment announcements (ERC-5564): every announcement of a payout made through Memoline, so a payee can find their own; and, for a day at a time, whether an address it checked had contract code on Arc.

Paying a link (no sign-in): nothing about the payer is stored beyond what Arc already shows: the transaction, the paying address and the amount, recorded as a payment of the link, and whether one of the three sanctions lists named that address when the payment was recorded, and which. The pay page keeps, in your browser only, the hash of a payment it sent (or a note that it asked your wallet to pay), so a reload checks that payment instead of offering to pay twice.

Receiving at a one-time address (no sign-in): nothing. The keys are made in your browser from your wallet’s signature. Their private part stays in your browser and is never sent anywhere; registering writes only their public part to Arc. Your browser reads your balances from Arc’s public RPC and signs each move itself.

The pricing waitlist (no sign-in): the email address you give, the plan you chose and your note, kept only to write to you when that plan opens. They are never shown to anyone, and are deleted a year after you signed up, or sooner when you ask. To ask, write to the Operator at hello@memolinepay.com. Never post your email address in a public issue.

On-chain: the memo attached to each payment contains an opaque payment ID and the reference you typed. For a one-time payment the memo names the payout and the row only, and the reference stays in your books. Do not put names, emails, or other personal details in the reference field: anything on-chain is public and permanent.

We count visits by where they came from (a campaign tag or the referring site’s name), never by who you are. Your browser keeps where you first came from for 30 days, so we can tell which channels bring sign-ups.

Operational data: public endpoints are rate-limited per client using an HMAC of the IP address (the raw address is not stored); these counters are deleted within three days. Memoline sets two cookies: memoline_session, signed, which keeps you signed in for up to 7 days (a session unused for 24 hours ends sooner), and memoline_ref, which keeps a referral link for 30 days. Its pages keep, in your browser only, memoline:pay:… (a payment a pay page sent, so a reload checks it instead of paying twice), memoline:refund:… (a refund you sent, for the same reason), memoline:recording:… (a payout transaction this tab is signing) and memoline:checked-file (a file you just checked, carried to the payout form for up to 15 minutes). The wallet code keeps its own: wagmi.store, rk-version, base-acc-sdk.store and keys starting with @appkit/. Aggregate, non-personal counts are published on the stats page, and the status page shows how many deliveries are waiting across all workspaces, never whose. Memoline itself runs no advertising, no analytics and no tracking pixel, and sells no data; what the wallet code sends when a page opens is under Third parties. When a browser blocks something this site’s security policy does not allow, it can send a report; Memoline logs only the rule, the blocked site and the kind of page (never the page’s own address, which can be a private link), and stores nothing else.

Where it runs: Memoline’s servers run in the United States, in Vercel’s iad1 region (Washington, D.C.), and its database in Neon’s aws-us-east-1 region (northern Virginia). For a data processing agreement, write to the Operator at hello@memolinepay.com.

Third parties

Memoline reads Arc through RPC providers (Alchemy, and QuickNode’s public Arc endpoint), and is hosted on Vercel with a database on Neon. The wallet code on every page contacts WalletConnect (Reown) at pulse.walletconnect.org and api.web3modal.org when the page opens, whether or not you connect a wallet, and connects to your wallet through WalletConnect when you choose that option; like any web request, those calls carry your IP address and browser details. Once a wallet connects, ENS names are looked up on Ethereum through PublicNode (ethereum-rpc.publicnode.com). When you pay or sign, your browser also reads Arc through Arc’s public RPC. On /receive your browser asks Arc’s public RPC about your wallet and each of your one-time addresses, and sends each move through it; that service can see they were asked about together. Where x402 is turned on, x402 payments are settled by Circle’s facilitator. Where pay per call is offered, those payments are verified and settled by Circle Gateway, which sees the paying address, the amount and what was bought, including the address asked about. Where email is turned on, it is sent through Resend. Where the direct sync with Xero or QuickBooks is turned on, the company you connect receives what is sent to it, and its sign-in is stored encrypted. Each of those services sees the network traffic necessary to do its job and is bound by its own terms. Memoline downloads the US Treasury’s sanctions list (OFAC) from the Treasury’s own service, the UK Sanctions List from the UK government’s (sanctionslist.fcdo.gov.uk), the EU’s financial sanctions list from the European Commission’s (webgate.ec.europa.eu), and exchange rates from ExchangeRate-API and from the European Central Bank’s rates through Frankfurter (api.frankfurter.dev); nothing about you is sent to them. Email you send to the contact address is forwarded by Spaceship, the domain’s registrar, to the Operator’s Gmail mailbox (Google).

Changes and contact

The date at the top is the version of these terms you are reading. Signing in accepts it: the message your wallet signs names the version. When these terms change, the date changes, and the next time you sign in your wallet asks you to accept the new version. Memoline keeps which version your address accepted and when. Earlier versions are available from the Operator on request. Questions, deletion requests and security reports: write to the Operator at hello@memolinepay.com. Never post personal details or a security problem in a public issue. These terms are governed by the laws of India, the Operator’s country of residence.