Web portal
FlirtBloom
A dating platform built from scratch for two markets: Germany and Italy. Profiles with distance search, chat, tokens and subscriptions, selfie verification, moderation with warnings and full GDPR handling - in four languages.
flirtbloom.de- Client
- Projekt własny
- Industry
- Portal randkowy, rynek niemiecki i włoski
- Year
- 2026
- Scope
- Platform · Token payments · Chat · Verification and moderation · GDPR · SEO · DE and IT markets
- 2 markets
- Germany and Italy, in four languages
- 19 sections
- in the data copy issued on request
- 3 variants
- of every photo, including a blurred preview
01/
The challenge
A dating platform is not a profile directory. Four things have to be solved at once, and each of them can sink the project on its own: money (who pays for what, and how not to short-change anyone), photos (paid content that must not leak before payment), safety (fake accounts and harassment) and the law. The service launches into two markets at once, Germany and Italy, which doubles the copy work: the same screens have to read naturally in both languages rather than like a translation. Germany adds its own requirements on top - Impressum, Datenschutz, AGB, youth protection and the right of withdrawal are not decorations but the price of entry. On top of that the site has to make sense to someone arriving from a search engine with two minutes of patience.
02/
The solution
I built the whole service from scratch, with no off-the-shelf engine. Money moves in tokens, and every operation runs inside a database transaction, so a balance cannot drift. Above the tokens sit two subscriptions. A free account replies without limits but cannot start new conversations - the simplest way to keep the site from turning into spam. VIP gets daily allowances, PLATINUM removes them and takes priority in the recipient's inbox. Photos are processed into three variants: full size, thumbnail and a blurred 64-pixel preview. A paid photo in chat shows as that blurred version, and the original never leaves the server until the recipient pays - the tokens then go straight to the sender. Safety rests on two pillars. Verification uses a selfie with a code derived deterministically from the account id, so it cannot be substituted and does not change between visits; the photo is stored as a private file visible only to its owner and to moderators. The second pillar is moderation with a history: three warnings mean an automatic account block and the end of every session, and each moderator action reaches the user as a notification they must acknowledge. I treated GDPR as a product feature rather than a paragraph in the terms. A copy of your data is one button and a file with nineteen sections. Accounts dormant for two years are anonymised and deleted a month later along with their files. A profile reaches search engines only if its owner opts in - by default it stays closed.
03/
The outcome
The service runs on its own server behind Cloudflare and covers both target markets, German and Italian, alongside Polish and English - four complete language versions in all, panel and moderation included. The sitemap is built from the database and picks up new content by itself, but only profiles that agreed to be visible. User files live outside the deployment directory, so a new release never touches them, and reaching the server while bypassing Cloudflare is simply closed off.
Tech stack
- Next.js
- React
- TypeScript
- Prisma
- MySQL
- Tailwind CSS
- sharp
- Cloudflare
Have a similar project? Let's talk.
Describe briefly what you want to achieve. You get a quote and a proposed scope back, usually within a day.
Get a quote
