Privacy Policy
The short version
- We collect what it takes to run your workspace, and no more. We never sell it or use it for ads.
- No one else can see your records unless you share them: one expense with someone you have linked with, or a Split link you turn on.
- Records of how the service is used say where you went, never what you saw, and are deleted after 30 days.
- AI features send only what a question needs to our AI providers, and only when you use them.
- No advertising or tracking cookies. Export or delete your data from Settings whenever you like.
Overview
veyra, operated by Amiel Brencis Salipande, is a private money workspace. This policy explains what we collect, why, who helps us run the service, and the control you have.
Your workspace is scoped to you. No other user can browse, search, or open your records. There are two exceptions, both deliberate and always started by you: if you link with someone and choose to share an expense with them, specific details of that one expense are sent to them; and if you turn on a link for a Split bill or group, anyone with that link can read it. These are described under Sharing with people you link and Split links below.
Information we collect
- Account details: when you sign in with Google, our authentication provider gives us your name, email address, and profile photo to identify your workspace.
- Financial information you enter: accounts, balances, transactions, bills, loans, income, budgets, goals, categories, and notes. This is the content of your workspace.
- Split: the names you give people and groups (often people who don't use veyra), what each bill was for, its shop, notes of up to 1,000 characters, and the places you pick (a name, an address and a point on the map). We use them only to show you your Split, and on a link you turn on.
- Statements you import: when you upload a bank or card statement, we store the rows read from that file so you can review them before anything is recorded, along with a fingerprint of each row used to recognise duplicates on a later import. The uploaded file itself is not retained, and a document password, if you supply one, is used only to open the file and is never stored or logged.
- Location, only if you allow it: when you record a transaction you may attach where it happened. If you grant your browser’s location permission, we store the coordinate, its accuracy, and the time it was taken, and we send the coordinate to a mapping provider to turn it into a place name. This is entirely optional: deny or ignore the permission and no location is collected, and you can remove a saved location from any transaction.
- A city for the weather, only if you add one: type a city in Settings, or tap Use my location and allow your browser’s location permission once. Either way we store only a city’s name and its point to about a kilometre, and show the weather there beside Home’s greeting. With Use my location, your browser rounds your device’s position to about a kilometre before sending it to us; we use it once to find the city and never store it, and nothing follows you afterwards. Nothing is ever worked out from your internet connection. Remove the city in Settings and it is deleted.
- A note you send from the help center: if you tell us a help article didn’t help and write what you were trying to do, that note and the article’s title are emailed to us through
Resend. The email does not carry your name, address or account, and we keep it only in our inbox. Like every request, the sending itself is recorded under your account (see Usage and technical data). The note’s words are not.
- A report you send: when you report a problem, an idea or a question from the help center or an error screen, we keep what you write, the kind of page you were on (for example /bills/[id], never the record itself), whether you were on a phone or a computer, the version of the app, and, from an error screen, the error’s code. If you add screenshots (up to four), each is made smaller and redrawn (in your browser and again on our servers), which drops the hidden data a photo carries, such as where it was taken; they are kept in our database and are never sent to anyone else. A report and its replies are visible only to you and to the operator, who reads it beside your account’s name and your recent failed requests (see Usage and technical data). Starting over does not delete a report; closing your account does.
- Notes from us in the app: now and then we show a short note when you open veyra: to everyone, or, rarely, to you alone. We keep which notes you have seen, so none shows twice; that record is cleared if you start over. A note meant for you is visible only to you and to us; we keep the note and who it was for, as the record of a message we sent. To choose who a note goes to, the operator sees account names in Veyra’s private console, as on its People page, and, for a note already sent, which accounts have seen it and on what day.
- Usage and technical data: to operate, secure, and debug the service we record each request your browser makes: the page or address it went to (for example /transactions), whether it succeeded, how long it took, and the account it came from. We record where you went, never what you saw: no amounts, balances, account names, merchants, notes, search terms, or anything you typed is stored in these records. Messages you send the assistant are not recorded here either: only that a request to it was made. When a request fails, we also record which version of veyra was running and, where it can be told, the place in veyra's own code where it failed, never the error's message, which can repeat what was on screen. If a screen crashes in your browser, your browser tells us the kind of error and which page (with any record's identifier removed from the address), and nothing else. Content-security reports from your browser are kept the same way: the page, with any record's identifier removed, and the site it tried to load from, nothing else.
- Page performance: your browser sends anonymous measurements of how quickly a page loads and responds. We keep the page section, measurement, value, device class, and app version for up to 30 days. These measurements contain no account, visitor code, address, or page content; the operator sees only grouped figures.
- Visits while signed out: when you open Veyra's public pages without being signed in (the home page, the legal pages, the sign-in form, a Split link someone sent you), we record each page you open (including moving from one of those pages to another), the approximate country and city our hosting provider estimates from your connection (none for the sign-in and sign-up pages), whether the visit looks automated (and if so, what kind: a search engine or an AI crawler, say), whether the page went on to run in your browser, and an anonymous code. The code lets us count how many different people visited that day and see the order in which one visitor moved through the public pages that day; it is never linked to an account. It is built from your connection and browser together with a random value that is deleted once the day is over (by 8 a.m. Philippine time the next morning at the latest), so it cannot be traced back to you or linked to another day. Your IP address is never stored, and no cookie is set to count you. Once you have signed in, your browser keeps a cookie that says only that it has (or that it was the operator's), never who you are, so your later visits while signed out are recorded only as such, with no location and no anonymous code, and left out of these counts instead of being counted as someone new. None of this is recorded for visits made while signed in.
- Your country while signed in: when you use Veyra signed in, the country (never the city) our hosting provider estimates from your connection is added to a daily tally that is not linked to your account: an entry holds the day, the country, and a code built from your account and that day's random value. The random value is deleted once the day is over, so afterwards no entry can be traced back to you. The dashboard shows only how many accounts used Veyra from each country, and counts any country with fewer than three accounts on a day together, without naming it. The tally is kept for 30 days.
- Assistant usage: Agent (our in-app assistant) runs on a paid service that charges by the amount of text processed, so for each question we also record how much text it involved (a token count for the question and the answer), how long it took, and whether it completed. This lets us see what the feature costs and how often it fails. It is a measure of size, not of content: these usage records never contain what you asked or what Veyra replied, and nothing in them can reconstruct it. Your conversations are kept separately, as described next.
- Your Agent conversations: so your conversations follow your account from one device to another, we store what you asked, what Veyra replied (which can quote your own figures), and the cards it drafted, with where each got to. Photos you send are still never stored; a conversation only notes that one was sent. Conversations are deleted automatically 90 days after their last message, deleting one from History removes it from our servers, and clearing your workspace removes them all. They are included when you export your data.
- How long we keep it: pages you open are deleted after 30 days; a request that failed after 180 days, except a request refused because no one was signed in, and security records (attempts to reach files or pages that aren't public, and your browser's content-security reports), which are deleted after 30 days. Each successful request the app makes in the background is deleted after 3 days, and before that it is added to a daily count per feature (how many requests and how long they took, with no account attached), kept for 90 days. Preview records are deleted after 3 days. Browser performance samples are kept up to 30 days. Nothing in these records is kept indefinitely. Agent conversations are deleted 90 days after their last message. From the assistant records we keep one daily total per account (how many questions and how much text, that day) so we can see costs across a month after the individual records are gone. We chose a daily total deliberately: keeping the individual records for longer would mean keeping a log of exactly when you used Veyra, and a daily total answers the same question without it. Your financial records are kept until you delete them or close your account; those things are separate. In Split, a deleted bill or person, and a bill's earlier versions after an edit, are kept as history in your workspace (and in your data download) until you start over or close your account.
Cookies and browser storage
veyra uses no advertising or analytics cookies, and does not track you across other websites. What it does keep in your browser:
- Sign-in cookies, set by our authentication provider so you stay signed in. The service cannot work without them.
- One short-lived cookie remembering the page you were heading to when you were asked to sign in, so you land back on it. It lasts 30 minutes at most and is cleared once used.
- One layout cookie that says only whether this device shows the phone or the desktop layout, so pages arrive already laid out for your screen. It holds one of those two words, is the same for anyone using the device, and lasts a year.
- One signed-in-before cookie, set once you have signed in on this browser, that says only that you have (or that it was the operator's), never who you are, so your signed-out visits are not counted as a new visitor's. It lasts a year.
- Your browser’s storage, for small preferences (such as hiding amounts on screen) and a copy of your Agent conversations, so the assistant opens quickly. That copy is kept per account but stays on the device after you sign out: on a shared computer, use a private window, or clear this site’s data when you are done.
How we use your information
- to provide the workspace: store your records and compute balances, summaries, and forecasts;
- to send the notifications you enable (such as bill reminders);
- to keep the service secure, prevent abuse, and diagnose problems;
- to comply with legal obligations.
We do not sell your data, and we do not use your financial records for advertising.
Service providers
We rely on a small set of processors to run veyra. They handle data only to provide their service to us:
- authentication:
Clerk, with
Google sign-in;
- database and application hosting:
Neon and
Vercel;
- transactional email such as reminders:
Resend;
- merchant and brand logos:
logo.dev and
Brandfetch (Brandfetch looks up the merchant name you type — in Split, only the shop named after “at”);
- turning a coordinate into a place name, only when you attach a location or move a pin in Split, and suggesting places as you type in Split’s Place field, only what you type there:
LocationIQ;
- map imagery for a saved location, only when you view it: the map area around the saved coordinate is requested from
Mapbox, or
CARTO when the primary map fails to load;
- the route drawn across a day’s map, only when you open that day and only when more than one of its transactions has a saved location: the saved coordinates for that day are sent to Mapbox, in order, to draw a line that follows roads. They are reduced to about 11 metres of precision before they are sent, which is coarser than a typical location fix. Nothing else about the transactions goes with them: no amount, merchant, account, time, or description;
- the weather beside Home’s greeting, only when you add a city: the city you type, or your device’s point rounded to about a kilometre, is looked up once with
OpenStreetMap when you save it, and the city’s point, to about a kilometre, is sent to
MET Norway for the forecast. Nothing else goes with either: no name, account, email, or money;
- rate limiting and abuse protection:
Upstash;
- the operator’s issue tracker, only when the operator files a report you sent:
Linear. The issue holds the report’s words, its number, the kind of page, the device type, the app’s version and any error code, never your name, email or account, and never your screenshot. Before it is filed we check for your name, an email address, a phone number, an amount or a link, and send nothing until they are taken out;
- the optional AI assistant, only when you enable it (see below).
Exchange rates (from Wise, or the European Central Bank's rates, through
Frankfurter, when Wise's are unavailable) are fetched by our servers. Nothing that identifies you is sent to any of them.
Where your data is stored
Our database, our servers, and our rate limiter run in Singapore. Some of the providers listed above process data in other countries, including the United States, for example, our authentication and AI providers. We choose providers that protect the data they handle for us, and they may use it only to provide their service to us.
Sharing with people you link
veyra lets you split an expense with someone and keep track of what is owed. If that person also uses veyra, you can link with each other by exchanging a signature that you generate and send yourself. Linking is mutual and can only be started deliberately: nobody can add you.
Once linked, when you split an expense with them, record a refund on one, settle a balance, lend or borrow, or forgive a balance, the details of that record are sent to their workspace so they can accept it into their own books, decline it, or say they had already recorded it. What crosses is limited to a fixed list:
- the amount, currency, and date;
- for a split or a refund, the label you gave the expense, and the merchant and its logo if set: a settlement, a loan, or a forgiveness carries no label of yours;
- the place name and coordinate, if you attached a location;
- your name as it appears on your account.
Your own name for the person stays in your workspace. When someone uses a signature you generated, you are told, and they appear in your list of people under the name on their account.
You can unlink at any time from their page. Unlinking ends the link for both of you, withdraws anything still waiting for an answer between you, and tells them. Your history together and your balance with them stay as they are: nothing is deleted.
When you export your data, it includes these shared records: the ones you sent and the ones you were sent: each one’s amount, currency, dates and answer, the label where it carries one, and the person under your own name for them. It never includes a place or coordinate, and nothing from the other person’s workspace beyond what the record already showed you.
Linking also shares your name and profile photo with that person, so you each appear as yourselves rather than as initials. This is the photo on your veyra account, which you control and can change or remove at any time. It is held by our authentication provider, not stored by us, and it is shared only with people you have linked with. Removing it, or unlinking, stops it being shown.
Nothing else is shared. Your private notes, categories, budgets, payment methods, account names, and balances are never sent, and the other person cannot see any record you did not choose to share. Only records involving a person you have linked with are ever eligible; everything else stays entirely in your workspace.
Split links
In Split you can turn on a link for one bill or one group. Anyone who has the link can open it without a veyra account, and read it but not change it, until you turn it off. Links do not expire on their own; making a new link stops the old one at once.
A link shows that bill — or that group’s bills and members — with each expense, its notes and places (with map imagery from Mapbox), what each person paid and owes, and the names of everyone on it. It shows your name as you chose it in Settings, or your first name from your sign-in profile if you have not chosen one. It never shows your accounts, balances outside Split, other bills or groups, or anything else in your workspace. A bill in a group shows the group’s name. If someone opening the link taps Open in Maps, that place’s point goes to Google Maps.
Treat a link like the bill itself: whoever you send it to can pass it on. We record a visit to a link like any signed-out visit (see Visits while signed out), without the link’s address, which is the key to it; our hosting provider’s request logs hold the full address briefly.
AI features
veyra includes AI features, such as Agent and the explanations some screens offer. They run only when you use them: when you ask a question or tap to explain something, the specific data needed to answer is sent to one of our AI providers, Cloudflare (its Workers AI service) or
OpenAI, to generate a response. Agent tries its models in a set order, so if one cannot answer, the same question goes to the next.
Voice. If you dictate to Agent, the recording is sent to OpenAI to be transcribed, and the words come back to your message box for you to check. veyra does not store the recording, and the words are kept only if you send them, as part of your conversation, like any other message.
Photos. If you send Agent a photo (a receipt, usually), it is made smaller in your browser and sent with your question, so the assistant can read it and draft the transaction for you to confirm. veyra does not store the photo, on our servers or in your browser: it is used for that turn of the conversation and the next, and a reopened chat only notes that a photo was sent.
Reports. To turn a report you sent into an issue for the developer, the operator may send its title, its words and the kind of page to the same AI providers. Who sent it, and its screenshots, are not sent.
Keeping and deleting your data
We keep your workspace data for as long as your account is active. You are always in control: from Settings you can export your workspace, or permanently delete it. Deletion removes your records from the live service; residual copies in encrypted backups age out on our providers’ ordinary schedules. Deleting your workspace leaves your sign-in account in place, so you can start fresh. To close your account entirely, choose Close my account in Settings (you'll be asked to confirm it's you) or email absalipande@gmail.com and we will delete it. When an account is deleted, everything veyra holds about it is deleted with it automatically: your workspace, your settings, your Agent usage, the reports you sent with their screenshots and replies, and the record of your requests, and anyone linked with you is unlinked. An issue already filed from a report stays in our tracker; it never named you. We keep only our own records (a decision we made about your account, such as a limit on Agent, and any note we sent you), and other people keep their own records of what you shared with them, without a link to you.
Who is behind Veyra
veyra is built and operated by one person, Amiel Brencis Salipande, its sole developer. There is no team, no contractors, and no staff with access to your workspace.
This matters for your data rather than as an introduction: it means the only human who can reach the systems holding your records is Amiel Brencis Salipande, and that access is used to run and repair the service, never to browse your finances. Requests you send to the address below are read by the same person.
To keep veyra running there is an internal dashboard showing whether the service is healthy and the usage records described above: which addresses were requested, by which account, and whether they worked; and, for signed-out visits, counts by page and place and the order of pages one anonymous visitor opened in a day; and how many accounts were active each day, and from which countries, as counts. It is built so that it cannot display anyone’s financial records: it can show that a workspace posted a transaction and how many ledger lines it created, and it cannot show the amount, the account, or the merchant. Each night Veyra also checks every workspace's balances against its own records (the same check you can run on your workspace) and keeps only how many problems it found across all workspaces, never whose or which.
While Agent is free, the same dashboard keeps it fair. It lists each account by its name and profile photo, with when it last signed in and was last active, and how many messages it sent to Agent, never an email address, and never what was asked. From that list the operator can limit how many Agent messages an account can send a day or a week, for a set time. A limited account sees how many it has left and when the limit ends; nothing else in veyra changes. Each limit, the operator’s reason for it, and when it was set, changed or lifted are kept as a record for as long as the account exists; the reason is never shown to the account it is about. You can ask for yours at the address below.
Security
We take reasonable measures to protect your information, including per-user data isolation, encryption in transit, and access controls. No online service can be guaranteed perfectly secure, but protecting your financial data is a core priority.
We record attempts to probe the service, or to open pages and functions reserved for the operator: the address asked for (without its query), what kind of attempt it looked like, and the account if one was signed in.
Your rights
You can access and export your data at any time, correct it by editing your records, and delete your workspace. Depending on where you live, you may have more rights over your personal data. Under the Philippines’ Data Privacy Act of 2012, for example, you have the right to be informed, to access, correct, and delete your data, to object to its processing, to take it with you, and to complain to the National Privacy Commission. To use any of these rights, contact us at absalipande@gmail.com.
Children
veyra is not intended for anyone under the age required to form a binding contract in their jurisdiction, and is not directed at children.
Changes and contact
We may update this policy from time to time; material changes update the date above. Questions or requests can be sent to absalipande@gmail.com.