Privacy Policy
Disclaimer: This is a template for informational purposes. Consult with a qualified attorney for legal advice specific to your situation.
Last updated: [OWNER: date on publication]
This policy explains what personal information TurkishDictionary.co.uk ("the site", "we", "us") handles when you use it, why, and what your rights are. We have tried to keep it short and plain.
The short version: the site is a free dictionary. You do not need an account. The site shows ads from Google AdSense; Google uses cookies for advertising only if you agree in its consent message (section 17). We do not use analytics or tracking of our own. The words you search for are sent to our servers so we can show results. Our hosting providers keep ordinary technical logs. Your recent searches stay in your own browser. If you search for a phrase or sentence, the text is sent to Google Cloud Translation so it can be translated, and a bot check from Cloudflare may run first (section 11). Voice search turns what you say into text in your browser: we never receive or store recordings of your voice (section 12).
1. Who we are
The site is run by:
- Legal name: OXDPR LIMITED
- Trading name: TurkishDictionary.co.uk
- Postal address: London, United Kingdom
- Contact email: hello@turkishdictionary.co.uk
- ICO registration number: [OWNER: ICO registration number, or delete this line if the owner has confirmed no fee is due]
We are the "controller" of the personal information described here, which means we decide how and why it is used. We are based in the United Kingdom, and the UK GDPR and the Data Protection Act 2018 apply to us.
2. What information we handle
Information you give us
- Search words. When you type a word or phrase, it is sent to our servers so we can look it up and show you results. Please do not type personal information (such as names, addresses or phone numbers) into the search box. If you search for a phrase or sentence rather than a single word, the text is also sent to Google Cloud Translation to be translated (see section 11).
- Voice searches. If you use the microphone button, what you say is turned into text in your browser and that text is searched like a typed word. We receive only the text, never the audio (see section 12).
- Emails you send us. If you write to us, for example to report a problem with an entry, we will receive your email address and whatever you put in your message.
Information collected automatically
When your browser asks our site for a page or for results, the technical systems that serve the site may record:
- your IP address
- your browser and device type (the "user agent")
- the address (URL) of the page or search requested, which can include the word you searched for
- the date and time of the request
When you search for a phrase or sentence that has not been translated before, the site also derives an anonymous request-counter key from your IP address so it can limit how many new translations one visitor can start (section 11). The key is a keyed one-way hash that changes every day. Your IP address itself is not stored in our database, and the key cannot be used to recognise you from one day to the next.
These are ordinary server and hosting logs. Your IP address can identify you in some circumstances, so we treat it as personal information.
[OWNER/DEVELOPER: confirm that the site's own code does not store search words or IP addresses anywhere other than the hosting provider's standard logs. If it does, describe it here and in section 3.]
Information that stays on your device
Your recent searches are saved in your browser's local storage on your own device. They are never sent to us. See our Cookie and Storage Policy for details and how to clear them.
What we do not collect
At this stage we have no user accounts, no sign-up, no payments, no analytics and no tracking of our own. Advertising is provided by Google (section 17). We do not ask for or intend to collect special category data (such as health or religion). We never receive, store or analyse recordings of your voice, and we do not create voiceprints or any other biometric data.
3. How we use it, and our lawful basis
UK GDPR says we must have a lawful basis for using personal information. Ours is "legitimate interests" (article 6(1)(f)) for the purposes below. We have considered whether our interests are outweighed by your rights, and we think the impact on you is low.
| What we do | Why | Lawful basis |
|---|---|---|
| Use your search word to return results | To provide the dictionary you asked for | Legitimate interests (running the service you chose to use) |
| Keep server and hosting logs | To keep the site secure, find faults and prevent abuse | Legitimate interests (security and reliable service) |
| Translate a phrase or sentence you searched for, and keep the translation so the same phrase need not be translated again | To provide the translation you asked for, and to keep the cost of the service down | Legitimate interests (running the service you chose to use) |
| Limit new translations per visitor and run a bot check before them | To stop automated abuse of a service that costs money per use | Legitimate interests (security and keeping the service available) |
| Read and reply to your emails | To answer your question or fix a reported problem | Legitimate interests (responding to people who contact us) |
We do not use your information for marketing, profiling or automated decisions that affect you. We do not sell it.
4. Who we share it with
We use service providers (called "processors") who handle information on our behalf under written terms. They may only use it for our purposes.
| Provider | What for | What information |
|---|---|---|
| Vercel | Hosting the website | Request logs (IP address, user agent, requested URL, time) and the search words in requests |
| Supabase | Database hosting (PostgreSQL) and storage of generated pronunciation audio files | Dictionary content and audio files only. We do not store personal information in this database or storage at this stage. |
| Google Cloud (Google Cloud Translation) | Translating phrases and sentences | The text of the phrase or sentence you searched for, with the languages involved. No account, name or contact details; Google receives the request from our servers, not from your browser, so it does not receive your IP address from us. |
| Cloudflare (Turnstile) | A bot check, shown only when a new translation is needed | Your browser talks to Cloudflare directly: it receives your IP address and browser and device signals. See section 11. |
| [OWNER: email provider, if any] | Receiving emails sent to our contact address | Your email address and message |
Google is not our processor for advertising: for AdSense, Google acts as an independent controller of the information its advertising code collects (see section 17). Wikimedia Foundation is not our processor either. It receives your IP address and browser details only if you press play on a pronunciation recording that is played from its servers, and then acts on its own behalf (see section 10).
We may also disclose information if the law requires it, for example to answer a valid request from the police or a court.
[OWNER: confirm the final provider list before launch. If any other service is used (for example a font host, a content delivery network or a bot-protection service), add it here.]
5. Where your information goes (international transfers)
- Vercel region used for the website: [OWNER: region]
- Supabase region for the database: [OWNER: region]
- Google Cloud Translation processing location: [OWNER: location, from the Google Cloud settings and terms accepted]
- Cloudflare Turnstile processing location: [OWNER: location, from the Turnstile Privacy Addendum]
Vercel and Supabase are companies that operate internationally, and some of their processing or support may take place outside the UK, including in the United States. [OWNER: confirm with each provider where data is actually processed.]
Where personal information is sent outside the UK, UK GDPR requires a safeguard. Depending on the provider, this may be a UK adequacy regulation (for example the UK Extension to the EU-US Data Privacy Framework, where the recipient is certified), or the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses. [OWNER: state which mechanism applies to each provider once confirmed.] You can contact us for more information about the safeguards we use.
6. How long we keep it
- Hosting and server logs: [OWNER: retention period, as set by or configured with the hosting provider]. They are deleted automatically after that.
- Emails to us: [OWNER: retention period, for example 12 months after the issue is closed]. We may keep a record of a correction or takedown request for longer where we need it to show we handled it properly.
- Recent searches in your browser: until you clear them. We do not hold them.
- Saved translations: the text of a translated phrase and its translation are kept without any link to you (no IP address and no request-counter key; only when the translation was last used) until 180 days after the translation was last used (the date is updated at most once a day), then deleted automatically. Searching for the same text again reuses it.
- Request-counter keys: about two days, then deleted automatically.
7. Your rights
Under UK GDPR you have the right to:
- be told how your information is used (this policy)
- ask for a copy of your information (access)
- ask us to correct information that is wrong
- ask us to delete your information
- ask us to restrict how we use it
- object to us using it on the basis of legitimate interests
- receive information you gave us in a portable format (this applies only in limited cases and is unlikely to apply here)
These rights have conditions and exceptions. To use any of them, email hello@turkishdictionary.co.uk. We will reply within one month. We may need to ask you for details that help us find your information, such as the approximate time you used the site. Because logs are mostly held by our hosting provider and are not searchable by name, we may not be able to identify records about you unless you tell us your IP address and the time of your visit. We will not charge a fee unless a request is clearly unfounded or excessive.
8. Complaints
Please contact us first at hello@turkishdictionary.co.uk so we can try to put things right. We will acknowledge your complaint and respond without unreasonable delay. [OWNER: confirm a complaints process is in place; UK law now expects controllers to facilitate data protection complaints. Check commencement with a solicitor.]
You also have the right to complain to the Information Commissioner's Office (ICO), the UK data protection regulator, at any time: ico.org.uk/make-a-complaint. You do not have to contact us first.
9. Children
The site is for the general public, including people under 18, and there is no age check. We designed it with the ICO's Age Appropriate Design Code (the Children's code) in mind. At this stage:
- there are no accounts, so we do not ask anyone for their name, email or age
- ads are shown by Google AdSense; without consent they are non-personalised and Google sets no advertising cookies, and we do not ask Google to personalise ads for anyone we know to be a child [SOLICITOR: confirm the Children's code position for advertising on a general-audience site, and whether to tag requests for non-personalised ads only]
- there is no tracking, profiling or nudging of our own
- we do not use search words to build a profile of anyone
- the only information we handle is ordinary technical logs and search words, as set out above
If you are a parent or carer and think your child has sent us personal information, email hello@turkishdictionary.co.uk and we will delete it. If we later add accounts or other features that collect more information, we will assess the impact on children first and update this policy before they go live.
10. Pronunciation audio
Words can be played in three ways, in this order of preference: a human recording, a computer-generated voice, and the speech voice built into your browser.
Recordings from Wikimedia Commons
Some entries have a pronunciation recording made by a volunteer and published on Wikimedia Commons. We do not copy these files to our site. When you press a play button that uses one, your browser downloads the recording directly from Wikimedia's servers (upload.wikimedia.org). Nothing is requested from Wikimedia just by viewing a page: the request happens only when you press play. If you never press play, Wikimedia receives nothing from your visit.
When you do press play, Wikimedia receives your IP address and ordinary browser details (such as your browser type and the address of our page) with the request, as with any website you visit. That happens between your browser and the Wikimedia Foundation, under the Wikimedia Foundation Privacy Policy, and we do not receive or control it. If the recording cannot be loaded, the site plays a generated clip or your browser's voice instead.
Computer-generated voices
For some words we play a clip made in advance with a computer-generated voice. These clips are files in our storage and are served from our own domain, like the rest of the site. Requesting one is an ordinary request to our site and appears in the hosting logs described in section 2. [DEVELOPER: confirm whether the hosting provider passes the visitor's IP address on to the storage provider when it fetches the file, and state it here if so.] Nothing is sent to any speech service when a clip plays.
Your browser's voice
When a word has no stored audio, or a stored recording cannot be played, the play button uses the speech synthesis built into your browser (the Web Speech API). The site does not send the word to any speech service. However, depending on your browser and the voice selected on your device, your browser may itself send the text of the word to the browser maker's online speech service (for example, some Google voices in Chrome work this way). That happens between your browser and its maker, under their privacy policy, and we do not receive or control it.
To avoid this, choose an offline or local voice in your device or browser settings, or do not use the play button. Pronunciation is optional and the rest of the site works without it. The audio features set no cookies and store nothing on your device.
11. Machine translation of phrases and sentences, and the bot check
Translation by Google
If your search is a phrase or sentence (several words that are not a single dictionary entry), the page shows a machine translation, labelled as such. To make it, our server sends the text you searched for, and the two languages, to Google Cloud Translation. We send nothing else: no account (there are none), no name, no email address and no IP address of yours. Google's handling of that text is described in the Google Cloud Privacy Notice. The dictionary entries for the individual words come from our own database, not from Google.
Because your text goes to Google, please do not put personal information into a phrase you search for. Machine translations can be wrong and are not a substitute for a professional translation. Single words never go to Google.
We keep each translation (the source text, the translation, and the time it was last used) so the next visitor who searches for the same text does not cause another request. The saved text is not linked to you, is never shown as a dictionary entry and is not published or indexed.
Limits and the bot check
Translating costs money for every request, so:
- the number of new translations one visitor can start per minute and per day is limited. A visitor is recognised only by the request-counter key described in section 2;
- the total amount of text translated per day and per month is capped, and when a cap is reached the translation is switched off for a while and the dictionary results continue to work;
- before a new translation (never for one that is already saved), the site may ask Cloudflare Turnstile to check that you are a person and not an automated program. It is loaded only at that moment, not on ordinary page views. Cloudflare's script runs in your browser, so Cloudflare receives your IP address and signals about your browser and device to make that decision, as the Turnstile Privacy Addendum and Cloudflare Privacy Policy describe. Cloudflare says Turnstile processes only the data strictly necessary for this security function and does not access your form entries. Our server then sends Cloudflare the one-time result code your browser received, to confirm it, and nothing else.
Machine translation and the bot check are not used for marketing, profiling or decisions about you.
[DEVELOPER: with the real Turnstile keys configured, load a phrase search in a clean browser profile and check DevTools (Application and Network tabs) for any cookie or storage Cloudflare sets, then make the Cookie and Storage Policy (section 4) match what you see. Confirm the processor terms accepted for Google Cloud and for Cloudflare, and record them in the checklist above.]
12. Voice search
Voice search is optional: you can always type instead. Your browser asks for your permission before the site can use the microphone, and the microphone is used only while the button shows that it is listening (tap it again to stop; it also stops by itself after a pause, and on-device recordings stop after at most 8 seconds). You can withdraw the permission at any time in your browser's site settings.
There are two ways the site turns speech into text. Which one is used depends on your browser, not on a choice we make about you.
Your browser's speech recognition
Where the browser has speech recognition built in (the Web Speech API, for example in Chrome, Edge, Safari and Samsung Internet), the site asks the browser to listen and receives only the recognised text. The site does not receive, store or send the audio. However, some browsers send the audio of what you say to their maker's online speech service to recognise it: for example, Chrome sends it to Google, and other browsers may send it to their maker or recognise it on your device. That happens between your browser and its maker, under the maker's privacy policy, and we do not receive or control it. [DEVELOPER: before publication, check the current documentation of Chrome, Edge and Safari and keep the examples above accurate.]
If you do not want your browser maker to process your voice, do not use the microphone button in that browser, or use a browser without built-in speech recognition (such as Firefox), where the site uses the on-device recognition described next.
On-device recognition
In browsers without built-in speech recognition (such as Firefox), or when the browser's speech service is unavailable and you tap the microphone again, the site uses a speech recognition model (OpenAI Whisper) that runs entirely inside your browser, on your device. The audio is recorded for at most 8 seconds, kept only in your browser's memory while it is turned into text, and then discarded. The audio never leaves your device, and only the recognised text is searched.
The first time you use it, your browser downloads the model once (about 58 MB; about 72 MB on devices that can use the graphics processor). The model files are part of the website itself and are served by our hosting provider like any page (not from our database, our storage or any other company), so the download is an ordinary request to our site and appears in the hosting logs described in section 2; nothing is requested from any other company. The files are kept in your browser's storage so later voice searches do not download them again (see our Cookie and Storage Policy). They contain no information about you.
Voice search is not used for marketing or profiling, and we do not use your voice to identify you.
13. Links to other sites
Entry pages link to sources such as Wiktionary, Tatoeba and Wikimedia Commons for attribution. Those sites have their own privacy policies and we are not responsible for them.
14. Security
We use reasonable technical measures to protect the site and the limited information we handle, including encrypted connections (HTTPS). No system is perfectly secure. [OWNER/DEVELOPER: confirm HTTPS-only and security headers are live before publishing this statement.]
15. Changes to this policy
If we change how we use personal information (for example, if we add accounts, advertising or analytics), we will update this policy before the change goes live and change the "Last updated" date. Significant changes will be highlighted on the site.
16. Contact
OXDPR LIMITED, London, United Kingdom Email: hello@turkishdictionary.co.uk
17. Advertising (Google AdSense)
The site shows ads from Google AdSense to keep the dictionary free. Google's advertising code, and Google's consent message, load on every page from Google's servers, so Google receives your IP address and browser and device details when you view a page.
- Your choice. On your first visit, Google's consent message (a Google-certified consent tool) asks whether you agree to advertising cookies and, separately, to personalised ads. Until you choose, and if you decline, Google is told that no consent has been given: it sets no advertising cookies and shows only limited, non-personalised ads. You can change your choice at any time from the privacy and cookie settings link that the message adds to the page.
- If you agree, Google and its partners may use cookies and similar identifiers to show and measure ads, limit repeats, prevent fraud and, if you allow it, personalise ads based on your activity on this and other sites.
- Who is responsible. For this advertising Google acts as an independent controller under its own privacy policy (policies.google.com/privacy); see how Google uses information from sites that use its services at policies.google.com/technologies/partner-sites and manage ad personalisation at adssettings.google.com. Our lawful basis for allowing advertising cookies is your consent (PECR reg. 6 and UK GDPR art. 6(1)(a)); for showing non-personalised ads it is our legitimate interest in funding the free site (art. 6(1)(f)).
- Transfers. Google may process this information outside the UK, under its own transfer safeguards.
We do not receive your identity from Google; we receive only total ad earnings and anonymous statistics. [SOLICITOR: confirm the controller relationship under current Google ads controller terms, the lawful bases above, and the Children's code position.]
Version history
| Date | Change |
|---|---|
| [OWNER: date on publication] | First published (Phase 2) |
| [OWNER: date on publication] | Added Google AdSense advertising and Google's consent message (section 17) |
| [OWNER: date on publication] | Added machine translation of phrases (Google Cloud Translation), saved translations, request-counter keys and the Turnstile bot check (section 11) |
| [OWNER: date on publication] | Added voice search: the browser's speech recognition and on-device recognition, with the one-time download of the speech model from our site (section 12) |