Parkersoftware engineering Message Ben on Telegram

Privacy policy

What data reaches Parker through this website, why we use it and how you can control it.

Last updated:

In short

  • The brief form doesn’t send anything to our servers. Your brief reaches Ben only when you press Send in Telegram.
  • We use Meta Pixel and the Conversions API to measure our ads. We don’t send the content of your brief to Meta.
  • We don’t sell personal data. You can ask us to show, correct or delete yours at any time.

Who we are

This website belongs to Parker [legal entity], company no. [placeholder], registered address [placeholder] (“Parker,” “we” or “us”). We are the controller of the personal data described in this policy.

For any question about privacy, email hello@parker.example.

What data we collect

  • Your brief. The brief form on this site doesn’t send data to us. When you press “Send brief via Telegram,” your browser opens a chat with Ben in Telegram with your answers already typed in: name, job title, company, work email or phone, the project description and the budget, timing and engagement options you chose. We receive the brief only if you press Send in Telegram. Along with it, Telegram shows us your profile name, username and anything else your Telegram privacy settings make visible.
  • Messages and emails. When you message Ben on Telegram or email us, we receive what you write and your contact details.
  • Technical data. When you open a page or click a link to Telegram, we collect your IP address, your browser’s user agent, the page address, the time of the event and identifiers from Meta cookies. If you arrive from a Meta ad, this includes the ad click ID.

We don’t ask for special categories of data, such as health or political views. Please don’t include them in your brief.

Cookies, Meta Pixel and Conversions API

We use Meta Pixel, a tool from Meta, to measure how our ads on Facebook and Instagram perform. It works in two parts.

  • In your browser. Meta Pixel loads a script from Meta and sets two cookies: _fbp, which recognizes repeat visits from the same browser, and _fbc, which stores the ad click ID when you arrive from a Meta ad. While you move between our pages, we keep that click ID in your browser’s session storage. It’s cleared when you close the tab.
  • From our server. Through the Meta Conversions API, a server sends Meta a copy of the same events: the event name, the page address, your IP address, your browser’s user agent and the values of the _fbp and _fbc cookies. Both copies share one event ID, so Meta counts each event once.

We measure three events: a page view when you open a page, a contact event when you click a link to Telegram, and a lead event when you send your brief to Telegram. We don’t send Meta the content of your brief or your messages.

Meta Pixel and the server copy start only after you press Accept in the cookie banner. If you press Decline, or don’t choose, nothing is sent to Meta. Your choice is saved in your browser.

Meta processes this data under its own privacy policy. To limit it, block or delete cookies in your browser settings, or change your ad preferences in your Meta account. The site works the same without these cookies.

Why we use your data and on what legal basis

PurposeDataLegal basis under the GDPR
Reply to your brief, prepare an estimate and discuss a projectYour brief, messages and contact detailsSteps you ask us to take before a contract (Art. 6(1)(b)) and our legitimate interest in answering business inquiries (Art. 6(1)(f))
Measure our ads with Meta Pixel and the Conversions APITechnical data and Meta cookiesYour consent (Art. 6(1)(a)), given in the cookie banner
Keep the site and our communication secure, and meet legal obligationsTechnical data and correspondenceOur legitimate interest (Art. 6(1)(f)) and legal obligations (Art. 6(1)(c))

Where we rely on consent, you can withdraw it at any time. This doesn’t affect anything we did before you withdrew it.

How long we keep data

  • Briefs and correspondence. While we discuss a project with you and for up to 24 months after our last contact. If we sign a contract, for its term and as long afterwards as the law requires.
  • Meta cookies. _fbp and _fbc expire after 90 days unless you delete them sooner.
  • Analytics events. Our server passes events on to Meta and keeps technical logs for up to 30 days. Meta keeps event data under its own policy.

Who we share data with

  • Meta. Meta Platforms Ireland Limited receives the analytics events described above.
  • Telegram. Your brief and messages travel through Telegram, which processes them under its own privacy policy.
  • Service providers. Companies that host our website and email, and the server that relays analytics events. They process data only on our instructions.

We don’t sell personal data, and we don’t share it with anyone else unless the law requires it.

Some of these providers process data outside the European Economic Area. When they do, the transfer is protected by safeguards such as the EU Standard Contractual Clauses or the EU-US Data Privacy Framework.

Your rights

Under the GDPR you can:

  • Access the personal data we hold about you and get a copy.
  • Correct data that is inaccurate or incomplete.
  • Delete your data.
  • Restrict how we use it, or get it in a portable format.
  • Object to processing based on our legitimate interest, including ad measurement.
  • Withdraw consent at any time.

How to exercise them

Email hello@parker.example with the subject “Privacy request” and tell us what you’d like us to do, or message Ben on Telegram. It’s free. We reply within one month and may ask you to confirm your identity first.

If you think we handle your data unlawfully, you can complain to the data protection authority in the country where you live or work. We’d appreciate the chance to put it right first.

Changes to this policy

We update this policy when our website or the way we handle data changes. The date at the top shows the latest version. If a change is significant, we’ll point it out at the top of this page.