Privacy Policy

Effective 2026-09-26 · EKIIRA, 3/4, APC Park, Kolkata-700086, WB, India · Privacy contact: ekiira.business@gmail.com

In short. Pinner is built so that we do not hold your data. There are no accounts, no analytics, no advertising and no tracking. Your pins, images, projects, clients and talent details stay on your devices, and travel only where you send them: your own paired devices on your own network, or a cloud folder you choose. The only server we run is a small licence service, and it receives only what is needed to sell and check Pinner Pro — a licence key (kept only as a hash), a random device id and the name you gave the device. This policy explains exactly what that is.

1. Who is responsible for what

1.1 For the licence service (§4) we, EKIIRA, are the controller of the personal data described there.

1.2 For everything you put into the apps — pins, page addresses and titles, notes, albums, projects, clients, talent and casting records, shoot locations, boards, documents — you decide why and how it is used, so you are the controller (or processor for your client). We have no access to it, do not process it on your behalf, and cannot see, export, correct or delete it. If you keep other people's personal data in Pinner (§7), your legal duties toward those people are yours.

1.3 India's DPDP Act. Because the Software operates locally and we have no access to Your Content, we are not a "Data Fiduciary" under the Digital Personal Data Protection Act, 2023 (DPDP Act) for the personal data you keep in the apps. You are the data fiduciary for any third-party personal data you process using the Software.

2. What stays on your devices

The apps store their data locally, in files and databases on your computer, phone or browser profile:

Secrets (cloud sign-in tokens, the bridge pairing token, the licence key and the encryption key) are protected on each device: with Windows DPAPI on the computer, in the Android Keystore on the phone, and in the extension's private storage inside your browser profile (which web pages cannot read). They never come to us.

3. What you send between your own devices

4. What we receive: the licence service

The licence service exists only to sell Pinner Pro and to check that a key is valid. It runs on Cloudflare's network. It is used only when you buy, activate, refresh, release a device, or open the billing page.

4.1 What is sent to it, and stored:

4.2 What we do not receive: your name, email address or payment details (Dodo Payments collects those, §5.2); any pin, image, project, client, talent, shoot, location or note; your cloud accounts or tokens; your contacts; analytics or usage data.

4.3 Network data. As with any web service, your IP address and the request are visible to Cloudflare while it delivers the request. We do not store IP addresses or use them for tracking; Cloudflare's own handling is described in its privacy notice.

4.4 Why, and on what legal basis (for people in the EU/EEA/UK): to perform the licence contract with you (Art. 6(1)(b) GDPR) and, for keeping the activation limit fair and preventing fraud and key sharing, our legitimate interest (Art. 6(1)(f)).

4.5 How long. A licence register is kept while the licence is in use. A register that has seen no activity for twenty-four (24) months is deleted automatically. You can release a device at any time in the app, which removes its entry from the register.

4.6 The web pages of the licence service (the plans page and the "thank you" page) set no cookies and load no third-party scripts, fonts or analytics. After a purchase Dodo Payments sends you back to the "thank you" page with your licence key in the address, so that it can show you the key; that address is visible to your browser and, transiently, to Cloudflare.

