Who we are
MGLO Software is run by BR PFA, registered in Romania with CUI 51858069 and Trade Register number F2025018669009, at Str. Cetății nr. 3A, cam. 1, birou 1, sc. 2, parter, ap. 27, sat Florești, comuna Florești, jud. Cluj, România. We decide what happens to the information described here and are responsible for it.
For anything about your data, write to contact@mglo-software.com. We answer within one month.
What you send us
When you send a brief, a message from the contact page, a call request or an application, we keep what you wrote and the details you gave: your name, email and company. A brief also keeps your phone number, your answers about the project and the time you chose for a call; an application keeps the links to your work, your note and the firm you would join through.
Each one reaches the team by email and in our internal tools, where we note what we answered and what comes next. From a brief's answers we estimate how closely the project matches our work, to decide where to start, and a brief completed within seconds is set aside as likely automated. A person always decides what follows.
We use what you send to answer you and to prepare the work you asked about; an application, only to consider you for work with MGLO. Until you send it, a brief waits in your browser tab and nowhere else.
If you fill in the form in one of our ads on Facebook or Instagram, Meta collects it for us: the name, email and phone number it fills in from your profile (you can change them before sending) and your three answers. We read them in Meta's tools, call or write to you about them, and see which ad brought you. If you write to us in Messenger, the conversation stays there, under Meta's privacy policy.
Conversations with Ask MGLO
The assistant's answers are written by an AI model from OpenAI, working from the site's own documentation. Each time you write, your message, the page you are on and your time zone go to OpenAI to write the answer. Under OpenAI's terms for business use, it does not train its models on them.
We keep the conversation so the team can follow up and improve the answers. If you are signed in, you can reopen your earlier conversations from the chat and carry on with them; the assistant also sees your name and can look back over them. For a client, it reads your projects as your client space shows them, including the names and replies of the people on them, and what it reads reaches OpenAI with your messages. The team uses the assistant too, to look through recent requests and conversations.
If you call MGLO from the chat, your voice goes to OpenAI so its model can hear you and answer aloud. We keep the call’s transcript in the same conversation, with its length; we don’t record the audio. If you are signed in, the call reads what the chat reads for you.
If you book a call in the conversation, we keep your name, your email or phone number, your company if you give it, the time you chose and a short summary of what you want to discuss. Please don't share passwords, payment details or health information in the chat.
At your request, the assistant can save your question in a project thread. For the team, it can read assigned work and shared notes, give a brief when asked and save a note with its author and channel.
Your account and the client space
You can sign in with your email, a code sent to your phone, or Google. Your account keeps your email or phone number and your name. Twilio sends the phone codes; if you choose Google, Google gives us your name and email.
Once work begins, the team connects your account to your company's projects. What you write there (comments, review answers, support requests and feedback) stays with the project. Our team and the people from your company on the project can read it, and they see each other's names. Messages sent from the Client space also reach the team by email; questions sent through the assistant appear in the project thread.
You can link a verified phone number to your account and unlink it at any time. Team members can link a trusted number. When WhatsApp messaging is enabled, Meta and Twilio deliver the messages and your number to us; the assistant uses the same account permissions as on the site. Linking a number does not subscribe you to updates.
MGLO's news
Only if you ask for it, from your account or with the box on the brief or the contact form, which we never tick for you. We keep your email, name and language to send it. Every email ends with a link that takes you off the list at once; after that we keep only your address, marked as gone, so nothing reaches it again.
Measurement and advertising, only with your yes
Measurement stays off until you allow it in the cookie card. With your yes, we record the pages you read, how far a brief gets and where conversations and requests begin, under a random ID your browser keeps. If you then send us something or talk to the assistant, the same ID links it to that visit, and a brief also notes the page where the visit began and the site or campaign that brought you.
We record the choice you make in the card, whichever it is, with the same random ID, so we can show what you agreed to. The card asks again after 13 months, and Cookie settings at the foot of every page changes your choice at any time.
Marketing stays off until you allow it, separately from measurement. With your yes, Meta's pixel loads with its cookies (_fbp, and _fbc when you arrive from one of our ads) and tells Meta which pages you read here and whether you start or send a brief, book a call, send a message or create an account. Our server reports the same events to Meta with your IP address and browser and, when you send a brief, a message or a call request, your email, phone and name in a hashed form Meta can match but not read. Meta uses this to measure our ads and choose who sees them, under its own privacy policy. Careers pages and applications never reach Meta. Turning marketing off in Cookie settings stops the pixel and removes its cookies.
What your browser keeps
Only what the site needs to work, and the choices you make.
| Name | What it holds | How long |
|---|---|---|
| studio-consent | Your cookie choice and its random ID | 13 months, then the card asks again |
| studio-theme, studio-appearance, studio-sound | Your hue, day or night, and sound | Until you change or clear them |
| NEXT_LOCALE | A cookie with the language you chose, when it differs from your browser's | Until you close the browser |
| sb-…-auth-token | The cookies that keep you signed in | Until you sign out, at most 400 days |
| studio-chat, studio-chat-rate, studio-brief | Your conversation, how many answers you've had this hour, and a brief you haven't sent | Until you close the tab |
| _fbp, _fbc | Meta's cookies, after a yes to marketing | 90 days |
Who helps us run it
A few companies handle data for us, each only on our instructions:
- Google Cloud runs the site and the assistant, in Warsaw.
- Supabase keeps our database and accounts, in Ireland.
- OpenAI writes the assistant’s answers and speaks them in a call.
- Resend sends the team's notification emails and MGLO's news.
- Twilio sends sign-in codes to your phone and, with Meta, delivers WhatsApp messages when that channel is enabled.
- Zoho hosts our company email.
- Meta collects the form in our Facebook and Instagram ads and keeps its answers for us.
Some of them are based outside the European Economic Area, in the United States among others; those transfers rely on the European Commission's standard contractual clauses or the EU–US Data Privacy Framework.
Our servers and these providers keep technical logs, with the IP address and browser of each request, to keep the service running and safe. We sell no data, and we share it with no one else unless the law requires it.
Links to LinkedIn, GitHub, YouTube and the projects we show lead to services with their own privacy practices. A film hosted on YouTube loads only when you press play.
On what grounds
We handle your requests, applications, account and projects because you asked us to, as steps toward working together or under our agreement. Measurement, marketing and the news rest on your yes. The conversation records, the spam check and the technical logs rest on our legitimate interest in answering well and keeping the service safe.
How long we keep it
- Briefs, messages and call requests that don't become a project: two years after our last exchange.
- The form in our ads: 90 days, in Meta's tools. If our conversation goes on, we keep it as a request, as above.
- Applications: one year after our last exchange.
- Conversations with the assistant: one year after the last message.
- Measurement and your cookie choice: 13 months.
- Your account: until you ask us to close it. What you wrote on a project stays with the project for as long as the work with your company needs it.
- The news: until you leave the list.
- Technical logs: up to 30 days.
- Phone bindings: until you unlink the number or close the account. WhatsApp delivery records older than one day are deleted at the next nightly cleanup. Transcripts and their phone-number association follow the one-year period above. Internal notes stay until the team removes them; closing the author’s account removes its attribution, not names written inside the note.
What has outlived its period is deleted automatically, every night.
Your rights
You can ask us for a copy of what we hold about you, and ask us to correct it, delete it, limit how we use it, or hand it to you in a format another service can read. You can object to how we use it, and take back any yes you gave at any time, without affecting what happened before.
Write to contact@mglo-software.com from the address you used with us; we answer within one month. If you think we have handled your data wrongly, you can complain to Romania's data protection authority, ANSPDCP (dataprotection.ro), or to the authority where you live.
When this page changes
The date above the contents changes with it. If a change affects what you have already given us, we tell you by email.