Privacy policy

Last updated: 10 October 2026.

Sight is published by TAPTAKE BİLİŞİM TEKNOLOJİ SATIŞ HİZMETLERİ YAZILIM SANAYİ TİCARET ANONİM ŞİRKETİ (TAPTAKE BİLİŞİM), the data controller for your personal data. Questions, requests and complaints: info@usesight.app.

This policy tells you what happens to your data. It is not a contract, and you are not asked to agree to it. It is published in English and in Turkish with the same content, and for people in Turkey the Turkish text (Gizlilik Politikası ve Aydınlatma Metni) is the reference version.

The short version

Sight does not record what you browse. There is no history, no list of pages visited, no analytics, no advertising, and no third party receives anything about you from the app except the mail provider that delivers messages you asked for, the app store the app was installed from, and, where the operator serves the block lists through a content network, that network. It is sent no token and no identifier: it sees an address asking for a file, the way any download does.

The websites you open are a different matter, as they are in any browser. They see what you ask them for, and anything you choose to give them: a file or a photo you upload, or, if you allow it, your location, camera or microphone. That goes from your phone to that website, and Sight's server sees none of it.

What leaves your phone for Sight's server is the small amount needed to make a waiting period survive a reinstall, and the email addresses of the people you chose to be told when you ask to turn filtering off, with the app's language for the messages to them.

If you subscribe where we are the seller, Turkey among them, Google also gives us a record of the order, which we keep for our books and share only with our accountant and, when the law requires it, the tax authority. What is in it is set out under If you subscribe.

What the app sends to Sight

A device identifier. Android's ANDROID_ID, specific to this phone and to this app's signing key, or on iOS an identifier created for this installation and kept in the device's keychain. It is sent so a waiting period can be held against something that survives the app's data being cleared. Without it, reinstalling would end a wait, and the wait is the point.

How long your device thinks a wait has left. A duration in milliseconds. Never a date, never a time of day. The countdown deliberately never reads a clock, so there is no clock reading to send.

Email addresses you enter, if you choose to name anyone. At most three. With them, the language the app is in, so the messages to them are written in it.

A token this device was issued, on each request, so the server can tell your device from someone else's.

Your IP address is visible to the server, as it is to every server you connect to. It is used to limit how often the same address can register a device or save a list of people to tell, and it is not written down. The reverse proxy in front of the server keeps its own access log, which is ordinary for any web server and is described at the end of this page.

What the app never sends to Sight

Words typed in the address bar that are not a web address are searched on DuckDuckGo, the way any page you open is visited: the request goes from your phone to DuckDuckGo, and Sight's server sees none of it.

Photographs are examined on your phone. The model that examines them is downloaded to the device and runs there. The filter uploads no image and no score for an image, and writes neither to storage. A photo you choose to upload to a website, or a picture you choose to download, is yours to send or to keep, and the next section says what happens to it.

What a website can be given

A website can ask for your location, your camera or your microphone, the way it can in any browser, and nothing is passed unless you allow it for that site and that request. You are asked each time, with the site named: on Android by Sight itself, and on iOS by the web view Sight is built on. The phone also asks, the first time, whether Sight may use them at all, and keeps that answer in its own settings. What you allow goes from your phone straight to that one website, and Sight's server sees none of it. The answer you give for a site is not remembered, because a list of the sites you allowed would be a list of the sites you visited.

To upload a file, you choose it in the phone's own picker, and it goes from your phone to the website you chose it for. Sight passes it on without looking inside it and keeps no copy. A photo or video you take with the camera for a page goes the same way.

A file you download is saved where you choose, in the phone's own save dialog, and Sight keeps no copy of it and no list of downloads. It meets the same refusals as a page: a download is refused where a page at its address would be, and so is one that passes through such an address on the way. While the photo and video filter is on, a picture or video saved from a page on Instagram or TikTok is judged before it is saved, and one the filter would withhold on screen, or one it cannot judge, is not saved. Anywhere else, a picture or video is saved as it would be shown, because the filter judges pictures and video on those two sites only. Once a saved file is opened in another app, what is inside it is that app's to show, and Sight does not filter it.

