Privacy Policy — Moneman

This policy covers the hosted service at app.moneman.com and the Moneman mobile app when connected to it (together, the “Service”), operated by Elexron, a sole proprietorship based in Türkiye (“Elexron”, “we”, “us”). It does not cover a self-hosted installation running under a Moneman licence on somebody else’s own server: there, that licensee is the data controller of everything the installation processes, and this policy has no application to it. If you are using a self-hosted install and are unsure who to ask, ask whoever gave you access to it, not us.

This policy does not cover moneman.com, the marketing site you may have arrived here from — that site sets no cookies, runs no script, and has nothing to disclose. See its Security page for how it is built.

Data controller

İbrahim Halil Sanduvaç (trading as Elexron)

Contact

privacy@moneman.com

Data Protection Officer

We have not appointed one — Elexron is small enough that this is not yet required under applicable law. Every enquiry reaches the same people; write to privacy@moneman.com.

Most privacy policies describe one relationship: you and the service. Moneman has two, and they carry different obligations.

Account Data

Information about you as a registered user — your name, email, password, locale, timezone, avatar. We are the controller of this. This policy is mainly about it.

Ledger Data

The financial records your corporate account enters: transactions, accounts, budgets, debts, loans, invoices, and — where you use the business ledger — your OWN customers’ names, tax numbers and addresses on the invoices you issue them. Your corporate account is the controller of Ledger Data; we process it on your account’s instructions, as a processor, to provide the Service. If your customers have questions about their own data inside your books, that is between you and them — we cannot act on a request from someone who is not our user.

Directly from you, at sign-up and while using the Service:

• Name, email address, password (stored hashed — we cannot read it), and the locale and timezone you set.
• If you sign in with Google instead: the name and email address of your Google account and its unique Google account identifier, which we use only to recognise you the next time. We never receive your Google password.
• A profile photo, if you choose to add one.
• Your corporate account’s name, and — if you enable the business ledger — its legal name, tax number, tax office and address, since these appear on the invoices you issue.
• Everything you enter into your books: accounts, transactions, categories, counterparties, budgets, debts, loans, invoices, quotes, and any file you attach to one of them (a receipt photo, a bank statement PDF).
• Support messages you send us.

Collected automatically:

• The time and IP address of your last sign-in, and standard session metadata (IP address, browser user-agent) for the duration of your session — kept only to keep you signed in and to investigate abuse, never sold or shared.
• A push-notification token if you enable notifications on the mobile app, held by Expo (see §6) until you disable notifications or delete your account from the device.
• Ordinary web server logs (request time, path, status code) on the hosting infrastructure, retained briefly for operational troubleshooting.

We do not run analytics, advertising pixels or any tracking script. There is nothing to opt out of because nothing is collecting it — see §8 on cookies.

To provide the Service

Performance of the contract between you and us (our Terms of Service) — running your books, keeping you signed in, sending the e-mails a bookkeeping product has to send (verification, invites, plan-expiry warnings).

To keep the Service secure

Our legitimate interest in not being breached, and yours in the same thing — the session/IP metadata in §4, tenant-isolation enforcement, abuse investigation.

To comply with the law

Legal obligation — tax and accounting records your jurisdiction may require you, and by extension us as your processor, to retain for a statutory period, regardless of a deletion request (see §9).

To answer you

Legitimate interest / performance of the contract — support requests, and the AI parsing you explicitly trigger by uploading a file (see §6).

We do not process your data for direct marketing, and we do not sell or rent personal data to anyone, for any reason, ever.

These apply to the hosted Service only (app.moneman.com). A self-hosted install has none of them unless the licensee configures their own.

Google (Sign-In)

If you choose “Continue with Google”, Google tells our server who you are (your name, your email address and a Google account identifier) so we can sign you in or open your account. Google handles that sign-in under its own privacy policy; we do not share anything about your books with it. If you never use the button, nothing is exchanged.

Google (Gemini API)

If — and only if — you upload a statement or receipt to the AI reader, that file is sent to Google’s Gemini API to be parsed into draft entries. Nothing is written to your ledger from the result until you review and confirm it. Google processes this as our sub-processor under its own API terms; this is a US-based service, so this is an international transfer of whatever the uploaded file contains (see §7).

Expo (push notifications)

If you enable mobile push notifications, your device’s push token is held by Expo’s push infrastructure to deliver them. Expo does not receive the content of your books, only enough to route a notification to your device.

Our hosting provider

The server app.moneman.com runs on, and the database behind it, are operated by [hosting provider / location]. They can access the underlying infrastructure but have no application-level access to your books.

Exchange rate sources

Currency rates are fetched from public rate APIs (the Central Bank of the Republic of Türkiye, Frankfurter, and others) to keep conversions current. These receive only a currency-pair query — never anything about you or your account.

Our payment partner — Lemon Squeezy

