PilePrompt
Privacy Policy for PilePrompt
Last updated: 2026-11-17
In short. PilePrompt works without an account, and then what you write stays on your device. If you sign in with Google to sync, your projects are stored on our servers so they can follow you across devices and be shared with people you invite. Usage statistics on the web and mobile versions are off unless you allow them. We show no ads, do not sell data, and do not use your content to train any AI model.
1. Who is responsible for your data
PilePrompt is operated by Miguel Angelo da Veiga Soares, an individual based in Portugal, working under the brand BoraDuo ("we", "us"). Miguel Angelo da Veiga Soares is the data controller for the personal data described in this policy. BoraDuo is the name the software is published under; it is not a separate company.
Contact for anything in this policy, including requests about your data: bora.duo.apps@gmail.com. There is no separate data protection officer.
2. What this policy covers
It covers PilePrompt on the web at pileprompt.boraduo.com, the installable mobile web app, the PilePrompt Desktop app for Windows, and the optional sync and sharing features. PilePrompt is a free Beta, with no paid plans, subscriptions or advertising; an optional "Buy me a coffee" link lets you donate voluntarily.
The policy distinguishes five situations, because they involve very different data: using PilePrompt without an account (section 3), optional sync (section 4), shared projects (section 5), optional usage statistics on web and mobile (section 6), and security and operational records (section 7).
3. Using PilePrompt without an account
You can use PilePrompt without signing in. In that case your projects, tasks, notes, instructions and settings are kept only on your device: in your browser's storage on the web and mobile versions, and in the app's own storage on Desktop. They are not sent to us.
- Files. On Desktop you can link a project to a text file on your computer. The file stays on your computer. Backups and exports are files you download yourself.
- Loading the app. The web and mobile versions, and the Desktop app, load PilePrompt's program files from our hosting provider, Cloudflare. As with any website, Cloudflare's network necessarily receives your IP address, your browser's technical details and the address requested, in order to deliver the files and protect the service.
- Storage on your device. PilePrompt uses your browser's local storage (not advertising or tracking cookies) to keep your projects, your settings, your sign-in session and your usage-statistics choice. This storage is needed for the app to work. If you sign in, Google's own sign-in window uses Google's cookies under Google's policies.
4. Optional sync (signing in with Google)
Sync is optional. If you turn it on, you sign in with your Google account through Firebase Authentication, a Google service we use to confirm who you are.
What our own servers receive and store
- Your account identifier — the user ID that Firebase Authentication assigns to your Google sign-in. It is stored with every record you sync, to keep your data separate from everyone else's.
- Your email address — received with each request. We keep it with your account identifier as a record that your account exists, so that other people can invite you by your address and so that an invitation is only ever stored for someone who has an account (section 5). It is also stored with shared projects, invitations, blocks and reports.
- Your content — the projects you sync: their names, sections, tasks, notes and statuses, your Project, Global and Shared Instructions, custom themes, markers for projects you deleted, and the times these were last changed.
Our servers do not receive or store your name, your profile picture or your Google password.
The sign-in record kept by Firebase Authentication
When you first sign in, Firebase Authentication creates a sign-in record for you in our Firebase project. For a Google sign-in this record normally contains your user ID, your email address, the name and profile-picture address from your Google profile, and when the record was created and last used. Firebase Authentication also logs the IP address and browser details of sign-in requests. Google processes this record on our behalf, in the United States. PilePrompt does not display or use your name or picture.
On your device
Your sign-in session is kept in your browser's storage (or the Desktop app's storage) so you stay signed in. Signing out removes it from that device.
5. Shared projects
If you share a project, or someone shares one with you:
- Inviting someone. The owner enters the email address of the person they want to invite and chooses a role. An invitation is created only if that address belongs to someone who already has a PilePrompt account, meaning they have signed in with Google and synced at least once. If it does, we store the address and role with the project, together with the owner's own email address, so that the person invited can see who is inviting them. If it does not, we store nothing: the address is checked and not kept, no invitation is created, and nothing waits for that person to sign up later. The inviter gets the same answer either way. PilePrompt does not tell anyone whether an email address has an account, and it does not show the inviter invitations that have not been accepted. Each account can make a limited number of invitation attempts per day.
- If someone invited you. If you have a PilePrompt account, another user can invite you by typing your email address. We then store your address with their project. In that case we received it from that user. PilePrompt shows you the invitation, with a note about where your address came from and a link to this policy: the inviter's email address, the project's name and the role offered. You choose whether to accept or decline. Until you accept, you cannot see anything else of the project, and nothing is accepted on your behalf. If you do nothing, the invitation is deleted 30 days after it was sent. You can also ask us to remove it. Invitations sent before version 0.9.24, when an address without an account could still be invited, are deleted on the same 30-day rule.
- After you decide. If you accept, you become a collaborator, and we store your user ID, email address, role and the time you joined. If you decline, the invitation is deleted. The inviter is not told.
- Who can see what. Collaborators can see and, depending on their role, edit the content of the shared project, including its Shared Instructions. The project's owner can see the email addresses of its collaborators, that is, of the people who accepted. PilePrompt suggests your own past collaborators when you share again; those suggestions come only from people who accepted your own shares.
- Blocking. From an invitation you can block the person who sent it. We then store that your account has blocked theirs, together with your email address (invitations are addressed to an email address, so that is what later invitations are checked against) and the address that was shown on their invitation. Their later invitations are not shown to you and cannot be accepted. The person is not told, and on their side nothing looks different. Blocking does not end projects you already share with that person; you can leave those yourself. You can see the people you have blocked and unblock them in Settings (on the web and Desktop: Settings → Account & Sync → Blocked users; on mobile: Settings → Blocked users). Unblocking deletes the record. Invitations sent while the block was in place are not delivered afterwards.
- Reporting. You can report an invitation. We then store your user ID, the inviter's user ID and email address, which shared project and which invitation it concerned, the reason you pick from a short list, and the time. No free text and nothing from any project is stored. The invitation is declined. A report is a record that the operator can look at to detect and stop misuse of invitations. PilePrompt has no moderation team: nothing happens automatically to the person reported, and you will not receive a reply. The person reported is not told.
- If someone blocks or reports you. When you invite someone, they may block or report you; the app says so when you invite. We then hold the record described above about your account. We do not send you a notice when that happens, because it would point to the person who did it. If a report ever leads us to limit your account, we will, where we reasonably can, tell you that we did and why, without naming anyone. Section 13 explains what you can ask us.
- Copies. People you share with can copy or export what they can see. Removing their access later does not delete copies they already made.
6. Usage statistics (web and mobile only, only if you allow them)
Usage statistics are off unless you turn them on. The web and mobile versions ask once whether you want to allow them. If you choose "Not now", or do not answer, nothing is collected. PilePrompt works exactly the same either way, and allowing statistics is never a condition of signing in or of using any feature.
If you allow them, we use Cloudflare Web Analytics to count page views and measure how fast PilePrompt loads. Your browser then loads a small Cloudflare script and sends, for each page load: the page address (without any query string), the referring website, and page-loading performance measurements. Cloudflare derives your browser, operating system, device type and country from the request. As with every internet request, Cloudflare's servers receive your IP address and browser details in order to handle it; Cloudflare states that Web Analytics uses no cookies or local storage and does not use this information to identify or follow individual people. We see only aggregated statistics. Your projects, tasks and notes are never included.
- Changing your mind. You can switch statistics on or off at any time: on the web in Settings → Account & Sync → Privacy → "Anonymous usage statistics", and on mobile in Settings → Privacy. Switching off stops further measurements; it does not undo statistics already collected, which contain nothing that identifies you to us.
- Where your choice is kept. Only in the browser you made it in. It is not sent to us and not linked to your account, so each browser or device is asked separately. "Clear this device" resets it to off.
- Desktop. The PilePrompt Desktop app never loads Cloudflare Web Analytics and never asks.
7. Security and operational records
- Rate limiting. To stop abuse, our servers count how many requests each signed-in account makes per minute. Each count is deleted shortly afterwards, normally within minutes. Failed sign-in attempts are counted per IP address in short-lived server memory only; they are not written to our database.
- Our logs. Our server software records only per-minute totals of request types and outcomes, and the type of any unexpected error. The entries we write contain no content, no email addresses, no account identifiers and no IP addresses. Cloudflare stores each entry together with limited technical details of the request being handled at that moment (such as its path, with identifiers removed). Logs are currently kept for about three days.
- Network processing. Cloudflare, which carries all traffic to PilePrompt, processes IP addresses and technical request information to route requests and defend against attacks, under its own retention practices.
8. Why we use your data, and the legal basis
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Delivering the app to your device | IP address and technical request data, processed by Cloudflare | Performance of our agreement with you (Art. 6(1)(b)) and our legitimate interest in running the service securely (Art. 6(1)(f)) |
| Signing you in and syncing your projects across your devices | Account identifier, email address, sign-in record, synced content | Performance of our agreement with you (Art. 6(1)(b)): you asked for sync |
| Sharing a project with people you choose, and working on a project you accepted | Shared content, collaborators' identifiers, email addresses and roles | Performance of our agreement with you (Art. 6(1)(b)) |
| Delivering an invitation and holding it until the person invited decides | The invited person's email address; the inviter's email address, the project's name and the role, shown to the person invited | For the inviter: performance of our agreement with you (Art. 6(1)(b)). For the person invited, who did not ask for the invitation: legitimate interests (Art. 6(1)(f)): letting a user share a project with the person they chose, limited to what that person needs in order to decide |
| Keeping a record that your account exists, and checking an invited address against it | Account identifier and email address of each signed-in account; the invited address, only while it is being checked | Legitimate interests (Art. 6(1)(f)): letting account holders invite each other by address without our storing the addresses of people who have never used PilePrompt |
| Blocking invitations from a person | The account identifier and email address of the person who blocks; the account identifier of the person blocked and the address shown on their invitation | Legitimate interests (Art. 6(1)(f)): the interest of the person who blocks in not receiving unwanted invitations, and ours in keeping sharing free of abuse |
| Recording a report of an invitation | The reporter's account identifier; the reported person's account identifier and email address; the shared project and invitation concerned; a reason category; the time | Legitimate interests (Art. 6(1)(f)): detecting and stopping misuse of invitations, which protects the reporter and other users |
| Preventing abuse and keeping the service available | Request counts, IP-based limits, aggregate logs | Legitimate interests (Art. 6(1)(f)): security and reliability of the service |
| Making a deletion stick | Deletion and reset markers (section 12) | Legitimate interests (Art. 6(1)(f)): stopping an old device from restoring data you deleted |
| Usage statistics on web and mobile | Section 6 | Your consent (Art. 6(1)(a)), which you can withdraw at any time |
| Answering your requests and meeting legal duties | Your message and what is needed to answer it | Legitimate interests (Art. 6(1)(f)) or legal obligation (Art. 6(1)(c)) |
For invitations, blocks and reports we have weighed these interests against those of each person concerned. The data is limited to account identifiers, an email address and a reason category. It is visible only as described in section 5. A block ends when the person who made it removes it, and its only effect is that one person's invitations do not reach another. A report is deleted after 90 days and leads to no automatic consequence for anyone. We did not find a way to offer blocking or reporting with less data than this. An invitation is stored only for someone who already has an account, and is deleted after 30 days if nobody answers it.
Where we rely on legitimate interests, you can object (section 13). We do not rely on consent for sync: signing in is a request for a service, not a consent to anything else.
9. Who receives your data
- Cloudflare, Inc. provides the hosting, network, database, logging and, if you allow it, usage statistics. Cloudflare acts as our processor under its Data Processing Addendum. See the Cloudflare Privacy Policy.
- Google provides Firebase Authentication as our processor under Google's data processing terms for Firebase. Separately, Google is responsible in its own right for your Google account and for its sign-in window. See the Google Privacy Policy and Privacy and Security in Firebase.
- People you share with or invite — collaborators on a shared project, and people you invite, who see your email address with the invitation, as described in section 5.
- Authorities, where the law requires it.
We do not sell personal data, show advertising, or use your content to train any AI model. PilePrompt itself does not send your content to any AI service; what you copy or paste into a coding agent is between you and that tool.
The operator can technically access the database in order to run the service, and does so only to maintain it, fix a problem, answer a request you made, or comply with the law.
PilePrompt has one optional donation link, "Buy me a coffee", which opens the external service Buy Me a Coffee (buymeacoffee.com) in your browser. PilePrompt does not send that service your projects or account data. If you choose to donate, you give your details directly to Buy Me a Coffee and its payment providers, which handle them under their own privacy policies. Buy Me a Coffee may show us what it shows creators about a donation, such as the name and message you choose to leave; we use that only to see and acknowledge the donation, and we never receive your card details. Other external pages PilePrompt links to, such as Google's sign-in window and the policies named above, also belong to separate services with their own privacy policies.
10. Transfers outside the European Economic Area
Our database currently runs in Western Europe, but we do not promise that your data stays in the European Economic Area:
- Firebase Authentication processes sign-in records in the United States.
- Cloudflare operates a worldwide network and may process data in the country you connect from and in other countries, including the United States.
Both Cloudflare, Inc. and Google LLC take part in the EU–US Data Privacy Framework, which the European Commission has recognised as providing adequate protection, and both include the European Commission's Standard Contractual Clauses in their data processing terms for transfers the Framework does not cover. You can ask us for more information about these safeguards.
11. How long we keep your data
| Data | Kept for |
|---|---|
| Synced content and your account identifier | Until you delete it (section 12) |
| Pending invitations | Until the invitation is accepted, declined or withdrawn, or the project is deleted; otherwise 30 days from when it was last sent. After that it can no longer be seen or accepted. A job that runs once a day then deletes it, so the record can exist for up to a day longer. |
| The record that your account exists (account identifier and email address) | Until you use "Delete all my data" (section 12). It is created again if you go on using sync. |
| Counts of invitation attempts (an account identifier and a number per day, no address) | Up to four days |
| Collaborator records | Until the collaborator is removed or leaves, or the project is deleted |
| Blocks | Until the person who blocked removes the block, or deletes their data (section 12) |
| Reports of invitations | 90 days. A job that runs once a day then deletes them, so a report can exist for up to a day longer. |
| Database history kept by Cloudflare for recovery | The database provider keeps a rolling history that allows recovery after a fault. It is currently 7 days (up to 30 days on other Cloudflare plans). Deleted data leaves this history when that period ends. |
| Deletion and reset markers | For as long as they are needed to keep the deletion effective. They contain an account identifier and a project identifier or a time — no content. |
| Firebase sign-in record | Until we delete it, which we do when you ask (section 12). Google then removes it from its systems within 180 days. Sign-in IP addresses are logged by Firebase for a few weeks. |
| Rate-limit counts | Normally a few minutes |
| Our server logs | Currently about three days |
| Usage statistics (if allowed) | As retained by Cloudflare Web Analytics in aggregated form |
| Messages you send us | As long as needed to deal with your request, and afterwards only if the law requires it |
12. Deleting your data
"Delete all my data" (Settings → Account & Sync) deletes from our live database, in one step: everything you have synced; every shared project you own, for all of its collaborators, together with its invitations and Shared Instructions; your membership of projects owned by other people; invitations other people sent to your email address that you had not accepted; the blocks you made; the reports you filed; and the record that your account exists (section 4), so that you can no longer be invited. It also clears this device's copy.
It does not, by itself, remove everything immediately and everywhere. The following remain:
- A reset marker (your account identifier and the time of deletion) and deleted-project markers (identifiers only, no content), kept so that another device cannot upload the deleted data again.
- The database provider's recovery history, for the period given in section 11.
- Your Firebase sign-in record (section 4). "Delete all my data" does not delete it. Email us from the address you sign in with and we will delete it.
- Blocks and reports that other people made about your account (section 5). A block protects the person who made it and stays until that person removes it; a report is deleted after 90 days (section 11). Both contain your account identifier and the address shown on your invitation.
- Counts of your invitation attempts (your account identifier and a number, no address), deleted within four days (section 11).
- Copies on your other devices, until each device next connects, and files you saved or exported, which are yours to delete.
- Your Google account, which is not ours to delete. You can remove PilePrompt's access at myaccount.google.com/permissions.
"Clear this device" removes PilePrompt's data from the device you are using, without touching your synced data or other devices.
13. Your rights
Under the General Data Protection Regulation you have the right to:
- access your personal data and receive a copy;
- correct inaccurate data;
- erase your data;
- restrict its processing in certain cases;
- receive your data in a portable format;
- object to processing that is based on legitimate interests;
- withdraw consent at any time, where processing is based on consent (usage statistics), without affecting what happened before.
What you can do yourself, in the app: edit or delete any of your content; export everything with "Download backup" (Settings → Account & Sync); delete your synced data with "Delete all my data"; accept or decline invitations; see the people you have blocked and unblock them, which is also how you object to a block you made (section 5); and switch usage statistics on or off.
What needs a message to us: anything else, including a copy of the data held about you (for example the reports you filed, which you can also ask us to delete before the 90 days are over), deletion of your Firebase sign-in record or of an invitation addressed to you, restriction, and objection. Write to bora.duo.apps@gmail.com. We answer within one month; the law allows two further months for complex requests, and we will tell you if that applies. Exercising your rights is free. We may need to confirm that a request really comes from you, normally by asking you to write from the address you sign in with.
Blocks and reports made about you. You can ask us whether we hold a block or a report about your account, ask for a copy of what it says about you, ask us to correct an address in it, and object to our keeping it or ask us to erase it. We look at each request individually. These records also concern another person, so we weigh your request against that person's rights: we normally cannot tell you who blocked or reported you or give details that would identify them, and we may keep a block while it is still needed to protect the person who made it. We will tell you what we decided and why, and you can complain to a data protection authority.
Complaints. You have the right to lodge a complaint with a data protection authority at any time, without contacting us first. In Portugal this is the Comissão Nacional de Proteção de Dados (CNPD), Av. D. Carlos I, 134, 1.º, 1200-651 Lisboa, www.cnpd.pt, geral@cnpd.pt. If you live or work in another EU country, you can complain to the authority there instead.
14. Automated decisions
PilePrompt does no profiling, and makes no decision about you by automated means that has a legal effect on you or affects you in a similarly significant way.
Some technical rules are applied automatically, without assessing you as a person: request limits (section 7); the limits on how many invitations a project can have pending, how many invitation attempts an account can make in a day and how many reports it can file in a day; not creating an invitation for an address that has no account; deleting an invitation nobody answered after 30 days; and not delivering an invitation to someone who has blocked its sender. A block is always another person's own choice, not ours. A report leads to no automatic consequence.
15. Children
PilePrompt is for people aged 16 or older and is not directed at children under 16. We do not ask for your age or date of birth. If you believe that someone under 16 has used sync, or that we hold data about a child, write to bora.duo.apps@gmail.com and we will delete it.
16. Security
We take reasonable steps to protect your data: connections to PilePrompt use HTTPS; every request to the sync service must carry a sign-in token issued by Google, which our servers verify; each account's data is kept separate; shared projects enforce owner, editor and viewer roles; an invitation gives no access to a project until the person invited accepts it; PilePrompt does not reveal whether an email address has an account; and request limits reduce abuse. Synced content is not end-to-end encrypted, which means the operator can technically access it (section 9). No system is perfectly secure, and PilePrompt is a Beta: keep your own backups of anything important. If a breach affects your data, we will tell you and the authority where the law requires it.
17. Changes to this policy
We update the "Last updated" date whenever this policy changes. For material changes — anything affecting what we collect or how we use it — we also show a notice in the app.
18. Contact
Miguel Angelo da Veiga Soares (BoraDuo), Portugal — bora.duo.apps@gmail.com
See also: Terms & Conditions.