What this site collects and why.

Who is responsible

Areeb Siddiqui, based in Tallinn, Estonia, operates mareebs.com and is responsible for the personal information described here. Contact mohammadareebs@gmail.com with a privacy question, access request, correction, deletion request, or objection.

Owner and legal review is still required before launch to confirm the controller’s full legal identity and any postal contact details that must be published.

The technical second opinion form

The form collects your name, email, company or product, role, the technical problem, why it matters now, optional technical context, and an optional relevant link. It also carries limited acquisition information from the page URL, a future answer slug when present, and a referrer reduced to its origin and path.

This information is used to review and reply to the business or technical inquiry you asked Areeb to consider, secure the form against abuse, troubleshoot whether the notification was delivered, and derive generalized, anonymized lessons for independent public writing. The site does not fetch, preview, or enrich a link you submit.

The form sends one internal notification through Brevo’s transactional email API to Areeb’s configured inbox. The submission and reply thread remain in Brevo and the receiving email provider. No feature database, CRM record, automated answer, or automated acknowledgement email is created.

Reason for processing

The intended basis is Areeb’s legitimate interest in responding to requested business inquiries and protecting the form from abuse, and steps you request before a possible contract where that applies. Optional Brevo analytics runs only after you allow it through Analytics preferences.

This lawful-basis wording is a factual implementation draft, not legal advice. The owner or legal reviewer must confirm it before launch.

Services involved

• Cloudflare delivers the site, provides Web Analytics, and runs Turnstile verification. Cloudflare receives the network and browser information needed to provide those services.
• Brevo delivers the internal form notification. Its optional website tracker also measures aggregate page and CTA behaviour only after analytics permission is granted.
• The configured inbox provider holds the notification and reply thread. The provider must be confirmed in this notice before launch if the production inbox differs from the Gmail contact route currently published on the site.

These providers may process information in countries outside Estonia or the European Economic Area under their own terms and transfer arrangements. This notice does not promise a location or safeguard that has not been verified. Review the current Cloudflare privacy policy and Brevo privacy policy.

Analytics preferences

Cloudflare Web Analytics is currently loaded across the site. The separate Brevo tracker is disabled unless you choose Allow analytics. That preference is stored in your browser so the site can remember the choice. Brevo analytics may then record page views, article reads, and coarse CTA or second-opinion funnel events. Form text, name, email, company, internal reference, relevant link, and verification token are never sent as analytics event data.

You can reopen Analytics preferences from the footer and change the Brevo choice. Turning it off reloads the page so the optional tracker is no longer active.

How long inquiries are kept

• Declined or unanswered submissions are deleted within 90 days.
• Answered submissions are kept for up to 12 months to preserve the conversation, unless an active client or business relationship or a legal record requirement justifies longer retention.
• Written approval for attribution or identifiable detail is kept while the relevant public article remains published.

This cleanup is performed manually in the email inbox. The site does not claim automated deletion.

Requests stay private

The submission and reply are not published. Areeb may independently write about generalized, anonymized lessons from the patterns and decisions in requests without seeking approval for each article. Before publication, he removes names, companies, people, customers, system-specific architecture, metrics, links, and identifying or proprietary context. If safe generalization is not possible, the material is not published without permission.

Attribution or any detail that could reasonably identify the submitter, company, customers, or system requires separate affirmative written approval. That approval is retained while the relevant article is public, and material identifying changes require approval again.

Your choices

Share only information you are authorised to disclose. Do not send credentials, secrets, customer or employee data, or proprietary source code. Depending on the law that applies, you may have rights to access, correct, delete, restrict, or object to processing and to complain to a data-protection authority. Contact mohammadareebs@gmail.com to make a request.