Privacy Policy

The data controller for this website and the Taglinko service is Taglinko, House 2, Road 3, Block C, Nobodoy Housing, Mohammadpur, Dhaka, Bangladesh.

We collect account information (name, email and, if you choose to give it, a phone number), billing information (processed by our payment provider, never stored in full on our servers), and usage data such as container logs and request counts needed to operate the service.

We also keep where you came from: the page you landed on, the website that sent you and the campaign tags in the link (UTM, such as utm_source=newsletter). When you sign up, this is saved on your account so we can see which of our posts, emails and ads bring customers. It stays with us and is not shared with Google, Meta or anyone else.

If you allow marketing cookies, we also keep the click identifiers added by Google Ads and Meta (gclid, wbraid, gbraid, fbclid), so we can tell which ads led to a sign-up or a purchase.

We use this information to provide and bill the service, respond to support requests, and monitor platform health. If you allow the matching cookies, we also use it to understand how the site is used and to measure our advertising (see Analytics and advertising below). We do not sell your personal information to third parties.

Data you send through your Taglinko Server GTM container remains yours. We access customer containers only to provide support you request or to investigate abuse or security incidents, and as described under COD Order Protection below.

When you turn on COD Order Protection for a Server GTM container, Taglinko stores the cash-on-delivery orders your container holds: order ID, value, items, time, ad click IDs, and your customer's name, email, phone number, city, IP address and browser. Personal details are encrypted when stored.

We use this data to send confirmed orders to your ad platforms and to run and improve the COD Order Protection service. We keep it after the order is confirmed, rejected or expired. We never sell it or share it with other Taglinko customers.

You are responsible for telling your own customers that their order data is processed for advertising measurement. To have this data deleted, contact us.

If you choose Connect Google on a Server GTM container, you sign in with Google and allow Taglinko to view and manage your Google Tag Manager containers. With that access we only:

• list your Tag Manager accounts and their server containers, so you can pick one;
• read the picked server container's ID and its live environment's ID and authorization code, to build the container config your Taglinko container needs;
• create a new server container in your account, if you ask us to;
• set that container's Server container URLs to your Taglinko container's addresses, so Tag Manager's Preview mode reaches it.

We do not read or change your tags, triggers, variables, web containers or published versions. We keep your Google email address, the access Google granted and a refresh token (encrypted), plus the ID of the container linked to each Taglinko container. We never sell this data, share it with anyone else, or use it for advertising.

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

How we protect this data.

• Encrypted in transit. Everything between your browser, Taglinko and Google travels over HTTPS (TLS).
• Encrypted at rest. The refresh token is encrypted with AES-256-GCM before it is saved. The encryption key is kept apart from the database, so a copy of the database alone cannot be used to read it.
• Short-lived access. The access tokens Google gives us expire within an hour and are kept only in our server's memory, never written to disk or to logs.
• Never exposed. No part of the dashboard or our API returns the token, so it never reaches a browser and our staff cannot view it. It is used only by Taglinko's own servers, only for the actions listed above.
• Restricted access. Our production servers accept logins only with personal SSH keys held by the Taglinko team. The container config built from your Tag Manager data is stored only in your own container's settings.
• Deleted when you leave. Disconnecting revokes the token at Google and deletes it straight away. Deleting your Taglinko account deletes it too.

You can disconnect at any time with Disconnect next to your Google account in the dashboard, which revokes our access and deletes the stored token, or from your Google Account's third-party access page. Deleting your Taglinko account deletes the connection too.

When you first visit taglinko.com, only the cookies needed to keep the site working are used. Analytics and marketing cookies stay off until you allow them in the cookie banner. You can change your choice at any time from Cookie preferences in the footer. A choice made on taglinko.com also applies to the dashboard at app.taglinko.com. If you say no, no analytics or advertising cookies are set; only the strictly necessary ones and our owntaglinko_src cookie described below.

• Strictly necessary. Keeping you signed in (the session cookie), remembering your cookie choice (taglinko_cookie_consent, taglinko_consent), the security check on forms (Cloudflare Turnstile), and, if you arrive through a partner link, the partner's code (taglinko_ref) so the partner is credited.
• Where you came from. Our own taglinko_src cookie keeps the campaign tags (UTM), the website that sent you and the page you landed on for up to 90 days, so we know which of our links brought you. It is set for every visitor, is only read by Taglinko and is never shared with advertisers.
• Analytics. Google Analytics, loaded through Google Tag Manager, to count visits and see which pages and plans people look at (cookies such as _ga).
• Marketing. Google Ads and Meta (Facebook) measurement tags (cookies such as _gcl_*, _fbp, _fbc) and our own taglinko_attr cookie, which keeps the ad click identifiers described above, with the campaign tags, for up to 90 days.

If you allow analytics cookies, Google receives information about your visit, such as the pages you view. If you allow marketing cookies, Google and Meta also receive events such as viewing a plan, creating an account, starting checkout, sending a contact form and buying a plan, with the plan and amount involved. We use this to see which ads work and to show our ads to people who may be interested.

To match these events to an ad click more reliably, we may also send your email address, phone number, name and billing address to Google and Meta. They are converted to a one-way code (hashed) before they leave our systems or browser, and they are used only for this matching. We may send these events from our own servers as well as from your browser. We never send your password or card details, and we do not send any of this unless you allowed marketing cookies.

Google and Meta use the information under their own privacy policies. You can withdraw your choice from Cookie preferences at any time, or ask us to delete the attribution saved on your account at hello@taglinko.com.

You may request a copy of or deletion of your account data at any time by contacting hello@taglinko.com.