What a website does with anything you gave it is covered by that website's own policy, not by this one.

If you subscribe

The store takes the payment and holds the payment details. We never see a card number.

Who sells the subscription depends on the country of your Google Play account. Where Google sells it in its own name, as it does in the European Union, we receive the order with the country it was made in and the model of the device it was made on, and nothing that names the buyer. In Turkey, and wherever else Google does not, we are the seller and Google takes the payment for us. Google then keeps a record of each order for us in its Play Console: the order number, the product, the price and the tax, the date, the model of the device, and the buyer's country, state or province, city and postal code, and, where Google's terms allow it, the name and email address of the Google account. We use that record only to keep our books and pay tax as the law requires, and to answer a cancellation, a refund request or a complaint about that order (KVKK article 5(2)(ç) and (c), GDPR article 6(1)(c) and (b)). It is kept for ten years, the period the Turkish Commercial Code sets for commercial records, and is shared only with our accountant and, when the law requires it, with the tax authority. If you write to us about an order, your message is kept with it.

The app asks the store three things every time the app is opened or comes back to the front, again when the Premium screen opens, and after a purchase attempt that did not go through: whether this installation has a subscription; the country of the Google Play account, which decides who sells the subscription and whether the Turkish pre-purchase information is shown; and the subscription's price and offers, which Google Play lists only as this account can still take them, so they show whether the account can still have the free trial. It asks whether or not you have a subscription, because that is how it finds out, so the store knows the app ran even if you never buy anything. What the store does with that is covered by the store's own privacy policy, not by this one.

What the app receives back is those answers. Whether there is a subscription is kept on the phone; the country, the price and the offers are held only while the app is open, except the offer you confirm after the Turkish pre-purchase information, which is kept as set out under What is kept on your phone. Apart from Google Play's token for each purchase, which the app uses to acknowledge it, as Google Play requires, and to tell a new purchase from one already there, nothing else is read from them. When you subscribe from inside the app after the Turkish pre-purchase information was shown, the app also reads the order number and time Google Play reports, only to put them into the copy of the contract it hands you. No purchase, no receipt and no subscription state reaches the Sight server, which has no column for it, so the server cannot tell a subscriber from anyone else, and nothing we hold connects an order to a device or to anybody's list.

The store's own handling of the purchase is governed by the store's privacy policy, which is a document we neither write nor control.

What is kept on your phone

On Android, Sight keeps cookies and site storage like any browser, because no site can be logged into without them. On iOS the web view uses a non-persistent store, so neither is written to disk and a login does not outlive the session.

It does not keep a cache of the images and video it filters. That cache existed and was removed: the media it held was from the sites being filtered, which is precisely the content that may be withheld, and keeping a recoverable copy of a picture the filter refused to show is not filtering. The cost is that scrolling back re-downloads. A download is held to the same rule for the same reason: saving a picture the filter would withhold is that copy by another route, so it is not saved.

The sites and words you add to your own lists are kept on your phone and nowhere else. They are never sent to the server, never included in a notification, and never read by anything but the filter on the device. What a person chose to keep away from themselves is theirs.

Files you download are kept where you saved them, and deleting them is yours to do; Sight keeps no list of them. On Android, a photo or video taken with the camera for a page's upload button is held in Sight's own private storage and deleted when the browser is closed, or the next time Sight opens if the phone closed it first. Which sites you allowed to use your location, camera or microphone is not kept at all: each answer lasts for the request it was given to.

Which version of the terms you accepted, and whether the Turkish or the English text, is kept on your phone, so the app can ask again when they change. It is not sent anywhere.

Whether this installation has a subscription is kept on your phone, with when Google Play last confirmed it and whether the photo and video filtering is still kept on after Premium ended. When the Turkish pre-purchase information was shown and you tap through to Google Play, the price, the period and any free trial you confirmed, the time of the tap, and Google Play's tokens for any subscription the account already had and for a purchase still pending, are kept on your phone. If a purchase follows, its order number and time are kept with them until you close the dialog that hands you the copy of the contract, so that a phone that closed the app first still shows it. If none follows, they are replaced at your next tap through to Google Play, or deleted the first time the app opens after seven days. None of this is sent anywhere.