When you buy a paid plan you pay on Lemon Squeezy’s checkout page. Lemon Squeezy is the merchant of record: it processes your payment, tax and receipts under its own privacy policy, and may process that data outside your country. It receives your name, email, billing address and payment details — card details never reach Moneman’s servers. We send it your corporate account’s numeric identifier and the plan you chose, so the payment can be matched to your account. In return we receive the subscription’s status and dates (plan, renewal, cancellation) and keep a log of those events, which can include the buyer name and email Lemon Squeezy reports. We do not use this log for anything other than operating your subscription and investigating billing problems.

Where a sub-processor above is outside your own country — Google, most notably — your data is transferred internationally to be processed. We rely on that provider’s own standard contractual safeguards (Google’s Cloud Data Processing Addendum, which incorporates the EU Standard Contractual Clauses) rather than negotiating our own, since we are a small customer of a very large processor. If you need a copy of the safeguard we rely on for a specific transfer, ask at privacy@moneman.com.

The hosted app uses exactly three cookies, all strictly necessary for it to function, none of them for tracking or advertising:

Session cookie

Keeps you signed in between requests. Expires when your session ends.

CSRF token

A security cookie that stops other sites from submitting forms to your account without your knowledge.

“Remember me” cookie

Only if you tick that option at login — keeps you signed in across browser restarts.

Because these are all strictly necessary for the Service to work, no consent banner is shown — that is what the strictly-necessary exemption in both the ePrivacy rules and KVKK guidance is for. The marketing site at moneman.com sets no cookies at all.

We would rather tell you exactly what happens than promise something the product cannot yet do.

• Ledger Data is kept for as long as your corporate account exists, and typically longer: accounting and tax law in most jurisdictions requires financial records to be retained for a statutory period (commonly several years) even after you would otherwise want them gone. We retain it for that period regardless of a deletion request.
• Exchange-rate history older than 180 days is deleted on a schedule. This never changes a figure already on your ledger — the rate used in a transaction is frozen onto that transaction when it is written, permanently, and is never recalculated from the rate table.
• You can delete your own account in the mobile app (Profile → Delete account), or ask us at privacy@moneman.com or through in-app support (the web has no button yet, so there we do it by hand within 30 days). What happens: access ends immediately; your Account Data (name, email address, profile photo, sign-in history and any link to a Google account) is removed; and if you were the only member, your company account is closed with you. If you are the only administrator of a company that still has other members, make someone else an administrator first. What does NOT happen: erasure of Ledger Data that the law requires us — via your account — to keep for the statutory period, or of entries you made in another company’s books, which stay with that company. If your jurisdiction gives you a stronger erasure right than that period allows for financial records, tell us at privacy@moneman.com and we will address it specifically.
• Support messages are kept for as long as needed to resolve the matter and for a reasonable period afterwards for quality and dispute purposes.

Subject to the limits in §9 above (we cannot erase what the law requires your account to retain), you can ask us to:

• Access — a copy of the personal data we hold about you.
• Correct — fix anything about you that is wrong. Most of your Account Data you can already edit yourself in the app.
• Export — everything in your books, as CSV, works today from inside the product for the ledger, reports and customer records, on any tier including free, and keeps working even if you stop paying.
• Delete or restrict — see §9 for exactly what this does and does not remove.
• Object — to a specific processing activity, where our legal basis for it is legitimate interest rather than a contractual or legal necessity.
• Withdraw consent — for anything we process on the basis of your consent (we currently process nothing on that basis alone; everything above rests on contract, legal obligation, or legitimate interest).

Write to privacy@moneman.com. We will respond within a reasonable time and, in any event, within the period the law applicable to you requires.

If you are in the European Economic Area, you also have the right to lodge a complaint with your local data protection authority. If you are in Türkiye, you may apply to the Kişisel Verilerin Korunması Kurumu (KVKK) under Law No. 6698 — see the Turkish version of this page for the specific application procedure under Article 11.

How this is actually built — the architectural claims here are the same ones the product’s Security page makes, checked against the source rather than written for either page:

• Every financial row belongs to one corporate account, and the boundary is enforced in the query layer and fails CLOSED — with no organisation to scope to, a query matches nothing rather than everything.
• Passwords are hashed, never stored or logged in plain text.
• Attachments are stored outside the web root and streamed through a controller that checks your rights first — there is no public URL to guess.
• Access within your corporate account is governed by a permission matrix, not a single admin/member toggle, so you can give someone exactly the access they need and no more.

Read more at moneman.com/security. Found a security issue? Write to security@moneman.com — we would much rather hear it from you than read about it somewhere else.

The Service is a business and personal bookkeeping tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us with personal data, contact privacy@moneman.com and we will remove it.

If we make a material change to this policy, we will change the effective date above and, for a change significant enough to matter to how you use the Service, notify you by email or by an in-app notice before it takes effect.

Privacy questions

privacy@moneman.com

Security issues

security@moneman.com

Everything else

hello@moneman.com