Privacy Policy

Who we are

DecTog is operated by Abdelrahman Saed, an individual based in Egypt ("DecTog", "we", "us"). For any privacy question or request, email support@dectog.com.

Our two roles

DecTog handles two kinds of personal data, and our role differs for each.

• Data about our customers and visitors. This covers your DecTog account and team, billing, messages you send us, and visits to dectog.com. We decide how this data is used, so we are its controller.
• Data about our customers' end users. When people tap a customer's link, install or open a customer's app, or visit a customer's website that uses the DecTog pixel, we process their data on that customer's behalf and following their settings. The customer is the controller and we are their processor.

Customers are responsible for telling their end users about DecTog in their own privacy notices, for their app store privacy disclosures, and for having a legal basis for the data they collect, including consent where the law requires it. If you are an end user, the app or website that used the link is the best place to start; you can also write to us and we will pass your request on and help the customer answer it.

Account data

• Sign-up and sign-in: your email address, username and password. We store the password only as a salted hash, never in readable form. If you sign in with Google, we keep your Google account ID and email address.
• Teams: the accounts you belong to and your role in each. An invite stores the invited email address and who sent it, and the invite email shows the sender's address.
• Keys and settings: account settings and API keys. Keys are stored hashed; SDK and website keys are also kept encrypted so the dashboard can show them to you again.
• Audit log: a record of changes made in each account: who made the change, what changed (with secrets removed), a hashed IP address and the browser's user agent. Failed sign-in attempts are recorded too.
• Billing: payments for paid plans go through Creem, which acts as merchant of record. Creem handles your card and billing details under its own privacy policy; we never see or store card numbers. We receive what we need to manage your plan, such as the plan, its status and the billing email.
• Messages: if you use the contact form, we keep your name, email address, subject and message. If you email us, we keep the email.

Link data

When someone opens a DecTog link, the service records the click so it can route the visitor and credit the right link:

• The IP address, stored in full and as a salted hash.
• The browser's user agent, the device model and operating system version the browser reports, and the preferred languages.
• The referring website, reduced to its domain.
• Approximate location derived from the IP address by Cloudflare: country, region, city and network provider. We never use GPS or precise location.
• A bot score, used to leave out automated traffic, and the campaign parameters on the link.
• On some link pages, and only when the customer turns on probabilistic matching: screen size, pixel ratio, touch support, connection type, time zone offset and display settings (text size, dark mode, high contrast and reduced motion).
• Which button on the link page the visitor tapped. On iPhone, tapping the button that opens the App Store copies the link to the clipboard, so the app can find it after installing.

Links set no cookies.

Install and app data

Customers add a DecTog SDK to their app. When the app is installed or opened, the SDK sends data that lets the service attribute the install to a link and open the right content:

• App version, operating system and version, language, time zone, the install referrer from the app store, and install and update times.
• Unless the customer turns it off: a device identifier (the identifier for vendor on iOS, the Android ID on Android), device model and manufacturer, screen details, connection type, the mobile network code, display settings, and on Android the WebView user agent. On iOS the identifier is kept in the device's keychain, so it survives reinstalling the app.
• Only if the customer enables them: the Apple Search Ads attribution token, Meta's install referrer, and the advertising ID (IDFA or GAID) through a separate optional package.
• The device's IP address, in full and as a salted hash, and the network provider derived from it.
• The clipboard: the SDK reads it only to find a DecTog link and clears it after using it. We keep the link it found, never other clipboard text.
• A daily activity record per device, used to count active users and monthly active users.

Customers can also send events from their app:

• Event names, revenue, currency, purchase and refund details, screen views, and the customer's own identifier for their user.
• If the customer chooses to send them, their user's name, email address and phone number. These are stored as sent so the customer can see who converted.
• Purchase notifications from the App Store and Google Play, which we match to purchases the app reported. Apple's notifications include the storefront and the app account token the customer set.

Website pixel