No browsing history is kept anywhere, by design and from the first version.

What the server stores

WhatWhyHow long
Device identifierSo a wait survives a reinstall Until you ask for it to be deleted
When a wait endsThe wait itself Cleared when the wait ends or is cancelled
A SHA-256 hash of the device's token Authentication. The token itself is never stored, so a copy of the database yields no working credentials Until replaced or deleted
Email addresses you entered Asking the recipient whether they agree, and sending the messages you asked for once they do Until you remove them, or until the recipient does
Whether the recipient agreed, and when So nothing is sent to somebody who has not, and so somebody who already agreed is not asked again when you list them a second time Until they remove themselves, or until you ask for your data to be deleted
A random secret per address So the recipient can agree, and can remove themselves, without involving you Kept with the agreement above, and deleted with it
The app's language, with each address So the messages to that address, and the pages they link to, are in the language you use Deleted with the address
Addresses that have been asked once So the same address is never invited twice, however many times a list is saved Kept until they ask for it to be deleted
Addresses that removed themselves So nothing is ever sent to them again, whoever lists them Kept until they ask for it to be deleted
Delivery records: address, event, time, attempts, last error Retrying a failure, and giving up on one that will never succeed 12 months, deleted by the server itself

Nothing here is shared, sold, or used to build a profile.

On what basis. The device identifier, when a wait ends and the token's hash are processed because the service you accepted cannot work without them (KVKK article 5(2)(c), GDPR article 6(1)(b)). An address you entered is used for the one invitation, and the lists of addresses asked once and of addresses that removed themselves, and the delivery records, are kept so that nobody is asked twice or written to after saying no; that is our legitimate interest in running the service without harming anybody it writes to (KVKK article 5(2)(f), GDPR article 6(1)(f)). Every message after the invitation is sent on the explicit consent of the person who receives it (KVKK article 5(1), GDPR article 6(1)(a)), which they can withdraw from any message.

Your IP address is not stored. Three things are rate limited, because each of them can be used to send mail to people: registering a device, saving the list of people to tell, and starting or cancelling a wait. The first two count by IP address. The third counts by the token your device was issued, and falls back to the IP address only for a request that arrives without one. Each counter is held in memory for as long as its own window lasts, a minute for registration and an hour for the other two, and none of them is written to the database or to a log. The server's own log records the status, method and path of a request and nothing that identifies who made it.

The machine in front of the server is a separate matter and an honest policy has to say so: a reverse proxy keeps its own access log, which does contain IP addresses, and how long it keeps them is set by whoever runs it rather than by this application. That is a question for the operator named at the top of this page.

The people you name

Read this part carefully, because it concerns somebody who is not you.

If you enter someone's email address, we send one invitation asking whether they agree. If they do, we send them a short message when you ask to turn filtering off, another if you change your mind, and another if the app is removed and put back while a wait is running. The message says that someone who asked them to know has done so. It never names a site, a category, or anything you looked at.

They did not sign up for this. You typed their address. So:

They are asked first, once. The only message that reaches a new address is an invitation: it explains that somebody listed them, what they would receive, and how to agree. Nothing else is sent unless they open the link and say yes.

Silence is a refusal. No reminder follows an invitation that goes unanswered, and nothing further is ever sent to that address. In the app you can see who has agreed and who has not, so you know whether anyone would actually be told.

Every message can end it. Each carries a link, including the invitation itself. It opens a page with a single button, and pressing that button removes the address. Opening the link alone changes nothing, deliberately: mail gateways follow every link in a message to scan it, and a link that acted on being opened would have them deciding on the recipient's behalf. Nothing else is asked: no account, no reply, and you are not asked and not told. Their mail client will also show its own unsubscribe button, because the messages carry the standard header for it.

Removal is immediate and final. The address and its secret are deleted, and any message still queued to them is dropped rather than sent. Nothing is ever sent to that address again, by you or by anyone else.

