Contact
Findy is made by one independent developer. Email is the only support channel, and every message is read — but replies are not instant, and we will not pretend otherwise.
Write in English if you can. There is no phone line, no live chat and no ticket system.
This is a one-person project, not a support department. We do not publish a response time, because we have no honest basis for promising one. Sending the same message repeatedly does not move it up a queue; a clear first message does more.
Before you write
These pages answer most incoming questions, and reading the relevant one is usually faster than waiting for a reply.
Reporting a bug
A bug report is only actionable if it can be reproduced. Include all six of these and the problem is usually fixable; leave them out and the reply will just be a request for them.
| Item | Where to find it |
|---|---|
| iPhone or iPad model | Settings, then General, then About, under Model Name. |
| iOS or iPadOS version | Settings, then General, then About, under Software Version. |
| Findy version | Shown in the app's settings screen. |
| What you did | The exact steps, in order, that lead to the problem. |
| What you expected to happen | One sentence. |
| What actually happened | The wording of any error, and a screenshot if you can. |
Whether it happens every time or occasionally, whether it started after an update, and which permissions you have granted. Findy has no crash reporting and no analytics, so we genuinely cannot see anything you do not tell us.
Reporting an incorrect detection
Errors in both directions are worth reporting: something ordinary labelled showing camera-related indicators, or something you later identified as a real device that Findy left marked Ordinary. Concrete examples are what improve the labelling rules.
- Note which method produced the result — network scanner, Bluetooth, camera tools or magnetic check.
- Copy the evidence Findy listed for the flag, and the label it gave.
- Say what the object actually turned out to be, if you found out.
- Describe the setting: your home, a hotel, a rental, an office, a crowded network.
- Add a screenshot of the result screen where possible.
- Send it to azattgoktas@gmail.com with "incorrect detection" in the subject.
Please remove anything you would not want to share — network names, addresses and device names can identify a place.
Reporting a security issue
If you have found a vulnerability in the app, email azattgoktas@gmail.com with "security" in the subject. Include what you found, how to reproduce it, and what an attacker could do with it.
Please report it privately first and give it a reasonable chance to be fixed before publishing. There is no bug bounty programme, and we will not offer payment — but credit in the changelog is yours if you want it.
"Findy did not find a camera that was there" is a limitation, not a vulnerability — the limitations page lists the cases where that is expected. Report those as incorrect detections instead, using the steps above.
What we cannot help with
- Issuing refunds. Apple processes purchases and handles refunds. How to request one.
- Telling you whether an object is a camera. We cannot see the room, and Findy itself does not make that claim.
- Legal advice about what you may lawfully inspect, remove or record in a property you do not own.
- Emergencies. If you believe you are in danger, contact your local emergency services or the police rather than emailing a developer.
Last reviewed 2026-07-23 · Written and reviewed by the Findy developer.