Digital nomads watching a visa clock
Day limits are rarely simple: rolling windows, multiple entries, a border hop that reset something or maybe did not. Know where you stand before you book the next flight, not after.
Travel duration tracking
Know exactly how many days
you spent in every country
Bedu reconstructs your travel history from your Google account, works out where you spent each night, and turns it into a day-by-day record you can trust and export.
- Read-only Google access
- No generative AI, no trackers
- Every number traceable
- Days abroad
- 132
- Countries
- 5
- Trips
- 5
- Avg. trip
- 26.4d
The midnight spreadsheet
Your travel history already exists. It is just scattered like a nomad's trail across a decade of confirmation emails and a memory that gets vague past about eighteen months ago.
That is fine right up to the moment it is not. A residency application asks for five years of presence. A visa has a day limit you would rather not discover you crossed. A tax question turns on where you slept in February.
Suddenly you are cross-referencing flight confirmations against hotel bookings at midnight, trying to remember whether that trip ended on the Sunday or the Monday.
Bedu — short for Bedouin, the desert-crossing peoples who always knew exactly where they had been — is for the moment before that: the record is already assembled, already counted, already correct.
Who it is for
How many days were you actually there?
Every one of these is someone being asked to prove a number.
Permanent residency applicants
Most routes ask you to prove continuous presence over years and declare every absence with dates. Bedu already has the timeline, assembled from the bookings you made at the time.
Citizenship applicants
Naturalisation asks for the longest look back of all, sometimes a decade, with absence limits per year and in total. An archaeology project becomes a table you can review.
Anyone with a tax question about days
Bedu will not tell you where you are tax resident, that is your accountant's job. It will give them the precise per-day record instead of your best recollection.
Expats and cross-border workers
Live in one country, work in another, visit a third, and "where were you" stops being simple. Bedu keeps the split visible across the whole year.
Frequent business travellers
Employers, immigration teams and payroll increasingly need to know which days you worked in which country. A defensible record without keeping a manual log.
Anyone asked to account for recent travel
The pandemic made this universal for a while. The specific rules pass, the pattern does not: border forms, insurance claims, medical intake and employer declarations all ask where you have been.
Family and partner visa applicants
Relationship-based applications often need evidence of time spent together or apart, in specific places, on specific dates. Bedu is a source you can point at.
Travellers who just want to watch the map fill in
Not every reason is bureaucratic. There is real pleasure in watching your footprint grow: countries visited, days on the road, how much of the world you have actually stood in versus the version in your head. Bedu keeps score, year by year and across your whole travel history.
How it works
Your travel history in three steps
-
01
Connect your Google account
Bedu reads the travel confirmations Google already recognises: flights, hotels, trains and bookings. Access is read-only, and Bedu never writes anything back to your calendar or inbox. Optionally switch on direct airline scanning to catch the flights that never made it into your calendar.
-
02
Bedu builds your timeline
Each booking becomes a travel event with a date and a country. Bedu groups those events into trips, then works out where you slept every single night from your first trip to today. Set your home country and everything is measured against it.
-
03
Review, adjust, export
Nothing is locked. Correct a country, move a date, ignore a cancelled booking, or set a specific day by hand. Your edits are preserved the next time Bedu recalculates. When the record looks right, export it as a report.
The core rule
One country per day. Always.
Every calendar day is attributed to exactly one country, based on where you spent the night. Accommodation takes precedence. Flights resolve to where you landed. Quiet days between bookings are filled in sensibly. The day you travel home counts as home, because that is where you slept.
No double counting when trips overlap. No gaps where a booking is missing. The reasoning stays visible on the calendar, so you can always see which booking put you where.
Abroad
Booking
What you get
A record built for the questions people actually ask
A dashboard that answers the obvious questions
Countries visited, total trips, days abroad and average trip length, for any year you pick, with a comparison against the year before.
A world map of where you have been
Your footprint on a zoomable map with your home country marked and day counts on hover, next to a ranked breakdown of days per country as a percentage of the year.
A calendar you can actually read
Trips drawn as bars across the days they cover. Click any day to see its country and the bookings behind it. Click a trip for its full duration and per-country day counts.
Exportable reports
Take the record out of the app when a form, an accountant or a case officer needs it.
Day-threshold alerts Soon
Set a limit for a country and get warned as you approach it, so a visa window is something you manage rather than something you discover.
Full manual control
Add trips and events by hand for the journeys no email ever covered. Override any single day. Filter by type, country or trip to find what needs attention.
Why Bedu
Deterministic, not guesswork
Bedu uses no generative AI to work out your travel history. Every trip, every day, every count comes from explicit rules and formulas: parse the booking, resolve the country, group the trips, attribute the nights.
There is no model deciding what probably happened, and no answer that quietly changes between runs. When a number matters enough to put on a government form, it should be reproducible.
The whole pipeline
- 01Parse the booking
- 02Resolve the country
- 03Group the trips
- 04Attribute the nights
same input
same output
every run, every time
Your data
A record of everywhere you have been is not a small thing to hand over
So here is exactly what Bedu asks for, and what it deliberately does not.
Read-only, and nothing else
Bedu can read. It cannot write. It never adds, edits or deletes anything in your calendar, never sends email on your behalf, and never posts anywhere.
You choose how much to connect
Reading airline confirmations is optional, off by default, and switched on one airline at a time. Turn on two and Bedu looks at mail from those two senders, nothing else.
We keep the itinerary, not the correspondence
Bedu takes the route, the date and the booking reference, then discards the message. Your emails are not copied into Bedu and not searchable from inside it.
Nothing is sent to an AI service
Because Bedu uses no generative AI, your history is never sent to a model provider and never used to train anything. That is structural, not a policy that could quietly change.
No trackers, no ad networks, no data sales
Bedu is funded by subscriptions. Your locations are not a product, and there is no data-broker business hiding behind the free tier.
You can withdraw at any time
Revoke Bedu's access from your Google account settings whenever you like. Your record belongs to your account, protected by per-user rules at the database level.
Good to know
- Google accounts only, for now
- Automatic import works with Google Calendar and Gmail. On a different provider you can still use Bedu by adding trips by hand, and broader support is something we are looking at.
- Bedu counts days, it does not give advice
- It tells you precisely how many days you spent where. It does not decide your visa eligibility, tax residency or immigration status. Bring the numbers to whoever advises you.
- It works from your bookings
- Anything missing, a coach trip booked at a counter, a car crossing, a stay with friends, you can add in seconds and it is treated exactly like an imported event.
FAQ
The questions people ask first
Does Bedu read all my email?
No. Calendar import only looks at the travel bookings Google itself has already identified. Optional airline scanning looks only at confirmation emails from the specific airlines you switch on, one sender at a time. Nothing else in your mailbox is touched, and access is read-only throughout.
What does Bedu actually store?
The travel events it derives, and the trips and daily country attributions built from them: dates, locations, countries, and the booking details that appear in a confirmation. Airline emails are read, parsed and discarded rather than kept.
Can I use Bedu without connecting my email at all?
Yes. Calendar and airline import are conveniences, not requirements. You can add trips and travel events by hand and everything else works identically.
Do you use AI to figure out my trips?
No. Trip detection and day counting are done with fixed rules and calculations, not a language model. Your travel history is never sent to an AI provider and never used as training data. That is deliberate: it makes results consistent, repeatable and explainable.
What if Bedu gets something wrong?
Fix it. Change the country on an event, adjust a trip's dates, override a single day, ignore an event that never happened, or add a trip from scratch. Your corrections survive future imports and recalculations.
How far back does it go?
As far back as your Google account does. Bedu imports your full history up to today in seconds, not just recent months.
How does Bedu decide which country a day belongs to?
By where you spent the night. Accommodation wins if there is any. Otherwise the last event of the day decides where you ended up, and the day you travel home counts as home. One day, one country, no overlaps.
Can I disconnect later?
Any time, from your Google account settings. Bedu loses the ability to import anything new; the history you have already reviewed stays in your account.
Ready when you are
Start with the years you have already travelled
Connect your Google account and Bedu will reconstruct your travel history from your existing bookings. Review what it found, correct anything that looks off, and have a day-by-day record ready for the next time someone asks.
Read-only access · No generative AI · Your record, your corrections