Privacy information for the Boğa website and Facebook and Instagram client account integrations. Last updated: October 16, 2026.
Important: details pending confirmation
This page separates verified website details from information that has not yet been verified. Items marked [TO CONFIRM] are placeholders, not statements of established practice. The review covered accessible Framer project code and page configuration; backend systems, Meta app settings and account-level scripts were not available. This page should not be treated as a fully verified description of those systems.
1. Who we are and how to contact us
This page covers Boğa’s website and its use of Meta APIs for client account management, as confirmed by Boğa. Contact hadil@uxboga.com for privacy questions or deletion requests.
[TO CONFIRM: legal entity name, registered address, country, jurisdiction, and controller or processor roles.]
2. Personal data collected
The contact form requests your name, company, email address and message. The newsletter form requests an email address. Messages may contain additional personal data. Do not send passwords, access tokens or sensitive credentials.
[TO CONFIRM: submission destinations, recipients, other forms, device data, logs, cookies and analytics. Local form code supports optional URL-based prefilling and fetching a public HubSpot-hosted free-email-domain list; live use of these features is not verified.]
3. Facebook and Instagram integrations
Boğa confirms that it uses Meta APIs for client account management. Accessible local website code does not identify the Facebook or Instagram data accessed. Access to content, messages, comments, insights or advertising data must not be assumed.
[TO CONFIRM: Meta app name and ID, enabled products, exact permissions and scopes, data fields, account types, operations, purposes, recipients and client authorization process.]
Review permissions in Meta’s authorization flow before granting access. Review connected apps or business integrations in Facebook or Instagram settings to remove access. Revocation may stop future access but does not establish that previously retained data has been erased. Contact Boğa separately about deletion.
[TO CONFIRM: access or refresh token storage, provider, encryption, access controls, token lifetime, renewal, revocation and deletion. No Meta OAuth or token handling was found in accessible local code; this does not establish that none exists elsewhere.]
4. How data is used
Contact and newsletter interfaces are presented for inquiries and subscribing to updates. Boğa describes its Meta API use as client account management. These interfaces alone do not verify downstream uses, sharing, profiling or marketing automation.
[TO CONFIRM: actual purposes and legal grounds for each data category, marketing consent and withdrawal, sale or advertising-related sharing, profiling and automated decisions. No claim that these activities do or do not occur is made here.]
5. Storage, hosting and retention
The website is built in Framer and uses Framer-hosted assets. This does not identify every provider handling submissions or Meta data. Production infrastructure, data locations, transfers and retention periods were not verified. No persistent browser storage was found in local files reviewed; platform scripts and external module internals were outside the review.
[TO CONFIRM: production hosting and subprocessors; email, form and Meta-data storage providers and regions; transfer safeguards; retention periods or criteria for inquiries, subscriptions, Meta data, tokens, logs and backups; deletion schedules and legal exceptions.]
6. Security
No online service can guarantee absolute security. Accessible website files do not verify Boğa’s organizational or backend safeguards. Do not send confidential credentials with a privacy request.
[TO CONFIRM: implemented encryption, access restrictions, authentication, monitoring, incident response and vendor oversight. No certification or compliance guarantee is asserted.]
7. Third-party services and links
The project uses Framer resources and external modules. Article-sharing code constructs links to Facebook, LinkedIn and X (Twitter). Third-party services have their own privacy terms. A Facebook sharing link is not a Meta API authorization and does not establish that login permissions are requested.
[TO CONFIRM: active processors, embeds, cookies, analytics, advertising tags, scheduling and form-delivery services, including account-level custom scripts. An available component does not prove a service is active.]
8. Your privacy rights
Depending on applicable law and the processing involved, you may have rights to access, correct or delete data, restrict or object to processing, receive a portable copy, withdraw consent, or complain to a competent supervisory authority. Legal conditions and exceptions may apply. Contact hadil@uxboga.com to ask about your data or exercise a right.
[TO CONFIRM: applicable laws, supervisory authority, identity verification, request-handling procedures and deadlines. Not every listed right applies in every jurisdiction.]
9. Requesting data deletion
Email hadil@uxboga.com with the subject “Data deletion request”. Describe the information to be deleted and, if relevant, identify the connected Facebook Page or Instagram account and your relationship to it. Do not include passwords or access tokens. To stop a Meta connection, also review and remove the integration in Meta’s settings.
[TO CONFIRM: verification, acknowledgment and handling procedures; deletion from live systems, tokens, backups and providers; retention exceptions; completion times; and any Meta deletion callback or status URL. This email route does not verify an automated deletion process or promise immediate erasure.]
10. Updates and privacy contact
The date at the top identifies this page’s latest revision. Confirmed legal and operational details should replace placeholders as they become available. For questions about this notice or your personal data, contact Boğa at the email below.