Privacy
Last updated 12 November 2026
Laik w alayk is a shared record of what two people owe each other. It keeps a running account between you and someone you have agreed to share one with. It moves no money, holds no funds, and is connected to no bank or payment network.
This page says what the app collects, why, who else sees it, and how to get rid of it. It is written to be read, not to be survived.
What we collect
Things you type
- Your identity: name, email address, a username, and optionally a phone number and a profile photo.
- Google or Apple sign-in, if you use it: Google or Apple tells us an identifier for your account with them, your email address and your name. We keep the identifier and that email address, with when you linked them and when you last signed in that way, so we know it is you next time.
- Your ledger: the entries you record — amounts, currencies, dates, what each one was for, any reference or invoice number, due dates, and notes you leave on an entry.
- Files you attach: receipts, invoices, contracts and any other file you attach to an entry or to the bill of a split — photos (JPEG, PNG, GIF, WebP or HEIC) and documents: PDF, Word, RTF, Excel, CSV, PowerPoint, OpenDocument and plain text files. We keep each file's name, type and size with it.
- Your network: who you are connected to, the connection requests and book invitations you send and receive with any message on them, who you have blocked — with the reason, if you gave one — and whether you reported them when you did.
- What you send us: complaints you file in Help & complaints, your replies to us, and reports you make about a person, an entry or a note.
Things the app records as you use it
- Your devices: platform, a device name, and a notification token so the app can reach you. With the token, the phone app — from version 1.2.0 — also tells us its version and which of our newer features it supports, such as the number on its icon. Sessions are held as rotating tokens.
- An audit trail — a record of what was done in the app, by whom, and when. It includes what was recorded, confirmed, disputed or amended on a book; every sign-in, with whether it was by password, Google or Apple, and from the app or the website; signing up, password resets, linking or unlinking a Google or Apple sign-in, and turning two-step sign-in on or off; connection requests; blocks, unblocks and reports — who, and of what kind, never the words of a report; complaints filed; allowing AI reading or turning it off; and agreeing to the Terms of Use. It is deliberately permanent — it is what makes a disputed figure answerable — so it stays after you unblock someone and after you delete your account. Our administrators can read it.
- Your agreement to the Terms of Use: which version of the Terms of Use you agreed to, and when.
- Logs — described under Logs below.
There is no advertising, no tracking across other apps or sites, and nothing is sold.
With your permission, receipts are read by an AI service
Attaching a file and having it read are two different things. You can attach files to any entry and to any split bill, and they are simply stored with it. With your permission, the first photo or PDF you attach to an entry or a split bill is also sent to Anthropic, an AI service, so a model can read the figures off it and fill the form in for you. The file and what it shows — amounts, items, names and dates — leave our servers and are processed by a third party. This also happens when you scan a receipt from Home, before you choose a book.
Nothing is read until you allow it. Until you do, the files you attach are only stored. You can change this at any time in your profile. Turned off, reading is off everywhere — on the website and on every phone you use — and nothing you attach after that is sent until you turn it on again. We keep your answer and when you gave it, and the audit trail records each time you allow AI reading or turn it off. If what is sent, or the service that reads it, changes, we ask you again. We can also switch reading off for everyone or for some books; then nothing is sent from there, whatever your answer.
Only a picture (JPEG, PNG, GIF or WebP) or a PDF is ever sent. On the website and in the current phone app, only one is read for each entry or split bill you fill in: once one has been read, the files you attach after it are stored without being sent. (An older version of the phone app has each photo it attaches read.) Along with the file go your name and — for an entry on a book — the other side's name as the book shows them, the currency, the app's lists of currencies, categories and projects, so the model can tell who paid and match what it reads to the form, and the language you use the app in, so the reading is written in it. The file's name is not sent, and nothing else about you or the book is. For a scan from Home, no name goes with it, not even yours, and the currency is the app's base currency, AED. Word, Excel, CSV and text files are kept with the entry but never sent, and neither are PowerPoint, RTF and OpenDocument files or HEIC photos.
A PDF is sent only when it has up to 10 pages — or, when its pages cannot be counted, when it is smaller than 3 MB. A longer or larger one is kept, like any file, but not read.
A photo's location is never sent. Before a photo goes to be read, we make a new copy of it without the details a camera stores inside the file — where and when it was taken, and with what. If a photo cannot be copied that way, it is kept but not read. The file stored with your entry is the one you attached, as it is: if your camera saved a location in it, anyone who can open the file can see it. A PDF is sent as it is.
From version 1.2.0, the phone app takes the location and those other details out of every photo it takes or picks from your photos, and out of every scan, before it sends it to us — so those reach us without them. A file you choose from your phone's files, and a photo sent from the website or from an older version of the app, is stored as it was sent.
What comes back is a suggestion sitting in editable fields — nothing is recorded on your behalf, and you can change every figure before it is saved. If you would rather a file was never sent, type the figures in by hand, save the entry, and then add the file from the entry with Add files: a file added that way is never read. Where reading is off, nothing you attach is sent.
When a receipt or a transfer slip is read, the form also gets its Details: what it says, line by line — the items and totals, how it was paid (a card by its last 4 digits only), the sender and the receiver and their banks, and the purpose of payment. When you save the entry, the Details are saved with it, and the other side of the book and our administrators can see them, as they can see the description. Card, IBAN and account numbers are cut to their last 4 digits before anything reaches the form, Emirates ID numbers and web and email addresses are taken out, and the reader is told not to copy balances, one-time codes or private people's phone numbers. You can change or empty the Details like any other field until the entry is confirmed, and removing the file they were read from can clear them too.
Anthropic deletes what we send it, and what it sends back, within 30 days, unless the law requires it to keep them longer or it needs them to enforce its usage policy. If its automated safety systems flag them as breaking that policy, Anthropic may keep them for up to 2 years, and the scores those systems gave them for up to 7 years.
Help & complaints, reports and blocks
Complaints. When you write to us in Help & complaints, we keep what you chose as the category, the subject, what you wrote, and the conversation that follows, together with your name and email address as they were when you sent it. They are read by our administrators — the people who run the service — and by nobody else.
Reports. A report is a complaint that points at a person, an entry or a note. We keep your reason and which person, entry or note you reported. To review it, an administrator can see what you reported: the person's name, email address and profile photo, or the entry or note itself. The person you reported is never told who reported them. Our audit trail records only that a report was made and of what kind — not your words.
What we do about a report. An administrator may hide a note, remove a profile photo, change a name or a username, remove an entry's description and attached files, or suspend or close an account. A hidden note shows as removed to everyone in the app; its text is kept with the report, so the decision can be reviewed.
Entries. An administrator may remove an entry's description and attached files when they break the Terms of Use. That covers every word typed on the entry — its description, reference and any name written into it, and the same words wherever a split bill or a repeating entry copied them. Its amounts, dates and the people on it are never changed, and the entry stays in the book for both sides. When the entry is a share of a split bill, removing its files also removes the files attached to the bill, which are the same files every share shows — so they are gone for everyone in the split. Removed words and files are deleted, not hidden: unlike a note's text, they are not kept for review, nor in the audit trail, and they are gone from our backups once those copies expire.
Complaints and reports are kept after the account that sent them is closed, with the name and email address they were sent under, because they are the record of what was raised and what was done about it.
Blocks. We keep who you have blocked, when, the reason if you gave one, and whether you also reported them. The person you block is not told. Unblocking deletes the block itself; the audit trail still records that you blocked them and later unblocked them. Books you already share stay as they are — a block stops new contact, it does not rewrite a ledger.
The QR code and document scanners
On Android, the phone app reads QR codes with Google ML Kit. The camera picture is processed on your phone, and the code is read there. ML Kit may send Google information about the scanning feature itself — your phone's make, model and operating system version, the app's name and version, an identifier for the installation, how long scanning took, the size of the image it worked on, and any error codes. Google says it uses this for diagnostics and usage analytics, encrypts it in transit, and does not pass it to third parties. What Google lists does not include the camera picture or the codes you scan. The iPhone app reads codes with Apple's built-in Vision framework, on the phone.
From version 1.2.0, when you scan a receipt in the Android app, it finds the edges of the page with Google's ML Kit document scanner, which Google Play services provides on your phone and may first download from Google. Google says the whole scan happens on the phone, and Google's terms for ML Kit say it processes pictures on the device and does not send them, or what it finds in them, to Google. ML Kit may still send Google metrics about how its features perform and are used, which Google says it uses to measure, fix and improve them and to detect misuse; the list of what ML Kit collects that Google publishes, quoted above, does not cover the document scanner. Where the document scanner cannot start, the app uses a simpler scanner of its own, or the camera — both on the phone. The iPhone app scans with Apple's built-in VisionKit document camera, on the phone. Either way, the pages you keep become one file — a photo, or a PDF when there are several — and it reaches us like any file you attach. A scan from Home is sent to us as soon as it is made, before you choose a book; if you save it in no entry or split, we delete it, as we do any file left behind by a form that was never saved.
The number on the app icon
From version 1.2.0, the iPhone app shows a number on its icon: the entries waiting for you to confirm, your own entries the other side disputed, and the requests to connect waiting for your answer — the two numbers on the app's bottom bar, added together. Our server counts them from your books and your network, which it already holds, and the number arrives with a notification or when you open the app. It is cleared when you sign out. Anyone who can see your home screen can see it. On Android the app puts no number on its icon; your phone may show a dot, or its own count of notifications, as it does for any app.
Logs
- Server access logs. Like almost every website, our web server records each request it receives: your IP address, the date and time, the page or address requested — which, when you look someone up, includes the email address, phone number, username or code you searched for — whether it succeeded, the page you came from, and your browser type. They are kept for 14 days and used only to keep the service secure and to find faults.
- App logs. The application records errors and what happened to the emails it sends — including the address each one was sent to. They are kept for 14 days and used only to find faults and to answer “did my email arrive?”.
Who else sees your information
Anyone who knows your email address, phone number or username
Anyone with a verified Laik w alayk account who knows your email address, phone number or username — or has your profile code, the one in your QR code — can look you up, so that they can invite you to a book or send you a connection request. They see your name, username and profile photo, and whether your email address is verified. They are not shown your email address or phone number, and they have to type the whole of it: there is no browsing and no partial search. Someone you have blocked cannot find you this way — they get the same answer as for an address nobody uses.
A phone number is matched however it was typed — with or without the country code, with spaces, dots or dashes, or in Arabic digits — so someone who has your number in their contacts can find you by it. Before you are connected they also see whether you already are, and the month your account was made (never the day). A number leads to an account only once that account’s email address is verified.
Numbers are typed in by their owners, and nobody checks them yet. So someone else may have added yours to their account. If that happens, write to support from your own account; once you have shown the number is yours — by a WhatsApp message or a call from it — support moves it from the other account to yours, and its holder is told by email. A number on an account whose email address was never verified goes, once that account is a day old, to a member with a verified email who adds it, and its holder is told the same way. You can add your own number in My profile, and remove it, at any time; changing it — or adding one back after removing it — is allowed once every 30 days. Each change is emailed to your account’s address. None of these emails contains the number.
The other side of a book
This is the part worth understanding properly. A book is shared. The person you share it with sees every entry on it, the files attached to those entries — whichever of you attached them, and whenever — the notes, and your name and profile photo. They can open and download each file. That is the point of the product — an account only settles if both sides can read it.
When a bill is split between several people, each person is shown only their own share, the total, and how many ways it went. They are not shown who else was in the split or what anyone else owes. When the bill is split by items, each person also sees the items that were theirs, and, for an item they shared, how many shared it — never who, and never anyone else's items. But the files attached to the bill are shown to everyone in the split, with their share — the same files for all of them — so whatever the bill itself shows, they all see.
Sharing your code or an entry
You can share your code, or an entry, from the app or the website. Sharing happens on your device: the app makes the picture or the link and hands it to whatever you choose — WhatsApp, email, anything your phone offers. We are not sent the picture, and we do not learn whom you shared it with.
A link to your code shows a stranger nothing about you: they see an invitation to the app. Someone signed in with a verified account who opens the link or scans the code sees your name and username, even if your name is not on the picture — the same as scanning it today. If your code has gone further than you meant, get a new one: the old code and link stop working. Your username stays the same, so anyone who has it can still find you.
A picture of an entry shows its number, its status and the day the picture was made, its amount, date and due date, its type, which way it runs, who raised it and the name of the side sharing it. When the entry is in another currency, it also shows the amount in the book's currency and the exchange rate; when it is a share of a split bill, the bill's total and how many ways it was split. It shows the other side's name only if the person sharing turns it on, and its description only if they choose to (it starts off when the other side wrote it). It never includes files, notes or the reason for an objection. Either side of a book can share an entry from it. Please share an entry only with people who should see it.
A link to an entry opens only for the two sides of the book (for a company, anyone who signs in for it), after signing in. Anyone else is told there is no entry there for them, exactly as for a link that never existed. Link previews in chat apps show only the app's name. Our administrators can still see an entry when handling a report.
Our administrators
The people who run the service can open any account in our admin console. They see its details — name, email address, phone number, username, profile photo, the devices signed in to it and when each was last used, whether a Google or Apple sign-in is linked, and its recent activity in the audit trail — and its books: the balances, every entry, each entry's notes (including any hidden by moderation), the documents attached to it and to the bill of a split it is a share of — the files themselves, which they can open — and its history.
The console does not wait for you to ask. We use it to answer support requests and complaints, to act on reports, to find out why something went wrong — a notification that did not arrive, an email that was refused — and to keep the service secure, and for nothing else. From it, administrators can also correct an account's details, reset its password, sign it out everywhere, or suspend or close it.
Service providers
- Anthropic — reads an attached receipt when you have allowed it, as described above.
- Google (Firebase Cloud Messaging) — delivers push notifications. Receives the notification text and a device token — and, for an iPhone on version 1.2.0 or later, the number for the app's icon.
- Microsoft 365 — sends email notifications.
- Amazon Web Services — hosts the application and its database, in Frankfurt, Germany.
- Google (ML Kit) — reads QR codes and, from version 1.2.0, finds the edges of a scanned receipt in the Android app, on the phone, as described above.
- Google (Sign in with Google) and Apple (Sign in with Apple) — let you sign in with those accounts. On our website's sign-in and sign-up pages your browser loads their sign-in buttons from Google's and Apple's servers, so they receive your IP address and browser details when you open those pages, even if you do not use the buttons, and Google can see its own cookies if you have any. In the phone app, Google's or Apple's sign-in opens only if you choose it.
Your information is not sold, rented, or shared with anyone else, other than where we are legally obliged to.
How long it is kept
Entries are kept for as long as the book exists, because they are also the other party's record of what was agreed. A ledger that one side could erase would not be worth keeping.
Files are stored on the server, separately from the database. Either side of a book can add files to an entry later, unless it has been voided or the book is archived; adding a file never changes a figure. The side that raised an entry can remove the files its own side attached until the entry is confirmed or voided (a file the other side added stays), and the person who split a bill can remove the bill's files until someone's share of it has been confirmed or voided; after that they stay with it, as part of the record, unless an administrator removes them because they break the Terms of Use. Verification codes expire within minutes. Sessions expire and rotate. Complaints, reports and the audit trail are kept as described above, and logs for 14 days. How long Anthropic keeps what we send it to read, and what it sends back, is described above.
Backups. Every night the database and the stored documents are copied to a backup, kept with our hosting provider, so the service can be recovered after a failure. Each nightly copy is kept for 30 days, and the copy taken on the first of each month for 400 days — about 13 months. Anything deleted from the service — a closed account, a block, a document, a profile photo — stays in the copies taken before it was deleted until those copies expire. Backups are used only to restore the service and to check that it can be restored.
Deleting your account
You can delete your account from inside the app — Profile → Delete my account — or on the web from your profile page. Because it cannot be undone, it asks you to prove it is you: your password, or — in the phone app, for an account that has no password because you sign in with Google or Apple — signing in with Google or Apple again. The website asks for a password; an account without one can set one first with Forgot your password? on the sign-in page. The delete-account page has every route.
What is removed from the service immediately:
- your email address, phone number, username, profile photo and password
- any Google or Apple sign-in linked to the account
- every device and notification token
- every session, on every device
- your connections, and any blocks you had set
- files you uploaded but never attached to an entry or a split bill
Copies already in our nightly backups are not changed; they expire on the schedule above, so the last of them is gone about 13 months after you delete your account.
What Anthropic already has from files sent to it to be read, and the names sent with them, is not changed either; how long Anthropic keeps it is described above.
What happens to the books you shared:
- They are archived — the entries stay and stay readable to the person you shared them with, but nothing more can be posted to them. Any unanswered invitation you had sent or received is withdrawn.
What stays, and why:
- Entries on shared books, and your name on them. They are the other party's financial records as much as yours. Removing them would rewrite someone else's account of what was agreed, and leave a balance they could no longer explain. Your name stays so those entries still mean something to the person holding them. The files attached to them, and to the bills of splits you made, stay with them too.
- Complaints and reports you sent, with the name and email address they were sent under, as described above.
- The audit trail of what was done in the app, as described above, with your email address and username taken out of it.
If entries were waiting on you to confirm or dispute when you left, they stay unanswered — the app tells you how many before you confirm.
After deletion you cannot sign in, nobody can find or contact you through the app, and the email address and username are released.
Your rights
You can see and correct most of what is held about you from inside the app, and delete your account as above. If you want a copy of your data, or you want to object to how something is handled, write to us at the address below and we will answer.
Children
Laik w alayk is only for people aged 18 or over — the Terms of Use say so. We do not knowingly collect information about anyone younger, and we close any such account we find.
Changes
If this policy changes, the date at the top of this page changes. The Terms of Use work differently: when they change, the app asks you to read and agree to the new version before you carry on.
Contact
Grand Block Technologies LLC, Dubai, United Arab Emirates
info@gbt.ae
Terms of Use · Privacy · Support · Delete your account · Sign in