Privacy

Version 1.0 · In force from 27 August 2026

This notice describes what Mixify collects about you, why, who else sees it, and what you can make us do about it. It is written to be read rather than to be defensible, so where something is a genuine choice we have made, it says so.

Who we are

Mixify is operated by Red Swift Systems Ltd, registered in England and Wales under company number 14891467, with its registered office at 2nd Floor College House, 17 King Edwards Road, Ruislip, London HA4 7AE, United Kingdom. We are the data controller for everything described here. Privacy questions go to privacy@redswift.systems; anything else to mixify@mixify.bar.

What we collect

Your account

Your email address, the name you give us, your username, display name, and optionally a short bio and an avatar. Your country, as a two-letter code, because the rules that apply to alcohol and to your data differ by market and we would rather ask than guess. Your role — whether you are here as a drinker, a bartender, or a brand — and whether you have been verified as working in the trade.

If you sign in with Apple or Google

We receive your email address and your name from them, and nothing else. We do not receive your password, your contacts, or anything about your use of their services. If you use Sign in with Apple and choose Hide My Email, Apple gives us a relay address instead of your real one; mail we send reaches you through Apple, and we never learn the address behind it.

What you do here

The drinks you log, the lists you build, the people you follow, and the recipes, revisions, ratings, likes, comments and venue reviews you create. Most of that is the point of having an account — it is what makes a profile yours rather than a browsing session.

Age and professional checks

Where we must confirm you are old enough, we store a record that a check happened — the method, the age threshold you cleared, and when. We do not store your date of birth. The question anyone will ever ask is “was this person old enough in this market”, and a date of birth is more personal data than that question needs.

The same applies to professional verification: we keep how the claim was checked, by whom, and when — and a reference to the evidence. We do not keep your employment paperwork.

Consents and requests

What you agreed to, which version of which notice was in front of you when you agreed, and whether you have since withdrawn it. Withdrawing does not delete the record — it timestamps it, because the history is what makes the consent meaningful.

Technical records

Our servers log requests, which includes IP addresses, in the ordinary way needed to run and secure a service. Email delivery is logged with the address partially redacted — enough to answer “did we try to write to this person”, not enough to rebuild a mailing list.

What we do not do

  • No advertising or analytics trackers. There is no Google Analytics, no advertising pixel, no session recorder, and no third-party script watching what you look at. The leaderboards are computed by us, from your activity here.
  • We do not sell your data, or share it with data brokers, or use it to build a profile for anyone else’s advertising.
  • We do not ask for a date of birth or store identity documents.

Why we are allowed to hold it

Running your accountPerformance of our contract with you.
Keeping the service working and secureOur legitimate interests in operating a service that is not being abused.
Age assurance and trade verificationLegal obligation, and our legitimate interest in attributing recipes honestly.
Anything optionalYour consent, recorded against the wording you were shown, and withdrawable at any time.

Who else touches it

We keep the list of suppliers deliberately short. Each of these processes data on our instructions:

RailwayHosting and the database. Our servers and data run in the European Union.
CloudflareDNS, and serving of our administration console.
ZohoSending email — verification links, password resets. European infrastructure.
Apple, GoogleOnly if you choose to sign in with them, and only for that.
Google FontsOur pages load typefaces from Google’s servers, which means your browser tells Google your IP address when a page loads, before you have done anything. We would rather this were not the case and intend to serve those files ourselves.

Where a supplier processes data outside the UK or EEA, that transfer relies on the standard contractual clauses or an adequacy decision.

How long we keep it

Your account data for as long as you have an account, and then only what we must. Recipes and contributions you have published are attribution records — deleting your account does not silently rewrite who invented a drink, and we will tell you what remains and why if you ask.

Records of a data request — what was asked, when, and when it was answered — outlive the account they concerned. Deleting the proof along with the data turns a compliant erasure into an unprovable one.

What you can make us do

You can ask us for a copy of your data, to correct it, to delete it, to give it to you in a portable form, or to stop a particular use of it. Write to privacy@redswift.systems and we will log the request with a due date and answer within the period the law allows — one month in the UK and EU, and sooner if we can. That mailbox covers every product Red Swift Systems Ltd operates, so you do not have to work out which one held your data.

If you are unhappy with how we have handled it, you can complain to your data protection supervisory authority. In the UK that is the Information Commissioner’s Office.

Age

Mixify is about alcoholic drinks. You must be at least 18 to hold an account, or older where your market requires it. Browsing without an account is possible; logging a drink is not.

When this changes

Each version of this notice has a number and a date, both at the top of this page, and we keep a record of which version you were shown. When we change something material we will tell you rather than quietly republishing.