Customers can add the DecTog pixel to their own websites to credit sign-ups and purchases to links. In the European Economic Area, the United Kingdom and Switzerland, or when the browser sends a Global Privacy Control signal, the pixel stores nothing until the visitor agrees. We don't store IP addresses for pixel events. The pixel sets these first-party cookies on the customer's website:

Our website and cookies

dectog.com uses no analytics, no third-party scripts and no cookies. Fonts are served from our own domain. The dashboard at app.dectog.com uses only the cookies it needs to work:

How we use data

• To run the service: route links, attribute installs and events, show reports, and send webhooks.
• To keep it secure: filter bots, limit request rates, detect fraud and investigate abuse.
• To run your account: sign-in, team invites, password resets, alerts and billing.
• To answer your messages and give support.
• To meet legal obligations.

We don't sell personal data and we don't use it for advertising. We use end-user data only to provide the service to the customer it belongs to, which includes counting that customer's monthly active users for billing, and we don't combine it across customers.

Where the GDPR or similar laws apply to data we control, we rely on these legal bases: performing our contract with you for account and billing data; our legitimate interests in running a secure and reliable service for security data, website requests and messages; and legal obligations for records we must keep.

Who receives data

We use these providers to run the service:

The service also sends data where a customer configures it to:

• To the customer's own servers, through the webhooks they set up.
• To the app stores: the link sends the visitor to Google Play or the App Store with a click reference, so the install can be matched.
• To the customer's website, with the link's campaign parameters, and to AppsFlyer, Adjust or Singular with a click ID when the customer connects one of them.

We disclose data to authorities only when the law requires it.

How long we keep data

• Link, install and event data is kept for the account's retention period: 400 days, unless the customer sets a shorter one. After it, records are deleted, or their personal fields (IP addresses, device identifier and model, user agent, region, city and network) are cleared.
• Screen and display settings from link pages are cleared after 30 days at most.
• Purchase and refund records are kept for revenue reporting after the retention period, with the device identifier, the customer's user ID, extra details and IP address removed.
• An end user's name, email and phone are cleared once they haven't been updated for the retention period.
• Daily per-link totals, which hold no personal data, are kept.
• Webhook delivery logs are kept for 30 days and the log of store purchase notifications for 90 days. When a customer deletes a link, the personal fields of its clicks are cleared after 30 days.
• Account data and the audit log are kept while your account is open. To close your account, email support@dectog.com; we delete its data within 30 days, except records we must keep by law.
• Contact messages are kept as long as we need them to answer you, and deleted when you ask.
• Database backups hold deleted data for up to 30 more days before it is gone for good.

Customers can erase or export the data held about one of their end users, by device or by their own user ID, from the dashboard or the API.

Where data is processed

Cloudflare runs the service on its global network, so data is processed in many countries. Our providers process data in the United States and elsewhere. Where the law requires it, these transfers rely on safeguards our providers offer, such as the European Commission's standard contractual clauses.

Security

All traffic uses HTTPS. Passwords and keys are stored hashed, secrets are encrypted, and webhooks are signed so customers can check they came from DecTog. No system is perfectly secure; if a breach affects your data, we will tell you and the authorities as the law requires.

Your rights

Depending on where you live, you can ask to access, correct, delete or export your personal data, object to or restrict how it is used, and withdraw consent you gave. Email support@dectog.com; we answer within 30 days. You can also complain to your local data protection authority.

If your data reached us through a customer's link or app, that customer decides what happens to it. Ask them first, or write to us and we will pass the request on.

Children

DecTog is a service for businesses and is not directed at children. Customers whose apps are aimed at children must make sure their use of DecTog meets the laws that apply to them, and can turn off device-level collection in the SDK.

Changes to this policy

We will post any change on this page with a new date. If a change is significant, we will email account owners before it takes effect.

Contact

Questions about this policy or your data: support@dectog.com. The Terms of Service cover the rest of how the hosted service works.