4.7 This website. The public website (https://ekiira.com/pinner/) sets no cookies and loads no third-party fonts, images or analytics. Its pages run one small script of our own, for the menu, the screenshot tour and the alpha application form. What you send through that form is covered by the website's own Privacy Policy.

5. Other services you choose to use

5.1 Cloud folders. If you connect one, the apps talk to that provider from your device, using the provider's own sign-in:

5.1.1 The sign-in service. "Sign in with Google Drive / Dropbox / OneDrive" goes through a small Cloudflare Worker that we run (cloud-auth). It exists for one reason: the providers require an app secret to turn a sign-in into a token, and that secret must not be shipped inside apps that anyone can take apart. When you sign in, or when a sign-in has to be renewed (about once an hour), the app sends the one-time sign-in code or the renewal token to this service, which adds the app secret, passes the request to the provider, and hands the provider's answer straight back to your device. Tokens pass through the service's memory only: it has no database, stores nothing, and does not log tokens, account names or file names. It never sees your files, folder contents or library, because your devices talk to the provider directly for those. Cloudflare, which hosts it, sees the network address of the device making the request, as any web host does. You can avoid the service altogether by using a synced folder, WebDAV, or your own developer app under Settings → Connections → Advanced.

The sign-in tokens are stored on your devices only, and a paired computer may hand its sign-in to your paired phone or browser over the encrypted link between them, so you sign in once. What the providers do with your data is governed by their terms and privacy policies.

5.1.2 The proofing relay (optional). If you set up the proofing relay for client galleries (it is off until you enter its address and runs on the Cloudflare account of whoever deployed it, normally your own), it stores only what your clients choose in a gallery you sent them: which pictures or people (known to it by random ids) they chose, their comments, how long they looked at each, when they opened the gallery, and the name and email they typed if the gallery asked for them. It never receives photos, file names or anything else from your library. Everything is deleted a day after the gallery's closing date and never kept more than 180 days; stopping a gallery deletes it at once. For the personal data of your clients that this involves, you are the controller (see section 7): tell your clients that their choices are sent to you this way.

5.2 Payments. Purchases are made on a checkout page run by Dodo Payments, our merchant of record, which collects the buyer's name, email, billing details, tax information and payment method under its own privacy notice, and sends you the receipt and licence key. We never see payment card details.

5.3 Google API Services User Data Policy. Pinner's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data obtained through Google APIs is used only to provide the Google Drive sync feature you turned on; it is not stored by us or transferred to anyone else, not used for advertising, not used to train AI models, and not read by humans. (The sign-in service in 5.1.1 relays your sign-in tokens without keeping them.)

5.3.1 The same applies to data obtained from Dropbox and Microsoft APIs.

5.4 Things the apps fetch when you ask them to. These requests are made from your device to the addresses involved, only when you use the matching feature:

5.5 We do not use advertising or analytics SDKs, cookies for tracking, fingerprinting, or crash-reporting services that send data off your device.

6. The browser extension's permissions

The extension asks for broad access ("all sites") because its job is to let you right-click an image on any website and pin it, to show its album menu on the page, and to add "Mark location for shoot" to Google Maps. It uses that access only to do those things when you ask. It does not read, record or transmit your browsing, forms, passwords or history. Page addresses, titles and images you pin are stored locally. Nothing is sold, rented or shared, and nothing is used for advertising, profiling or credit decisions. The identity permission is used only to run the cloud sign-in you start (Google Drive, Dropbox, OneDrive).

7. Other people's personal data in your library

7.1 Photographers and casting teams store personal data about other people: talent names, contact details, agency, measurements, photos, availability, notes, releases; clients; crew. That data lives only in your library on your devices.

7.2 You are responsible for having a lawful basis to hold it, for informing people as the law requires, for security, for keeping it only as long as needed, and for honouring their rights (access, correction, deletion, objection). Pinner helps: you can search, correct, export (CSV, PDF, ZIP) and permanently delete any record, and deleting an item also deletes it on your other devices when they sync. Images, projects, shoots and profiles can carry a mature-content marker that you can search and filter on. Pinner does not perform facial recognition or any biometric identification.

7.3 Be especially careful with minors' data and with images of nudity: see the Acceptable Use & Copyright Policy.

7.4 Face recognition (optional add-on). If you install and switch on the face recognition add-on, Pinner Studio makes a face print of each face in the photos you choose, on your computer, to find the same person again. Face prints are biometric data in many laws (for example the GDPR and UK GDPR, Illinois' BIPA, Texas and Washington law). They stay in the add-on's own database on your computer: we never receive them, and they are not synced, uploaded or put in backups. You decide whose faces are recognised and are the controller of that processing: get the consent the law requires from the people you recognise (agencies usually do this in the model contract; each person has a consent note), use Only people I add to keep no face print of anyone you have not named, and delete face data when it is no longer needed (Delete all face data, or remove the add-on with its data).

7.5 Auto-tagging (optional add-on). If you install and switch on the auto-tagging add-on, Pinner Studio analyses your photos on your computer to suggest keywords and descriptions. What it computes stays in the add-on's own database on your computer; we never receive it. It is designed never to infer or tag people's racial or ethnic origin, religion, political opinions, sexual orientation, health, age, gender, emotions or appearance, and it rewrites generated descriptions without such words. Tags you create about adult content (nudity, underwear) can be learned and suggested only after you confirm the conditions in the Acceptable Use & Copyright Policy §3.5; they describe what is in an image, not who the person is.

7.6 Mature-content detection (optional add-on). If you switch it on, Pinner Studio compares each photo's image description (the one the auto-tagging add-on already made, on your computer) with a description of adult content, to mark images that may be mature and, if you choose, blur their thumbnails. It stays on your computer and is never sent to us; you can correct every mark, and switching the add-on off keeps your own marks and drops its guesses.

8. Your rights

8.1 About the data we hold (§4). Depending on where you live (for example under the GDPR, the UK GDPR, the California Consumer Privacy Act, India's Digital Personal Data Protection Act, 2023 (DPDP Act) or similar laws) you may have the right to know what we hold, get a copy, have it corrected or deleted, restrict or object to its use, receive it in a portable format, withdraw consent, and complain to your data-protection authority.

8.2 How. Email ekiira.business@gmail.com from any address and include your licence key or the device name and id shown in Settings → Licence. Because the register is keyed by a hash of your licence key, we can only find your entry if you give us the key or a device id; we may ask for proof that you control it. We answer within thirty (30) days (or the shorter period your law requires). Releasing a device in the app removes its entry immediately.

8.3 We do not sell or share personal information (as those terms are used in California law) and do not use it for targeted advertising or automated decisions with legal effects.

8.4 About the data in your apps (§7). Those requests go to you, as controller. If someone contacts us about data they believe is in someone's Pinner library, we can only tell them that we hold no such data and that they should contact the photographer or team concerned.

9. Security

9.1 Transport to the licence service is over HTTPS. Licence tokens are signed (RSA-2048) and checked offline on your device. Keys are stored hashed. Phone links use TLS with pinned certificates. Optional end-to-end encryption uses AES-256-GCM with a key derived by scrypt from your passphrase. Secrets are held in the operating system's protected stores.

9.2 No system is perfectly secure. Protect your devices with a screen lock and disk encryption; use a strong, unique passphrase; and do not share your licence key.

10. International transfers

The licence service runs on Cloudflare's global network, and Dodo Payments processes payments in several countries. Where personal data of people in the EEA or UK is transferred to a country without an adequacy decision, it is protected by standard contractual clauses or an equivalent safeguard used by those providers.

11. Children

Pinner is a professional tool and is not directed to children. We do not knowingly collect personal data from anyone under 16 (or the age set by local law). If you believe a child has provided data to the licence service, contact ekiira.business@gmail.com and we will delete it.

12. Changes

We may update this policy. If the change is material we will say so in the Software and ask you to accept the new version. The effective date above shows when it last changed.

13. Contact

EKIIRA · 3/4, APC Park, Kolkata-700086, WB, India · ekiira.business@gmail.com. If you are in the EEA or UK and are not satisfied with our answer, you may complain to your local data-protection supervisory authority.