Privacy policy
Last updated: 22 November 2026
The short version
Your privacy is important to us. We do not keep your photos. We keep the words of a message for one year, so a new tablet can have them back, then delete them.
- Once a photo has reached the user's tablet and is safely stored there, our server deletes its copy. The words of a message are kept for one year, then deleted. Backup copies are gone within 30 days. The only exception is anything we have had to report to the authorities, which we keep securely for one year, as the law requires, and then delete.
- If the user's tablet is replaced, lost, or the app is put on again, the old photos do not come back. The family should keep their own originals.
- Bobbles is free. We do not sell your information, track you around the internet or build profiles of you. There are no advertising tools or third-party analytics in our apps or on our website.
- We count how often each part of the app is opened, added up across everyone, so we can see what people enjoy and make it better. Our website keeps simple totals of its visits for each day and each hour in the same way. We never record what any one person does.
- An older person (we call them the user) only receives photos and messages from people their family have let in. The user can only send back a heart.
- We take camera and location details out of every photo before it is passed on.
- You can see, correct, download or delete your information. Write to admin@silverseekers.co.uk.
Who we are
Bobbles is run by Silver Seekers Ltd, registered in England and Wales, company number 17477350, registered office 22 Deepdene Vale, Dorking, England, RH4 1NL. We are the "controller" of your information: we decide how it is used and we are responsible for looking after it.
Silver Seekers Ltd offers the app through the app store, and is responsible for your information.
We pay the data protection fee to the Information Commissioner's Office (ICO), the UK's data protection regulator.
The person responsible for data protection at Bobbles is Iain Vellacott, a director. Write to admin@silverseekers.co.uk about anything in this policy, to ask for your information, or to tell us about a problem. We do not have a Data Protection Officer, because the law does not require a service of our size and kind to have one.
Who uses Bobbles
| You are… | What that means |
|---|---|
| A user | The older person the app is for. You use the Bobbles app on a tablet. Your account may have been set up for you by a member of your family or a carer. |
| A manager | A family member, friend or carer who sets up and manages a user's account, using the manager pages in a web browser. A user may have more than one manager, and a manager may manage more than one user's account. A user who manages their own account is a manager too. |
| A sender | Someone a manager has allowed to send photos and messages to a user, using a private link on their phone. Senders do not need an account. Senders may be children, such as grandchildren. |
| Someone who has been invited | A manager may type in your email address to invite you to send, or to become a manager for a user. |
| An independent account | A user's account that the user manages themselves. |
| A managed account | A user's account run for them by a manager. |
User and manager accounts are for people aged 18 and over. Senders can be any age. In the United States, a child under 13 may only be added as a sender by their parent or guardian, who agrees on the child's behalf.
What we collect, and why
If you have an account (users and managers)
| What | Why |
|---|---|
| Your name and email address | To create your account, let you sign in, and link a user with their managers. |
| Your phone number, if you are a manager of someone else's account | So the person whose account it is, and anyone with them, can see who their managers are and how to reach you. It is shown on their tablet. |
| Your password | Only as a scrambled "hash". We never store or see the password itself. |
| When you created the account, when you last signed in, and when you confirmed your email | To keep your account secure. |
| A code when you confirm your email or reset your password | To prove the email is yours. We keep only a scrambled copy, for 30 minutes. |
| A sign-in record for each device | To keep that device signed in. We keep only a scrambled copy. It ends 180 days after the device was last used. |
| A notification token for your device, if you allow notifications | To tell you when something new has arrived. |
About a user
| What | Why |
|---|---|
| The user's name and, if chosen, a picture for their profile | To show it in the app and to the family. |
| The user's home town, chosen by a manager from a place search | To show the weather and the old maps for where they live. |
| The user's settings: which parts of the app are switched on, puzzle level, text size, chosen radio stations | To set the app up the way the family chose. |
| The name, email and phone of the person who set up a user's app, if the user adds them | So anyone with the user can see who to ask for help. It is shown on the user's tablet. |
| Photos and messages sent to the user | To pass them on to the user's tablet. See "Photos and messages" below. |
| Diary dates and birthdays the family add | So they are in the user's diary. |
| Busy times | If you keep your own diary in Bobbles, the people who look after you can see when you're busy (just the time, never what you've written), so they know when to call. You can turn this off, and we only keep the next few weeks. |
| Your iPad or tablet | Bobbles works on one iPad or tablet per person, so photos only ever go to the right one. To do that we keep a scrambled code that recognises your iPad or tablet. It isn't used for anything else, and it's deleted with your account. |
| A heart the user sends back | So the sender can see it. |
| Puzzle progress | So the user can carry on where they left off. |
| When the user last opened each part of the app | To show a small mark for what is new. |
| People the user has quietly blocked | So nothing from them reaches the user. The blocked person is not told. |
Location for the weather. Only while the Weather page is open, and only if the user allows it on the tablet, the app works out roughly where the tablet is, rounded to about a kilometre, and uses it to fetch the forecast. The tablet itself turns the position into a place name. We do not store the location. If the user does not allow it, we use the home town instead. The user can change this at any time in the tablet's Settings.
The camera. The Magnifier and Mirror tools use the camera to show a live picture on the screen. Nothing is recorded, saved or sent anywhere.
Adding photos to Photos. When you delete your account on your iPad or tablet, Bobbles asks once if it may add your photos to the iPad's Photos app, or the tablet's photo gallery, so you keep them. This is add-only: Bobbles can put photos in, but it cannot see or read anything already in your Photos. If you say no, nothing is added. It makes no new album.
Keeping family photos in your device's own Photos. If you allow it when Bobbles is set up, or turn on "Keep photos in Photos too" in Settings, Bobbles also saves a copy of each family photo into your iPad's or tablet's own Photos app, about two days after it arrives. Messages are never copied, and nor is any photo you have removed or told us about, or that has been taken down. Bobbles asks only for permission to add photos, never to see or read your photo library. Once a photo is in your Photos it is yours: it stays there if Bobbles is removed or your account is deleted, and Bobbles cannot change or remove it. If iCloud Photos (or your tablet's photo backup) is on, those copies are also kept by Apple (or your backup provider) and may appear on your other devices signed in to that account. You can turn this off at any time in Settings; photos already copied stay in your Photos until you delete them there.
Old Maps. Old Maps open on the user's home town, chosen by the family. They never use the tablet's location.
About senders
| What | Why |
|---|---|
| The name the manager gave you | So the user knows who a photo is from. |
| What you send: photos, messages, and diary dates if you are allowed | To pass them on to the user. |
| A random code for the phone that first opened your link | So your private link only works on your phone. |
| Your email address, if your link did not come to you by email, and when you confirmed it | So we know the link is in the right hands, and so one person is always one sender. |
| What you are allowed to send, and whether a manager looks at things before the user sees them | To keep the user safe. |
| How the family know you (for example Grandson) | Shown on the user's tablet, so anyone with them can see who is able to send. |
| Whether you are under 16 | Senders under 16 need a parent's OK before anything they send is delivered. |
| If you are under 16: your parent's or guardian's email address, which manager gave it (if a manager did), and their answer (yes or no) and when they gave it | Only to ask your parent and to record what they said. |
| If a manager who is your parent or guardian gave the OK when they added you: which manager it was, and when | To record who said yes. |
Senders do not create an account. The first time someone sends with a link that did not come to them by email, we ask for their email address and send a short code to it, so we know the link is in the right hands. We keep the email address with the sender, so one person is always one sender, and it is deleted with the sender. We never ask a sender for their phone number.
Before someone sends for the first time, we ask one question: are you 16 or over? We don't ask people who told us they are 18 or over when they joined the family app. If the answer is no, we ask for a parent's or guardian's email address, email the parent once to ask whether that is all right, and hold anything sent until they say yes. A manager who is the child's parent or guardian can give the OK when they add them; we keep a note of who gave it and when. A manager who is not the parent can give us the parent's email when they add the child, and we email the parent straight away. We use the answer, the parent's email and that note only to ask and to record the answer, never for anything else, and they are deleted with the sender.
About people who have been invited
The email address a manager typed in, the name they gave, and who invited you. We use it only so that you see the invitation when you sign in with that email address. An invitation stays open until it is accepted, declined or withdrawn.
An activity record for each user
We keep a short line for each thing that happens on a user's account, such as "Sarah sent a photo". A user's managers can see it, so the family can check what has happened. We keep each line for 12 months.
Our server's request log
When your device talks to our server, the server writes one line: the time, your internet (IP) address, which part of our service was asked for, whether it worked, and how long it took. It never records what you sent. We use it to keep the service running, to stop misuse, and to look into problems. The log is kept for about a month. The once-a-minute message described below, and our website's visit count, are logged without the internet address.
How often each part of the app is opened
We count how often each part of the app is opened, added up across everyone, so we can see what people enjoy and make it better. We never record what any one person does.
This is how it works. The user's tablet keeps a simple count for each day of how many times each part of the app (Photos, Games, Radio and so on) was opened. Once a day is over, the tablet sends us that day's part-opened numbers and nothing else in them: no times, no order, nothing about what was looked at or played. We add them to the totals from everyone else for that day, and we do not keep who sent them. What we keep is, for each day, how many times each part of the app was opened in all, and on how many tablets. The counts are ours alone: no other company is involved, and they are never sold or used for advertising.
While the app is open it communicates with our server about once a minute. It only says whether it is an iPad or an Android tablet, with a random code that changes every time the app is opened. This lets us see how many people are using Bobbles at any time, to help us understand the position. It is never linked to you or your tablet. We don't keep your internet address with it and we only keep each day's totals.
How our website counts visits
Our website counts how many times each page is visited each day, which kind of site the visitor came from (such as Facebook or a search engine), and how many people tap through to the App Store or Google Play. These are just totals for each day, and for each hour of the day. We do not use cookies, we do not keep your internet address, and we never record what any one person does.
The counting is done by our own server: no other company is involved. When a page opens, it tells our server which page it is, the name of the website the visitor came from (just the name, never the page they were on), and the short code at the end of a link we have shared, if there is one. If the visitor taps a button for the App Store or Google Play, it says which. We add one to that day's totals and keep nothing else.
The same goes for the page where anyone can try Bobbles in a web browser: it adds one to that day's totals for each time it is opened on a computer, tablet or phone, each time the film on the phone page is played, and each time a store button is tapped, and keeps nothing else.
When the app goes wrong
If something goes wrong in the user's app, the tablet sends our own server a short crash report so we can find the fault and fix it. It says what went wrong in the app's own code, which screen it was on, which version of the app it was, and what kind of device it is. We do not collect anything typed, any photo, anything that identifies the tablet, or your internet address with it. Before it leaves the tablet, and again on our server, anything that looks like an email address, a phone number, a postcode or a quoted name is taken out, and web addresses are cut down so they carry no codes or ids. No other company is involved. We keep each one for 30 days after the problem was last seen.
What we do not collect
No advertising identifiers. No third-party analytics, and nothing that records what any one person does in the app. No crash-reporting company: our own crash reports are described above. No contact lists taken from your phone. No payment details. We do not use your information to make automated decisions about you, and we do not profile you.
Photos and messages
We do not keep photos on our server. Once a photo has reached the user's tablet and is safely stored there, our server deletes its copy. The words of a message are kept for one year, then deleted. Backup copies are gone within 30 days.
If the user's tablet is replaced, lost, or the app is deleted and put on again, the old photos do not come back, and only the last year of messages does. The family should keep their own originals, and can send any of them again.
The only exception is anything we have had to report to the authorities, such as child sexual abuse material. We keep that securely for one year, as the law requires, and then delete it.
Important: we are not responsible for storing photos. Anyone who sends a photo must keep their own original if they want to keep it.
In more detail:
- A photo waits on our server only until the user's tablet has the whole photo safely stored and has told our server so. Our server then deletes the photo within a day.
- Something that has not reached the tablet yet waits for it, however long that takes, or until the account is deleted. A photo that a manager is looking at first waits until they decide.
- The words of a message are deleted once the message has reached the tablet and is a year old. The user's tablet keeps its own copy.
- Something the family take down is deleted from our server within days: a photo 3 days after it was sent; a message after a year (we keep a note that it was taken down, so the tablet takes it off too).
- Once a photo or message has gone, we keep a small note that it was sent, who it was from, whether it was a photo or a message, and any heart the user sent back, for 30 days, so that a heart can still reach the sender. It has no picture and no words in it. Then that goes too.
- Diary dates and birthdays stay on our server until the family take them out or the account is deleted, so the user's diary is always complete.
Before a photo is passed on, our server makes it smaller and saves it again. This takes out hidden details such as where the photo was taken and which camera took it. While a photo is on our server, it can only be opened by the user's app, the user's managers and the person who sent it, through a private link that stops working within two days. There are no public photo addresses.
Safety checks. Photos come only from people the family have let in. The words of every message, and the names people use, are checked automatically on our own server before they are passed on, to try to stop web links, phone numbers, bank details and signs of a money scam. No automatic check is perfect. The user and their managers can report anything and block anyone, or tell us at admin@silverseekers.co.uk, and we will act on it straight away. We keep a short safety record of any words the checks stop for 12 months.
If we were ever to find child sexual abuse material, we are required by law to report it, and we will. We report it once: to the National Crime Agency, or, if anyone in the United States is involved, to the National Center for Missing & Exploited Children (NCMEC) instead, which passes anything linked to the UK on to the National Crime Agency. We keep what we have reported securely for one year, as the law requires, and then delete it. The account responsible will be closed.
Who can see what is sent. Everything sent to a user stays inside the family circle. The user's managers can see what is sent to the user. People the family invite are trusted, and what they send goes straight to the user. Anyone else's photos and messages also reach the user straight away, and the managers can see what they send. A manager can choose to look at things from any one person before the user sees them.
Notifications. A notification only says who something is from and what kind of thing it is, for example "A photo from Sarah" or "A message from Sarah". It never includes the words of a message or a diary date.
Safety checks
If we have reason to believe that an account may be being used for something it isn't meant for, which could be against the law, we may look at the photos sent to it. We only do this for that account, only to keep people safe, and never to sell or share anything.
Our lawful basis is legitimate interests (keeping people safe).
Where your information comes from
Most of it comes from you. Some comes from other people:
- A user's account, name, home town and settings are usually entered by a manager.
- Photos, messages, diary dates and birthdays come from managers and senders. They may include information about other people, such as a grandchild's name or birthday.
- An invited person's email address comes from the manager who invited them.
Our legal reasons for using your information
Data protection law says we must have a reason, called a "lawful basis", for each thing we do with your information. These are ours:
| What we do | Lawful basis |
|---|---|
| Running the account of a manager, or of a user who signed up themselves | Contract: we need to do this to provide the service you signed up to. |
| Running the account of a user set up by a manager | Legitimate interests: the user's own interest, and their family's, in staying in touch in a safe, simple way. We have weighed this against the user's rights and expectations. The user, or someone acting for them, can ask us to stop at any time. |
| Passing on what a sender sends, and holding an invited person's email address | Legitimate interests: letting the family keep in touch with the user. |
| The request log, limits on repeated attempts, the activity record and keeping accounts secure | Legitimate interests: keeping the service and the people who use it safe. |
| Counting how often each part of the app is opened, added up across everyone | Legitimate interests: finding out what people enjoy, so we can make the service better. Only totals across everyone are kept, never what any one person does. |
| Counting our website's visits each day | Legitimate interests: finding out whether people find our website, and how, so we can tell more people about Bobbles. Only totals for each day and each hour are kept, never what any one person does. |
| Device location for the weather, notifications, and adding photos to the iPad's Photos app, or the tablet's photo gallery | Consent: only with the permission you give on the device, which you can take back at any time in the device's Settings. |
| Looking at the photos sent to one account we have reason to believe is being misused, by us or by our own automatic check | Legitimate interests: keeping people safe. |
| Asking whether a sender is under 16, and asking their parent | Legitimate interests: keeping people safe. |
| Meeting legal duties, such as answering the ICO, or reporting child sexual abuse material and keeping what we reported | Legal obligation. |
When someone sets up an account for a user. A manager who creates an account for a user confirms that the user has agreed, or that the manager is acting in the user's best interests, for example as their attorney.
Sensitive details. We do not ask for health, religion or similar details. Someone may choose to write something like that in a message or a diary date. It is handled in exactly the same way as everything else, and we never use it for anything other than passing it on.
Who else handles your information
We do not sell your information or share it for anyone else's use. We use a small number of companies to run the service. They act only on our instructions.
| Company | What they do for us | What they receive | Where |
|---|---|---|---|
| DigitalOcean | Hosts our server, database and the photos waiting to be passed on | What is on our server, on an encrypted disk | London, United Kingdom |
| Cloudflare (R2 storage) | Stores our encrypted backups | Encrypted backup files only. They cannot read them. | European Union |
| Resend | Sends our emails: sign-in codes, password resets and account notices | Your email address and the email's text | European Union |
| Twilio | Sends the text-message code when we need to confirm a manager's phone number. | It receives the phone number only. | United States |
| Google Workspace | Our email inbox, admin@silverseekers.co.uk | Whatever you write to us | Google's data centres, which may be outside the UK |
| Anthropic | Runs Stella, the AI assistant that helps us with the work behind the scenes, such as reading and sorting the emails you send us | Whatever you write to us, and the details needed to look into a problem you report | United States |
| Expo, and then Apple or Google | Delivers notifications to the tablet, and delivers app updates | The device's notification token, and the notification: who something is from and whether it is a photo or a message | United States |
| Apple (App Store) | Provides the app on an iPad | Apple's own terms and privacy policy apply | United States |
| Google (Google Play) | Provides the app on Android tablets, and delivers notifications to them | Google's own terms and privacy policy apply | United States |
Services our server asks for things without saying who is asking. These receive no information about you:
- Open-Meteo gets a place, or a position rounded to about a kilometre, and returns the weather.
- postcodes.io and Open-Meteo get the words a manager types when searching for a town.
- MapTiler and Esri send the map squares for Old Maps. The old maps are from the National Library of Scotland, served by MapTiler; the present-day pictures are from Esri.
- YouTube sends the still pictures shown for the daily Smile clip and the Nostalgia film.
- YouTube is asked, while a service in the Live door is on, for that service's public live page, so we know which video is that day's service. Nothing about anyone is sent.
Things the tablet fetches directly. Some things play straight from their source, so that service can see the tablet's internet address, as any website can:
- Films (the daily Smile clip, Spotlight and other films, and the services in the Live door) play from YouTube, in its privacy-enhanced player (youtube-nocookie.com), inside the app. When one plays, YouTube (Google) receives the tablet's internet address and may store information on the tablet, under Google's own privacy policy. YouTube may also show its own short advert before a film. We don’t choose these adverts, we earn nothing from them, and we never tell YouTube who you are.
- Radio plays straight from the broadcaster, such as the BBC.
Our website and send page use their own copy of their lettering, so opening them tells no font service who you are.
We may also share information if the law requires it, or to protect someone from serious harm.
Every manager of a user's account agrees, in our terms, to give the full list of people who can send to the user, and how to reach them, to anyone with a genuine concern for the user. For a child, they give a parent's details rather than the child's.
Information that leaves the UK
Our server is in London. Some of the companies above are based in, or use services in, the European Union or the United States. Where information goes outside the UK, it is protected by the UK's adequacy rules (which cover the European Union, and US companies certified under the UK–US data bridge) or by the UK's approved contract terms.
If you live in the United States
Bobbles is run from the UK. If you live in the United States, your information is handled in exactly the same way as everyone else's, and kept in the same places: on our server in London, and with the companies listed above. This policy applies to you in full. You can ask to see, correct, download or delete your information in the same way, by writing to admin@silverseekers.co.uk, and we will reply within one month.
How long we keep things
| What | How long |
|---|---|
| Photos | Deleted from our server within a day of being safely stored on the user's tablet. |
| Messages | Deleted from our server once on the user's tablet and a year old. |
| Something the family take down | A photo 3 days after it was sent; a message after a year (we keep a note that it was taken down, so the tablet takes it off too). |
| The note that something was sent, and any heart | 30 days after the photo or message itself has gone. |
| Diary dates and birthdays | Until the family take them out, or the account is deleted. |
| Busy times | Only the next few weeks. Nothing is kept once it is turned off, or when the account is deleted. |
| The scrambled code for the user's device | Until the account is deleted, or it moves to another device. |
| Your account and the user's settings | Until the account is deleted. |
| Sign-in records | 180 days after the device was last used, then deleted automatically. |
| Email and password-reset codes | 30 minutes, then deleted automatically. |
| A sender's email code | Kept only as a scrambled copy, until it is used or runs out after 30 minutes. |
| The safety record of any words the checks stop | 12 months, then deleted automatically. |
| The activity record | 12 months, then deleted automatically. |
| Unanswered invitations | Until accepted, declined or withdrawn. |
| Whether a sender is under 16, their parent's email address, the parent's answer, and the note of which manager gave the OK and when | Deleted with the sender. |
| Anything sent while waiting for a parent's yes | Deleted after 14 days if the parent has not said yes, and straight away if they say no. |
| The server's request log | About a month. |
| Crash reports | 30 days after the problem was last seen, then deleted automatically. |
| Counts of how often each part of the app is opened | On the user's tablet, a day's count until it has been sent, and never more than two weeks. On our server, only the totals across everyone, kept for two years and then deleted automatically. |
| Our website's visit totals for each day and each hour | Kept, as they say nothing about any one person. Nothing about a visitor is kept at all. |
| Backups | Encrypted, and kept for up to 30 days. Anything deleted is gone from our backups within 30 days. |
| Device location for the weather | Not stored. |
| Anything we have had to report to the authorities | Kept securely for one year, as the law requires, then deleted. |
Deleting your account
- A user can delete their account in the Bobbles app: Settings, then Lock, sign out or delete, then Delete this account.
- A manager can delete their account on the manager pages: your account, then Delete this account. If you are a user's only manager, we ask you to invite someone else first, or to delete the user's account, so the user is not left alone.
Deleting an account removes it and everything that belongs to it. This cannot be undone. Copies in our backups are gone within 30 days.
When you delete your account on your iPad or tablet, the photos and messages already on it stay on it, and your photos are copied into the iPad's Photos app, or the tablet's photo gallery, if you allow it.
Senders do not have an account. To have something you sent removed, ask the user's family, or write to us.
Your rights
You have the right to:
- see the information we hold about you, and have a copy of it;
- correct it if it is wrong;
- delete it;
- object to us using it, or ask us to limit how we use it;
- take it with you, in a file a computer can read;
- take back your permission for location, notifications or adding photos to Photos at any time, in your device's Settings.
To use any of these rights, or to ask for a copy of your information or for it to be deleted, write to admin@silverseekers.co.uk. We will reply within one month, as the law requires, or tell you within that month if we need longer. We may ask you to prove who you are first. A family member or attorney can ask on behalf of a user. A parent or guardian can ask on behalf of a child. It is free.
Children
Bobbles is made especially for older people and their families, and for anyone who likes a calmer corner of the internet. User and manager accounts are for people aged 18 and over. Children of any age may send photos and messages to a user, with a parent's knowledge, through a private link that a manager gives them.
Children don't have their own accounts. They send with a link from a parent, and younger grandchildren play and see photos on a parent's device.
In the United States, a child under 13 may only be added as a sender by their parent or guardian, who agrees on the child's behalf.
We have followed the ICO's Children's Code:
- a child needs no account, and we never ask a child under 16 for their own email address or phone number;
- we ask senders whether they are under 16 (people who have told us they are 18 or over are not asked again), and if so for a parent's email, only so that a parent can say yes before anything is delivered;
- we collect only what they choose to send, and the name the family gave them;
- we never show a child adverts, track them or profile them;
- a child can only ever send to the one user their link belongs to;
- there is no newsletter and no marketing.
The send page tells every sender, in the user's own name, for example: "What you send goes to Grandma, and the grown-ups who manage Grandma's account can see it too. It stays private to the family." It also shows a link to this policy and says: "Problem? Email us at admin@silverseekers.co.uk"
Keeping your information safe
- Passwords, codes and sign-in records are stored only in scrambled form.
- Everything travels over encrypted connections.
- Photos on our server can only be reached through private links that stop working within two days.
- Backups are encrypted before they leave our server.
- A user can only be reached by people their family have let in.
If something goes wrong that puts your information at risk, we will tell the ICO within 72 hours where the law requires it, and we will tell you if you are affected. Please report any problem to admin@silverseekers.co.uk.
Cookies and similar storage
We do not use cookies. The send page and the manager pages save a small note on your device, such as a random code for your phone or your sign-in, so that they keep working. The website remembers whether you chose light or dark colours. The user's tablet keeps its own count of how often each part of the app was opened each day, until that day's numbers have been sent (see "How often each part of the app is opened"). Our website's visit count saves nothing on your device at all (see "How our website counts visits"). None of this is used to track you.
Changes to this policy
If we change this policy, we will put the new version here with a new date. If the change is important, we will tell account holders in the app or by email before it takes effect.
Questions and complaints
Write to admin@silverseekers.co.uk. If you are not happy with our answer, you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint, or by calling 0303 123 1113.