Privacy

What happens to what you send

Looking around this site leaves almost no trace: no cookies, no analytics, no advertising. I learn who you are only when you write to me, and then I use what you send for one thing: to answer you.

Who is responsible

Nikita Shmyrev (Nick Brighter), based in Serbia. I work alone, so I am the only person who reads what you send. For any question or request about your data, write to hello@brighter.team or to me on Telegram: @nickflocka.

What I receive

• When you send the form: your name, your email and your project brief and, only if you add them, your company, the type of project, a target date, a budget range, a reference link and one file of up to 25 MB.
• When you write in the chat: your messages and, only if you add them, one file of up to 25 MB with a message and a contact for the reply: an email or a Telegram handle.
• Added to a form message or a chat by the server: the time, the page of this site you wrote from, and your IP address.
• When you only look around: like any web server, mine writes each request to a log: the IP address, the time, the address requested, the page that led there and how your browser identifies itself.

That is all. I build no profiles, send no mailings and sell nothing to anyone.

Why, and on what basis

I read your message to answer it and to work out an estimate and a schedule. You asked for exactly that, so the basis is the steps taken at your request before a possible contract. The IP address and the server log serve a legitimate interest: keeping spam and attacks out and finding faults. For the same reason the form and the chat ask my server for a one-time ticket before they send: a random value that says nothing about you and is not kept in your browser. When the same text arrives from several addresses, my server sets such messages aside until I have looked at them myself; no message is deleted because of what a machine makes of its content. By sending the form or writing in the chat you also agree to the handling described on this page, and you can take that agreement back at any time.

Where it goes

• My server. The message and the file, and the chat conversations with their files, are stored on a server I rent from a hosting company in Bulgaria, in the EU. The form and the chat are sent over an encrypted connection.
• My Telegram. A bot forwards a copy to my own Telegram account, so that I see it at once: everything you entered, the time, your IP address and the file. That makes Telegram a recipient too. From the chat the bot forwards each message with its file, the page you started from and the contact you left, without the IP address; when I answer from Telegram, my reply travels through Telegram as well. It is a messaging service run by a company outside the EU, and the copy sits on its servers under Telegram’s own privacy policy.
• Me, in Serbia. I read and answer from Serbia, which is outside the EU.
• Backups. The server makes a nightly backup that includes the form’s inbox and the chat conversations, and keeps the last fourteen. I also keep backup copies on my own computer.

Nobody else receives it. If a project needs another specialist, I ask you before passing anything on.

How long

I keep your message, from the form or the chat, while we talk and delete it, with its files and the copy in Telegram, once the conversation is over: at most a year after your last message. The backups follow: the server’s within two weeks, the copies on my computer within the same year. The server log is kept for about two weeks. To have your message deleted sooner, just ask. A chat conversation I delete also disappears from the chat in your browser.

Cookies and local storage

This site sets no cookies for visitors and runs no analytics or advertising code, so there is no cookie banner: there is nothing to accept. Everything a page needs, the typefaces, the scripts and the video included, comes from this site itself. Nothing is loaded from other companies’ servers.

Two things are remembered in your browser, each only after you do something yourself. When you turn the sound on or change the volume in the video player, the browser keeps that choice in its local storage, so the next video starts the same way. It stays on your device, is never sent to me, and goes when you clear this site’s data in your browser. A diagnostic link that I may send you when a video misbehaves keeps one switch in the same way, until you close that tab.

When you send a first message in the chat, the browser keeps a random key for that conversation in its local storage, with the number of the last reply you have seen. The key is what lets the same browser find the conversation again, so my reply reaches you after a reload or some days later; without it nobody can open the conversation. It is sent to my server with each chat request and to nobody else. To remove it, clear this site’s data in your browser: the chat then starts empty, as it does in any other browser or device, while the messages you sent stay with me until I delete them as described above.

Your rights

You can ask me what I hold about you and for a copy of it, have it corrected or deleted, object to my using it or ask me to pause that, and take back your agreement at any time. Write to @nickflocka on Telegram; I answer within a month. If you think I have handled your data wrongly, you can complain to the data-protection authority of the country you live in, or to Serbia’s Commissioner for Information of Public Importance and Personal Data Protection.

The rules I follow

I am based in Serbia, so Serbia’s Law on Personal Data Protection applies to my work; it is built on the same model as the EU’s GDPR. I handle inquiries from clients in Europe by the GDPR’s principles: collect only what is needed, use it only for the stated purpose, keep it no longer than needed and protect it while I have it.

Last updated · 10 October 2026