Privacy Policy

This policy explains how Safli Technologies Ltd (“Measura”, “we”, “us”) handles personal data in the Measura mobile measurement platform. It covers the Measura SDKs, the event ingestion and attribution services, the deep link redirector, and the developer and administrator dashboards.

Two audiences are addressed. If you are a customer, meaning a company that has integrated our SDK, sections 2 through 12 describe what we do with data collected through your app. If you are an end user of an app that uses Measura, section 13 explains your rights and how to exercise them.

If you sign in to a Measura dashboard with your Google account, section 14 explains exactly what Google shares with us and how we handle it.

For data collected through a customer’s app, Measura acts as a data processor. The customer decides what to collect and why, and we process it on their documented instructions. The customer is the controller and is responsible for having a lawful basis and for giving notice to their users.

For a limited set of platform level processing, principally fraud detection signals evaluated across our whole customer base, and for account data belonging to our own customers, Measura acts as a controller.

Measura ships a single SDK, for Android. The following fields are sent with every event.

Fields sent only in specific circumstances

Three things are recorded by our servers rather than by the SDK.

• A masked IP address. We take the source address of the request and truncate it before storage. IPv4 addresses lose their final octet, becoming a /24 network. IPv6 addresses are truncated to a /48 block. The full address exists only in memory for the duration of the request.
• The HTTP user agent header. Used for fraud signals such as detecting automated clients.
• A computed fingerprint hash. A one way hash of the masked IP address, user agent, device model, screen resolution and operating system version, used for probabilistic matching when no deterministic identifier is available.

Stated explicitly, because the absence is as important as the presence.

• No location data. No GPS, no coarse location, and no IP based geolocation lookup.
• No contacts, photos, messages, calendar or file access. The SDK requests none of these permissions.
• No browsing history and no cross app tracking beyond the attribution of a click to an install within a single customer’s account.
• No hardware identifier. ANDROID_ID, IMEI, MAC address and serial number are never read. The advertising ID, which the SDK does collect by default, is resettable and can be cleared or switched off by the user at any time from system settings.
• No raw IP address in storage, as described above.

The Measura Android SDK reads the Google Advertising ID by default and sends it with events. It is used to attribute an install to the click that caused it, and to report that conversion back to the ad network a customer has configured.

An integrating app can switch collection off entirely with collectAdvertisingId = false. Apps directed at children are required to do so. Attribution continues to work without it: the Play Install Referrer carries a click identifier through the store install and ranks above the advertising ID in our matching order.

Our ingestion endpoint will accept an advertising identifier if a customer chooses to send one through a direct server to server integration, and historical data imported from another platform may contain them. Where either applies, the customer is instructing that processing and is responsible for the lawful basis. Where an operating system supplies the all zero placeholder that signals limited ad tracking, we discard it after signature verification rather than storing it.

The SDK exposes disableTracking(), which stops event collection entirely, and enableTracking() to resume. The setting is written to disk immediately, so an opt-out survives an app restart and does not need to be reapplied on launch.

Obtaining valid consent from end users is the responsibility of the customer operating the app, since they are the controller of that data.

We do not sell personal data. We do not use customer event data to build cross customer advertising profiles, and we do not share one customer’s data with another.

Where Measura acts as processor, the lawful basis is established by our customer as controller. Under Nigeria Data Protection Act 2023 (NDPA) and the GDPR this is typically consent for advertising identifiers, and legitimate interests for fraud prevention and service security.

Where Measura acts as controller, for platform security and fraud prevention, we rely on legitimate interests. For our own customer account and billing records we rely on contractual necessity.

We use the following sub-processors. Each has a defined role and receives only what that role requires.

Advertising network postbacks

If a customer configures a postback to an advertising network such as Meta or Google, we send that network a conversion notification when an attribution resolves. This notification includes the event type, attribution and install identifiers, the confidence score, the campaign identifier, and the advertising identifier where one is present.

This transfer happens only when the customer enables it, and the receiving network is an independent controller of what it receives. Customers should review the network’s own terms before enabling postbacks.

We may also disclose data where required by law, or to establish or defend legal claims.

The following windows are enforced by scheduled jobs in our database.

Account and billing records are retained for as long as the account is active and afterwards as required for legal and accounting purposes.

Platform data is stored in a managed Postgres database operated by Supabase, in the us-west-2 region (Oregon, United States). Our application layer runs as edge functions on the same platform, and our web properties are hosted on Cloudflare’s global network.

