Privacy
Desktop organization and search run on your PC. Picketdesk needs no account and sends nothing on its own: the one thing it can send is a crash report, only with your consent, and a report is built to leave out your file names, folders and picket titles (see Crash reports).
Publisher and contact
NOMIKOSI SYMVOULEFTIKES YPIRESIES L.P., trading as NOMIKOSI CONSULTING, a Greek limited partnership (Ε.Ε.). Registered Greek name: ΝΟΜΙΚΟΣΙ ΣΥΜΒΟΥΛΕΥΤΙΚΕΣ ΥΠΗΡΕΣΙΕΣ Ε.Ε. Address: ΘΕΡΜΟΠΥΛΩΝ 3, ΣΠΑΤΩΝ - ΑΡΤΕΜΙΔΟΣ / ΑΝΑΤΟΛΙΚΗΣ ΑΤΤΙΚΗΣ, 19004, GREECE. VAT: EL802065339. GEMI: 169243201000. Tax office (DOY): PALLINIS. For support or privacy requests, contact support@picketdesk.com.
Desktop files and search
Your workspace, search index and OCR cache are stored locally. Picketdesk sends none of them anywhere: there is no licence check or activation, no telemetry and no advertising, and a support e-mail reaches us only when you send one. A folder you choose for configuration sync is handled by the storage provider you use.
Crash reports
When Picketdesk stops unexpectedly or runs into an internal error, it keeps a crash report on your PC. A report says where in Picketdesk's own code the problem happened: whether Picketdesk stopped or ran into an internal error, the version of the report format, the version and build of Picketdesk, the version of Windows, the processor type Picketdesk was built for, the time to the minute, how long Picketdesk had been running, the program thread, the place in the source code, the error message, the Windows error code when Windows ended Picketdesk with one, and the program's position as program file names and offsets, with an identifier for the report. No field of a report holds your workspace or a log. The error message is the one place where text from your desktop could appear: before keeping it, Picketdesk takes out quoted text, file paths, e-mail addresses and the user and computer names it recognises. A report is built to leave out file names, folders and picket titles, but Picketdesk cannot guarantee to recognise every one, so Settings → Crash reports shows each report exactly as it would be sent, for you to check before you send it.
A report is sent only with your consent. By default Picketdesk asks when it next starts; in Settings you can instead send reports without being asked, or never keep them, and send or delete any report yourself. A copy of Picketdesk built without a crash-report service never asks and cannot send: its reports stay on your PC. An unsent report stays on your PC until you delete it; once it is 90 days old, Picketdesk deletes it the next time it starts or writes a report, and it keeps only the 20 most recent. A sent report goes over an encrypted connection to a database Supabase hosts for us in the European Union, with no account and nothing added to identify you. Like any connection it reaches Supabase with your IP address, which is not stored with the report; Supabase's request logs record that address, the approximate location derived from it and the program's name; on the Supabase plan we use, they are kept for one day. To keep one sender from using up the service, we count the reports we accept from each connecting address (for IPv6, its /64 network) under a salted hash, and delete those counts within three hours. We keep a report for a year, delete it within the hour after that, and use it only to find and fix defects. Because a report is built not to name you, we cannot pick out yours on our own; if you give us a report's identifier, we will find and delete that report. Settings → Crash reports shows the identifier with the report before it is sent, and Picketdesk's log (picket.log) records it, as part of the report's file name, when Picketdesk keeps a report.
Update e-mails
If you ask for them on our website, or through the link in Picketdesk that opens it, we e-mail you when a new version of Picketdesk is out. We keep your e-mail address as you typed it, where you gave it (the website or the app's link), which version of the sign-up wording you agreed to, when you asked, how many times you asked before you confirmed, when you confirmed, and which update e-mails we sent you. Each confirmation or already-on-list e-mail waits in a private queue until it is sent, so that it can be tried again if delivery fails; we stop retrying 23 hours after you asked, and remove the queued e-mail when it is delivered, when you confirm or unsubscribe, and otherwise within the hour after it is 24 hours old. Pending announcement attempts separately keep the announcement identifier, recipient address, number and timing of attempts, retry timing and a redacted failure reason. We stop retrying 23 hours after the first attempt. If we cannot tell whether the e-mail reached you, the record stays for review until a successful send is recorded or you unsubscribe; 31 days after the first attempt, when the e-mail provider's own record of the send is gone, we delete the attempt's copy of your address and its failure reason, and keep only which announcement it was and when it was tried, so that announcement is never sent to you twice. Nothing is sent to you until you confirm from the e-mail we send, and a request you do not confirm is deleted within the hour after it is 7 days old. Every update e-mail has a link that stops them; using it deletes your address, the record of what we sent to it, and any pending messages or announcement attempts from the list straight away. If you ask for update e-mails by writing to us instead, we treat your message as a support e-mail: we do not put your address on the list ourselves, but reply with the link to the sign-up form, where you confirm as above.
The e-mails are plain text and report nothing back: we do not track whether you open them or which links you follow. To keep the sign-up from being misused, we count requests per connecting address (for IPv6, its /64 network) and per inbox under a salted hash, and keep those counts for about two days. Supabase runs each sign-up, confirmation and unsubscribe request in its data centre nearest you and stores the list for us in the European Union; its request logs record the IP address, approximate location and browser of each sign-up, confirmation and unsubscribe request, and on our plan keep them for one day. Resend sends the e-mails. It keeps each e-mail it sends for us, with its delivery record, for 30 days, and if an e-mail to an address bounces or is marked as spam, it keeps that address on its block list until we remove it.
Support e-mails
When you write to support@picketdesk.com, we receive your e-mail address, your message and the attachments you choose to send. The logs and workspaces that tray → Export logs… writes can include file and folder names, notes, reminders and configured commands, and nothing in them is redacted: read them before you attach them.
We keep a report and its attachments while we handle it, then remove personal attachments. Nothing is deleted automatically, so write to support@picketdesk.com to have yours removed sooner.
Visiting this website
Cloudflare, Inc. serves this website for us. Like any web server, it receives what a browser sends with each request, such as your IP address, your browser's user agent and the address of the page or file you ask for, and uses it to deliver the site and protect it from attacks. We rely on our legitimate interest in running a secure website, under Article 6(1)(f) GDPR. Our pages set no cookies and run no analytics or advertising scripts. Cloudflare's security analytics show us a sample of these requests, with the IP address, user agent and address requested, for the last 31 days; we set up no export of request logs and keep none ourselves. Cloudflare also uses traffic data to protect its own network; for that purpose Cloudflare decides how the data is used, as a separate controller, and keeps it for as long as that purpose requires under its own privacy policy, which states no fixed period.
Where the data is processed
Supabase hosts the crash reports you send and the update e-mail list, in a data-centre region in the European Union. Supabase Pte. Ltd., a Singapore company, processes this data for us under a data processing agreement. Where it or one of its sub-processors accesses the data from outside the European Economic Area, the transfer is covered by the European Commission's standard contractual clauses in that agreement. Plus Five Five, Inc. (Resend), a United States company, sends the update e-mails for us under a data processing agreement; it is certified under the EU-U.S. Data Privacy Framework, and the agreement's standard contractual clauses also cover the transfer. Cloudflare, Inc., a United States company, serves this website for us under a data processing agreement; it is certified under the EU-U.S. Data Privacy Framework, on which the transfer relies, and the standard contractual clauses in that agreement apply if that certification lapses. Support e-mails are kept in our support mailbox, which our e-mail provider hosts for us. If the Picketdesk business passes to another company (clause 21.4 of the licence agreement), this data passes with it, and that company is bound by this notice; we announce such a transfer at least 30 days ahead. You can ask us at support@picketdesk.com for a copy of the standard contractual clauses these transfers rely on.
Why we process service information
- Requested support: your message, your e-mail address and the attachments you send are used to handle your request, on the contractual basis in Article 6(1)(b) GDPR. Please avoid including unrelated personal information.
- Crash reports: sent and used to find and fix defects only with your consent, under Article 6(1)(a) GDPR; you can take it back at any time in Settings → Crash reports.
- Update e-mails: your address is used only to tell you about new versions of Picketdesk, with your consent, under Article 6(1)(a) GDPR; you can take it back at any time with the link in any update e-mail, or by writing to us.
- Security, abuse prevention and defect investigation: the counts that keep the crash-report and update e-mail services from being misused, the website's request records, and the details you send to support are processed for our legitimate interests in protecting the service and correcting faults, under Article 6(1)(f), subject to necessity, balancing and your right to object. The contents of a crash report are used only with your consent (above).
We need your e-mail address to answer you; without it, we cannot reply. Using Picketdesk does not require an account. Accepting the licence agreement is not consent to unrelated processing or marketing.
Retention criteria
These criteria say how long each kind of record is kept.
- Crash reports: a year after they arrive, deleted within the hour after that; the counts per connecting address, at most three hours; an unsent report is deleted from your PC once it is 90 days old, the next time Picketdesk starts or writes a report.
- Update e-mails: your address and successful-send records until you stop them; queued confirmation and already-on-list e-mails until delivery, confirmation or unsubscribe, otherwise within the hour after 24 hours; pending announcement attempts, including review holds after 23 hours, until a successful send is recorded or you unsubscribe, except that a hold's address and failure reason are deleted 31 days after its first attempt and only the announcement and attempt times stay until you unsubscribe; a request you do not confirm, 7 days, deleted within the hour after that; the sign-up counters, about two days; Resend's copy of each e-mail sent, 30 days.
- Support e-mails and attachments: kept while handling the report and related defect investigation. When that work ends, remove personal attachments and identifying details unless specific records are needed for an unresolved dispute or legal duty. A de-identified technical explanation may remain for regression prevention.
Our providers keep their own records for limited periods: on the Supabase plan we use, its request and database logs are kept for one day and no database backups are included; Cloudflare's security analytics show us sampled website requests for the last 31 days; Resend keeps the update e-mails it sends, with their delivery records, for 30 days. Cloudflare also keeps traffic data for its own network security under its own privacy policy. A deletion we make therefore reaches these records only when their period ends, and we do not promise immediate erasure from them.
Privacy requests
For access, correction, deletion or another privacy request, contact support@picketdesk.com. We may need enough information to verify which messages or which update e-mail subscription are yours; never send a password.
Applicable rights can include access, correction, erasure, restriction, portability and objection. You may complain to the Hellenic Data Protection Authority (Αρχή Προστασίας Δεδομένων Προσωπικού Χαρακτήρα), Kifissias 1-3, 115 23 Athens, www.dpa.gr, or to the data protection authority where you live. See the European Commission's explanation of your data rights.