Somebody can still type it into the form afterwards, and it will sit in their list looking exactly like an address that was asked and never answered. That is deliberate. Refusing to store it told the person who typed it that their save had failed, and it turned the reply into an answer to "has this address refused Sight?" for anyone who cared to ask. Listed and silent gives away nothing and delivers nothing.

Ask them first. It is their inbox, and the terms require it.

Children

Sight is for adults setting limits on themselves. You must be 18 or older. It is not a parental control product, not a monitoring product, and it is not directed at children.

Your rights

Under the KVKK and the GDPR, about your device, about your order if you subscribed where we are the seller, or, if somebody listed you, about your email address, you may: learn whether data about you is processed, and ask for information about it; learn why it is processed and whether it is used for that; know which third parties in Turkey or abroad receive it; ask for it to be corrected, or deleted or destroyed, and for those third parties to be told; object to a result against you that comes solely from automated analysis; claim compensation for damage caused by processing it unlawfully; and ask for a copy. Write to info@usesight.app and we will answer within 30 days.

Deleting your data ends any waiting period recorded on the server.

Uninstalling the app does not delete the server's record. That is deliberate: a record that disappeared when you uninstalled would make uninstalling the way around the product you chose to use. Ask, and it is deleted.

If you believe we have handled your data unlawfully, write to us first. If we refuse, our answer is inadequate, or we do not answer within 30 days, you may complain to the Turkish Personal Data Protection Board within 30 days of our answer, and at most 60 days after you wrote (KVKK article 14). In the EU you may complain to your national supervisory authority.

Where it is processed

Servers in the United States, at a hosting provider working for the publisher. What is processed there is only what the table above lists, and it travels over TLS. The order records of the subscriptions we sell are held by Google in its Play Console, and in our accounting records.

Changes

Material changes are published on usesight.app, and the date at the top of this page says when it last changed.


Decisions taken, and the risk that remains

Written down so that the reasoning survives the person who made it.

The recipients of notifications ask for their own consent. They are third parties whose address was supplied by someone else, so the only message that reaches them before they have agreed to anything is the invitation, and it is sent on legitimate interest: one message, to ask, with a way to agree and a way to refuse in the same email.

Everything after that runs on the recipient's own consent, recorded against their address with the time they gave it. Silence is a refusal and there is no reminder. That closes the question this document previously left open, at the cost the earlier draft predicted: a user can list somebody who never answers, and then nobody is told. The app shows who has agreed, so that cost is visible rather than discovered.

What remains is ordinary. The invitation itself is unsolicited mail to somebody who did not ask for it, justified by being a single message that exists only to ask. It carries the standard unsubscribe header, refusing is one click, and a refusal is permanent and applies to every user, not only the one who listed them.

Websites can be given what they ask for. Refusing every camera, microphone and location request, every upload and every download did not make Sight stricter. It made it a browser that cannot join a video call or attach a file to a form, and the person who needs either opens another browser, which is the way around the limit Sight exists to keep. So location, the camera and the microphone reach a website only when the user allows them, and a file only when the user chooses it, one website and one request at a time, and none of it reaches the server. No answer is remembered, because a list of the sites a user allowed would be a list of the sites they visited, and this policy says there is no such list. A download is held to the same refusals as a page, because a file is a page that stays. What remains is ordinary for any browser: a website holds what it was given under its own terms, and a saved file is outside the filter once another app opens it.

Retention periods are chosen, not derived, except the ten years for order records, which the Turkish Commercial Code sets. Twelve months for delivery records, so that "was this person ever told" can be answered for a plausible period, and the server deletes them itself.

The application keeps no log of its own. It writes to standard output, which carries counts and row identifiers and no address or device identifier, so there is nothing there to set a period on. What the machine running it does with that output, and what the reverse proxy keeps in its own access log, is the operator's, and is described above.

Eighteen rather than sixteen, because the subject matter is adult content and the product is a self-control tool, not because of any consent threshold.

Sight Terms of Service Türkçe

a Taptake product

© 2026 Taptake. All rights reserved.