This means personal data collected through your app is transferred to and processed in the United States, outside Abuja, Nigeria. Where a customer’s use of Measura brings data within the scope of the GDPR or UK GDPR, we will put an approved transfer mechanism in place, such as the European Commission’s standard contractual clauses or the UK International Data Transfer Agreement, as part of the data processing agreement for that engagement. Customers with cross-border transfer requirements should raise them before integrating so the right mechanism is agreed up front.

The following controls are implemented and in use.

• IP truncation at ingestion, so raw addresses are never stored.
• Row level security on every tenant table, enforced by the database itself. Access is scoped by a server controlled identity claim, so one customer cannot read another’s data even if application code were wrong.
• API keys stored as hashes only. The plaintext key is shown once at creation and cannot be recovered afterwards.
• Cryptographically signed events. Every event carries a signature computed with a per customer secret, and requests outside a ten minute window are rejected.
• Advertising network credentials held in a secret vault rather than in application tables.
• Hardened security headers including a content security policy on both dashboards.
• An append only administrative audit log recording every administrative change with its previous and new values.

Data is encrypted in transit over TLS, and encrypted at rest by our hosting platform. We do not currently apply application level column encryption on top of that, and we do not claim to.

No system is perfectly secure. If you believe you have found a vulnerability, please report it to security@measura.dev.

Under Nigeria Data Protection Act 2023 (NDPA) and, where applicable, the GDPR, you have the right to request access to your personal data, correction of inaccurate data, deletion, restriction of processing, portability, and to object to processing. You may also withdraw consent at any time where processing relies on it.

How to exercise them

If you are an end user of an app that uses Measura, direct your request to that app’s operator first. They are the controller of the data and we act on their instructions. If you cannot reach them, contact us at privacy@measura.dev and we will help identify the right party.

If you are a Measura customer, the developer dashboard includes a form for submitting data subject requests on behalf of your users.

You also have the right to lodge a complaint with the Nigeria Data Protection Commission (NDPC) or with your local supervisory authority.

You can sign in to the Measura developer dashboard with your Google account. When you do, Google shares a small amount of information about you with us. This section covers exactly what we receive, why, where it is kept, who can see it and how to remove it.

What we access

We request only Google’s basic sign-in permissions (openid, email and profile). From them we receive:

• your email address;
• your name and profile picture;
• a Google account identifier, so we recognise you the next time you sign in.

We do not request access to Gmail, Drive, Calendar, Contacts, YouTube, Google Ads or any other Google service, and we cannot read any of that data. Google also issues a sign-in token; we never use it to call a Google service and we do not store it in our database.

How we use it

• To create your Measura account and sign you in.
• To show your name and email address to you, and to members of teams you belong to, so they know who is on the team.
• To contact you about your account, for example about billing or a change to this policy.

That is all. We do not use Google user data for advertising, we do not sell it, we do not use it to build profiles, and we do not use it to develop, improve or train generalised artificial intelligence or machine learning models. People at Measura do not read it unless you ask us to (for example in a support request), it is needed for security, or the law requires it.

How we store and protect it

It is kept in our authentication database, hosted by Supabase in the United States, encrypted in transit over TLS and at rest. Access is restricted to your own account and to the teams you join.

Who we share it with

We do not sell, rent or share Google user data with third parties. Supabase processes it on our behalf only to run sign-in (see section 9). We will not transfer it to anyone else without your explicit consent, except where the law requires it.

How long we keep it and how to delete it

We keep it for as long as your Measura login exists. To delete it, email privacy@measura.dev from the address you sign in with. We delete your login and everything Google shared with us within 30 days and confirm by email.

You can also remove Measura’s access at any time from your Google Account at myaccount.google.com/permissions. That stops future sign-ins with Google; email us as above if you also want what we already hold deleted.

Measura is a business to business service and is not directed at children. We do not knowingly collect personal data from children. Customers operating apps aimed at children are responsible for complying with the applicable rules in their market, including obtaining any required parental consent, and should not enable advertising identifier collection in such apps.

We may update this policy as the platform changes. Material changes will be communicated to customers through the dashboard or by email to the registered billing address. The revision date at the top of this page records the most recent change.

Questions about this policy, or about how we handle personal data, can be sent to privacy@measura.dev.