Privacy notice

Last updated 3 October 2026

Fintech Global Hub is a shared calendar of fintech and startup events, where people can also plan events in the open and join group trips. This page says what we keep about you, why, who else sees it, and how to take control of it. We have tried to say it plainly.

Who we are

The hub is run by [Name and address of the organisation that runs the hub: to be confirmed]. Fintech Global Hub is a product of SUPER HOW?.

For anything on this page, write to [Privacy contact address: to be confirmed].

If you only look around

You can read the calendar without an account. We do not ask who you are, and nothing about your visit is counted unless you tell us it may be (see "Counting visits" below).

Like every website, the hub is delivered through a hosting company, Cloudflare, which sees the internet address your request comes from and uses it to deliver the page and keep the site safe. Our own logs keep the page that was asked for without its query string, the time, the result and a request number. They do not keep your address, your cookies or anything you typed.

We store a few small items in your browser to make the site work: your time zone, your light or dark choice, and your answer about counting visits. The cookie list names each one.

If you join

You join by an email link or by signing in with LinkedIn, Google or Microsoft. We receive what you give us or what that service shares when you agree to it, which is your name, your verified email address and your photo. We do not receive your password for any of them, and we never ask for one.

Then we keep:

your name, display name, email address and photo;
your home city, time zone and language;
the topics you follow;
your role in the hub, and the organisations you act for;
a link to your LinkedIn profile, where one has been given, so that curators can check a request to add events;
your answer about counting visits, and when you gave it;
which sign-in services you have used, and a record that a sign-in exists. We do not keep the address or the browser it came from.

We use this to run your account, show you events that suit you, send you what you asked for, and keep the calendar trustworthy.

What you do in the hub

When you use the hub, we keep what is needed for it to work:

events and trips you add, and their history of changes;
the events you say you are interested in or going to, and the organisations you follow;
offers you send to help with an event, and your note with them;
requests for a seat on a trip, with the number of people, your company stage and your note;
reports you make about a listing, with your reason and note;
requests to add events for an organisation;
if you act for an organisation, or are a curator, the contact email and phone you enter for its page, which of them you set, and the website and social links you add, which are public;
your notification settings, the notes in your hub, and your calendar links;
the weeks in which you used the hub: one entry for you and the week, nothing about what you did. We count these ourselves to know whether the hub is useful, and this does not depend on your answer about counting visits.

Who sees it: an organisation's contact email and phone are shown to signed-in members of the hub, and never to a visitor, so that addresses are not collected from public pages. Its website and social links are public. Organisers see how many people from each organisation are going, never your name. The same goes for following an organisation: its page shows how many members follow it, and who they are is never shown to anyone. You see your own follows on the organisation pages and in your download. We use them to tell you, in the hub and by email if you switch that on, when an organisation you follow adds an event. Your contact details go to an organiser or a trip lead only after an offer or a seat request of yours is accepted. Curators, who look after the quality of the calendar, can see names when they review listings, reports and requests, and what they decide is kept in a record of their actions.

Email

We send sign-in links, notices about security, and the notifications you have switched on in Settings. Every notification email has a link to turn that kind off. Sign-in links and security notices are always sent, because without them you could not get in or be told about a risk. Emails carry no tracking pixel and no tracking in their links, so we do not know whether you opened one.

Counting visits

If you say yes in the card that asks, we count how the hub is used so that we can improve it. Until you say yes, and for ever if you say no, no counting tool is loaded and nothing is stored for it. You can change your mind at any time in Settings (Privacy) or in Cookie settings at the foot of every page. Saying no changes nothing else about the hub.

We use PostHog, on its servers in the European Union. It is set so that it does not follow clicks, scrolling or typing, does not record your screen, does not store your internet address and does not build a profile of you. It records only these events, each with at most the detail shown:

that you looked at the Day, Month, Pipeline or Trips view;
that you opened an event, and whether it was an idea, a plan or confirmed;
that you changed your time zone, or filtered by a topic;
that you said you were interested or going, and the stage of the event;
that you sent an offer, and its kind (venue, speakers, co-host or sponsor), or answered one (accepted or declined);
that you added an event, and its stage, or confirmed a date, and whether the date clashed;
that a clash was shown to you, how strong it was, and where;
that you asked for a trip seat, made a calendar link, or pressed Join.

Nothing you type is sent: no names, emails, titles or notes. Each browser gets a random number to tell its visits apart; it is deleted when you say no. We do not link it to your account.

Finding and fixing faults

When something breaks, a short report goes to Sentry, on its servers in the European Union, so that we can fix it. It holds the kind of error, which part of our code failed, the version of the hub and the page without its query string. It never holds what you typed, your cookies, your sign-in, your internet address or your email address, and we strip these out before it is sent. Our logs on Cloudflare are the same: a request number, the page without its query string, the time and the result. This is how we run the service safely, and it does not depend on your answer about counting visits.

[How long logs and error reports are kept: to be confirmed]

Your choices and rights

See and take a copy of what we hold: Settings, Account, Download your data.
Correct it: Settings, Profile.
Delete your account: Settings, Account, Delete your account. You are signed out at once and your name, email address, photo and profile are removed, and so are the contact email and phone you entered for an organisation. What other people rely on stays without your name: the events you added and their history stay with their organisation, decisions a curator made stay in the record of their actions, and offers and seat requests stay for the organisers they were sent to, without your words.
Stop counting visits: Settings, Privacy, or Cookie settings at the foot of any page.
Stop notifications: Settings, Notifications, or the link in the email.

You may also ask us to restrict or stop using your data, or complain to a data protection authority: [Supervisory authority: to be confirmed]. Write to [Privacy contact address: to be confirmed] and we will answer.

How long we keep it

Your account and what you did in it: until you delete your account.
A sign-in link: 10 minutes. A sign-in on one browser: up to 30 days, and it is removed when you sign out or delete your account.
An invitation: 14 days.
The action you were about to take when you were asked to sign in, kept in your browser: 30 minutes.
Your time zone, last sign-in method and answer about counting visits, in your browser: the lengths on the cookie list.

Changes to this page

If what we do changes in a way that matters to you, we change this page first and say so in the hub. The date at the top is the date of the last change.

Cookies and similar storage