bekarabekara

Legal

Privacy Policy

1. Controller

bekara · Karl Fiegle · 6370 Stans, Switzerland
Email: hallo [at] bekara [dot] tech

Personal data is processed in accordance with the Swiss Federal Act on Data Protection (FADP). Where applicable, the EU General Data Protection Regulation (GDPR) is also observed.

2. No cookies, no tracking on this website

This website is static. It sets no cookies, uses no analytics or tracking services and loads no content from third-party servers. Fonts are served locally.

3. Hosting and server logs

The website runs on Google Cloud (Cloud Run, Zurich region, Switzerland). When you open the website, the infrastructure processes connection data for technical reasons (IP address, time, page requested, user agent) in server logs. This data is used only to keep the service secure and stable and is not combined with other data.

4. Contact form

If you send a request through the contact form, the data you enter (name, email address, topic, message) is transmitted and stored in an internal system hosted in Switzerland. It is used only to handle your request and the related correspondence and is not passed on to third parties.

To prevent automated spam, the form uses a self-hosted ALTCHA check. Your browser solves a short computational challenge, which the server verifies once. No cookies are set and no data is sent to a third-party CAPTCHA provider. Short-lived proofs and request limits derived from an IP address, stored without the plain IP address, are valid for at most ten minutes and are deleted on the next form request after expiry.

5. Email

Business emails (for example quotes and invoices) are sent through Resend (Resend Inc., USA) as a processor. The data needed for sending (recipient address, content) is processed for this purpose.

6. Bekara Connect: what it is

Bekara Connect (connect.bekara.tech) is the page where my clients connect their advertising and shop accounts to my reporting. The client signs in with their own account at the platform and grants access themselves. I never receive a password.

Supported platforms, depending on what is enabled for a client: Meta, Google Ads, TikTok, Pinterest, Snapchat, Klaviyo, Shopify and HYROS.

For the data from my clients' accounts I act on behalf of the respective client (as a processor). The client remains the controller of this data.

7. Bekara Connect: data I process

When connecting

  • Invitation link: I store only a hash of the link, not the link itself. It is valid once and for 7 days at most.
  • Session cookie: Connect sets one strictly necessary cookie so that you stay signed in while connecting. It is valid for 24 hours at most. There is no tracking and there are no analytics services.
  • Connection details: platform, ID and name of the accounts you approved, connection status and time of the last check. For Google, also the email address and ID of the Google account used to connect, so that it is clear which account the access runs through.
  • Audit log: time, platform and type of action (connected, accounts selected, disconnected).
  • Server logs: as described in section 3.

Access tokens

After you grant access, the platform issues an access token. It is stored encrypted in a separate cloud project that exists only for this one client. The central Connect service can write the token there but cannot read it.

Data from the connected accounts

  • Advertising platforms (Meta, Google Ads, TikTok, Pinterest, Snapchat): ad accounts, campaigns, ad groups, ads, and cost and performance figures per day.
  • Klaviyo: campaigns, flows and the revenue attributed to them.
  • Shopify: orders, products and inventory, to calculate revenue and results per day.
  • HYROS: attributed revenue.

In the first stage I only read data. I do not change anything in the accounts.

8. Bekara Connect: how I use the data

Only to show the client who connected the account their own figures: advertising cost, revenue and results per day in their own dashboard.

I do not sell data and do not pass it on to third parties. I do not use it for my own advertising or for profiling. I never show one client's data to another client and never combine it with other clients' data.

Data from Google accounts. Bekara Connect's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements.

9. Bekara Connect: storage location and processors

Connect and the client projects run on Google Cloud (Google Cloud EMEA Limited, Ireland) at locations in Switzerland and the EU. Each client has a separate cloud project of their own.

The connected platforms process the data under their own privacy policies, in part outside Switzerland and the EU.

10. Bekara Connect: disconnecting and deletion

You can disconnect at any time:

  • in Connect under "Manage" and "Disconnect", or
  • directly at the platform by removing access for the app "Bekara Connect" (at Google, for example, in your Google Account under "Security", third-party apps).

On disconnecting, access is revoked at the platform and the stored access token is deleted. No further data is retrieved.

Data already retrieved from that platform is deleted within 30 days after disconnecting, unless the client expressly asks to keep their existing reports and the platform's terms allow it. When the collaboration ends, I delete all of the client's data within 30 days, unless a statutory retention duty applies.

11. Bekara Connect: security

All transfers are encrypted (HTTPS). Access tokens are stored encrypted in the Secret Manager of the respective client project and never appear in logs or reports. Only I and the services of that project have access to a client project.

12. Your rights

You have the right to obtain information about the personal data stored about you and to have it corrected or deleted. Contacthallo [at] bekara [dot] tech.

13. Changes

This privacy policy may be updated when needed. The version published on this page applies. Last updated: November 2026.