Only as long as needed
Data is kept for the purpose it was collected for. Recency matters most, so older events lose value and are not kept for their own sake.
Data handling
Data kept for areason, then deleted.
Retargeting needs identifiers and events, and very little else. This page lists what we touch, why, and what is still to be published.
What we process
The data the platformtouches.
Retention periods are not published yet. Each is marked below and will be filled in when confirmed.
| Category | Example | Why we process it | Kept for |
|---|---|---|---|
| Advertising identifiers | IDFA where tracking was allowed, Android advertising ID | To recognise a lapsed person in a bid request and to measure the result | Only as long as the purpose needs |
| App events | Sessions, purchases, add to cart | To build segments by recency, value and behaviour | Only as long as the purpose needs |
| Consent signals | TCF string, Global Privacy Platform string | To decide what we may do with each request | Only as long as the purpose needs |
| Bid and delivery logs | App bundle, time, outcome | To report spend by app and to detect invalid traffic | Only as long as the purpose needs |
| Product feed content | Titles, images, prices | To assemble creative for each person | Only as long as the purpose needs |
| Website enquiries | Details typed into the contact form | To reply to the person who wrote | Only as long as the purpose needs |
What we never need: names, email addresses and phone numbers of the people being retargeted, payment card data, and data about children or sensitive categories.
Retention
Principles for howlong data is kept.
Shorter where possible
Identifiers and event data used for audiences are held for shorter periods than records needed for billing or legal duties.
Written down
Each period will be stated in the agreement and listed in the table above once confirmed.
Deletion
When an agreement ends,so does our use.
At the end of an agreement
We delete the advertiser's data or return it, as the advertiser chooses, unless the law requires us to keep something.
On request during an agreement
An advertiser can ask us to delete data, including data about a single person, and we help it respond to its users.
When a person opts out
The identifier is added to a suppression list so that retargeting stops across the platform.
Sub-processors
Who else handles data for us.
We use suppliers to run the platform and this website. They fall into three categories. Each is bound by written terms carrying the same data protection duties.
- Cloud hosting for the systems that bid and deliver
- Data storage for events, logs and reports
- Email delivery for messages sent from this website
Customers are told of changes to this list under the agreement, and may object on reasonable grounds.
The current list of sub-processors, with what each one does and where, is available on request from privacy@mobiretarget.com.
Transfers
International transfers.
- Where data moves out of the EEA or the UK to a country without an adequacy decision, we rely on standard contractual clauses and any further measures the law requires
- The same applies to transfers to our sub-processors
Rights
Requests from people.
- The advertiser is the controller for its users' data, so requests belong with it
- If a person writes to us about an advertiser's data, we refer them to the advertiser and help it answer
Contacts
Who to write to.
- Privacy questions
- privacy@mobiretarget.com
- Everything else
- Use the contact page.
Questions
Data, answered.
Do you sell the data advertisers send you?
No. An advertiser's data is used to provide its services and is not offered to other customers.
Can you delete data for one person?
Yes, on the advertiser's instruction. We help the advertiser answer such requests.
Is the sub-processor list available?
Not yet. The categories are above and the named list will be published here.
Do you use data from one customer for another?
No. Each advertiser's data is kept separate and used only for that advertiser.
Get started