Privacy
Privacy Policy
Effective date: 9 November 2026
Applies to: the Pakopya app for iPhone and Android, version 1.0 and later
1. Who we are
Pakopya is made by Luigi-John Canosa, trading as Pink Potato Design ("we", "us"), in the Philippines.
For anything in this policy, including any request about your personal information, contact our Data Protection Officer at onepinkpotatodesign@gmail.com.
We handle personal information under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173), its Implementing Rules and Regulations, and the issuances of the National Privacy Commission (NPC). Pakopya is available outside the Philippines too, and section 9 describes the rights people have elsewhere.
2. The short version
- Your recipes live on your phone. Everything you save in Pakopya is stored in a database on your device. We do not have a server that holds your library.
- A recipe you share is kept for 90 days. From version 1.0.8, when you share a recipe, the app uploads that one recipe to our server, Supabase, and sends a short link to it. Anyone who has the link can read the recipe until it is deleted, 90 days later. It is not linked to you or your account, and your notes are never included (section 3.3). Earlier versions upload nothing when you share.
- An account is optional. If you sign in with Apple or Google, our sign-in service, Supabase, keeps an account identifier, which of the two you used, and the email address that Apple or Google gives us. No recipe, note or setting is sent with it. If you don't sign in and don't share a recipe, we receive nothing at all, apart from the ordinary request details our service providers see when a shared recipe is opened (section 4).
- We do not track you. Pakopya has no analytics, no crash reporting, no advertising and no tracking.
- Tips are paid through Apple or Google. Pakopya is free, and a tip is optional and unlocks nothing. If you leave one, Apple or Google takes the payment; we never receive your card, GCash or other payment details, and the app keeps no record of it.
- Your phone contacts other websites when you import. When you paste a link, your phone fetches that page and its picture directly from the site that hosts them. Section 4 lists every kind of site the app contacts.
- You can export your library from Settings, and if you signed in, delete your account and everything with it.
3. What the app stores, and where
3.1 On your phone
Pakopya keeps its data in a database file on your device (named pakopya.db).
It holds:
| What | Where it comes from |
|---|---|
| Recipes: title, description, ingredients, steps, times, yield, drink type | Imported from a link or text you provide, and any edits you make |
| The recipe's source: the link, the site or platform name, and the author's name or handle as the source shows it | The page you imported from |
| The recipe's picture, downloaded and saved as a copy on your phone | The picture the source page points to |
| Your notes on a recipe | You |
| Your make log: when you made a drink, your star rating and any note | You |
| Your settings: language register, library view, whether you finished the intro screens | You |
If you sign in, the app also keeps your signed-in session on the phone, so you stay signed in between launches.
We use this information only to run the app for you: to show, search, edit and make your recipes. It does not leave your phone except in the ways described in section 4, and when you choose to share a recipe (section 3.3) or export your library (section 7).
Clipboard. Pakopya does not read your clipboard. To import a link, you paste it into the link field yourself, the way you would in any text field.
Device backups. Your phone's own backup can include app data. The Pakopya database is stored in a location that iCloud and computer backups normally include, so a backup you make can contain your recipes, under Apple's terms.
Temporary network data. When the app fetches a page or picture, your phone's operating system may keep temporary cached copies, and a site may set cookies that your phone sends back to that same site on a later fetch. These stay on your device.
3.2 What we receive: your account, if you make one
Signing in is optional. Pakopya accounts use Sign in with Apple or Sign in with Google only. There is no password.
- Apple gives us a unique user identifier for Pakopya and, if you allow it, an email address. If you choose Hide My Email, Apple gives us a private relay address instead of your real one. Pakopya does not ask Apple for your name.
- Google gives us a unique account identifier and your email address, and its sign-in token also carries your name and the address of your profile picture.
Our sign-in service stores, for your account: the account identifier, which provider you signed in with, the email address and other details the provider returned (as listed above), when the account was created and when you last signed in, and the technical records a sign-in service keeps to secure accounts, such as the internet address a sign-in came from.
We use these only to create and secure your account and to contact you about your account when necessary. We do not use them for marketing.
Apart from a recipe you choose to share (section 3.3), that is everything we receive from the app, and if you never sign in, we receive none of it. The app does not send your library, notes, make log, settings, location, contacts, photos or usage information to us or to any analytics, advertising or crash-reporting company.
3.3 What we receive: a recipe you share
From version 1.0.8, when you tap Share on a recipe, the app uploads that
recipe to our server, run for us by Supabase, and sends your friend a short link to it, such as
https://pakopya-lemon.vercel.app/r/ followed by a random 7-character code.
Sharing works whether or not you are signed in. Earlier versions upload
nothing: they put the recipe inside a longer link, described below.
What is stored: the recipe as it is in your library: its title, description, ingredients, steps, times, yield and drink type, the source link, the original author's name or handle as the source shows it, and the address of the recipe's picture (the address only; the picture itself is not uploaded).
What is not stored: your notes on the recipe, your make log, any account identifier, your name or email, or a device identifier. Your IP address is not stored with the recipe. A shared recipe is not linked to you or to your account, and we do not use it for tracking, advertising or analytics. To stop the share service being flooded, we keep a scrambled (salted SHA-256) form of the internet address a share came from, counted per minute, and delete it within two days. Supabase's own request logs record the IP address of each request to the share service, as any web server does, and keep it for up to 1 day.
Who can read it: anyone who has the link, including anyone your friend forwards it to. The link is not listed or searchable anywhere, but it is not private either, so share only what you are happy for others to see. The Pakopya app and the Pakopya website fetch the recipe from Supabase when the link is opened.
How long: 90 days from when you shared it. After that it is deleted automatically, within a day, and the link stops working. To have a shared recipe deleted sooner, email onepinkpotatodesign@gmail.com with the link.
If the upload fails, or there is no connection, the app sends a longer link
instead. That recipe travels in the part of the link after #, which never
reaches us or our website host.
3.4 Permissions
From version 1.0.8, you can import a recipe from a photo or a screenshot. When you do, your phone shows its own photo picker, or opens the camera if you take a photo (on iPhone it asks you first). The picture is read on your phone to find the text, and only that text becomes your recipe; the picture is never sent to us or anyone else, and it is not saved with your recipe. The picker hands the app a temporary copy, which your phone clears.
Pakopya does not ask for access to your location, contacts or microphone, and it does not send notifications. Apart from the photo picker and camera, the only system prompt you may see is the Apple or Google sign-in sheet, if you choose to sign in.
4. Who your phone talks to
The app makes network requests only in the situations below.
| When | Your phone contacts | What that service receives |
|---|---|---|
| You sign in | Apple or Google, then our sign-in service, Supabase | The sign-in you approve on Apple's or Google's sheet, and the token it produces |
| You are signed in and open the app | Supabase, to keep your sign-in current | Your session token |
| You delete your account | Supabase, and Apple if you signed in with Apple | Your session token, and for Apple a one-time code used to revoke Pakopya's access |
| You import a link | The website in the link (for example a recipe blog, Instagram, Facebook, YouTube or TikTok) | Your IP address, the link, and standard request details such as a browser-style user-agent and a language preference |
| You import a Reddit link | old.reddit.com (the app rewrites Reddit links to that address, and removes Reddit's tracking parameters from the link first) | The same as above |
| You import a TikTok link | TikTok's public embed service, https://www.tiktok.com/oembed | Your IP address and the TikTok link |
| An import finds a picture | The server that hosts the picture, which may be a different company from the page (for example an image delivery network) | Your IP address and the picture's address |
| When the app checks for a connection (before an import, a sign-in or Delete account) and at intervals after that while the app is open | Google's connectivity check, https://clients3.google.com/generate_204, used by the open-source network library the app is built with | Your IP address and a request with no content. No recipe or personal data is included |
| When the app starts, and when you open the tip jar or leave a tip | The App Store (Apple) or Google Play (Google) | The tip products the app asks to show, and for a tip, the purchase you approve on Apple's or Google's own sheet. The store handles the payment under its own privacy policy |
| You tap a source link, Privacy Policy or Terms of Use | Your browser or the App Store opens | Whatever that app or site collects under its own policy |
| You share a recipe | Our share service on Supabase | The recipe listed in section 3.3, your IP address and standard request details. We store the recipe, and a scrambled form of the IP address for up to two days. The IP address is not stored with the recipe; Supabase's request logs keep it for up to 1 day |
| You export or share | The app you pick in your phone's share sheet | What you chose to send: the export file, or the recipe's link |
You open a short link a friend sent (/r/ and a code), in Pakopya or in a browser | Our share service on Supabase, to fetch the recipe | Your IP address, standard request details, and the link's code. Nothing about you is stored with the recipe; Supabase's request logs keep the IP address for up to 1 day |
| You open a recipe a friend shared with you as a link, in a browser or without Pakopya installed | The Pakopya website, pakopya-lemon.vercel.app, hosted for us by Vercel | Your IP address, standard request details such as your browser's user-agent, and a request for the page /r, which for a short link includes its code. For a longer link, the recipe is in the part of the link after #, which browsers do not send to websites, so neither we nor Vercel receive it. If Pakopya is installed and the link opens it directly, the website is not contacted |
Imports go straight from your phone to the site in the link, never through a Pakopya server. Each of those sites and services handles what it receives under its own privacy policy. Apart from Supabase and Vercel, which work for us (section 11), we do not control them and do not receive anything from them about you.
Pakopya does not use these requests to identify you, and it does not combine them with any other information.
Downloading Pakopya, and receiving updates, happens through the App Store under Apple's privacy policy.
Tips. The tip jar's three tips are in-app purchases that Apple or Google sells on our behalf. They process the payment; we never receive your card, GCash or other payment details, and a tip unlocks nothing, so the app stores nothing about it. For our tax and accounting records, Apple and Google send us sales reports listing what was bought, when, for how much and in which country, and Google's may include the general location it records, such as a postal code. These reports do not include your name, email address or payment details.
5. Why we process information, and on what basis
What the app does on your phone (section 3.1) happens on your own device, at your direction, to provide the features you use.
Where we process personal information ourselves, we rely on the grounds in the Data Privacy Act (and, for users where it applies, the GDPR):
| Purpose | Basis |
|---|---|
| Your account and keeping it secure | Needed to provide the service you asked for (contract), and our legitimate interest in preventing misuse |
| Storing a recipe you share, so its link works for 90 days | Needed to provide the service you asked for when you tapped Share (contract) |
| The one-day scrambled IP count on shares | Our legitimate interest in keeping the share service from being flooded |
| Responding to your requests and complaints | Legal obligation and legitimate interest |
| Keeping sales records of tips | Our legal obligations for tax and accounting records |
We do not sell personal information, we do not share it for advertising, and we do not make decisions about you based solely on automated processing.
6. How long information is kept
- On your phone: until you delete it. Delete account removes it from the app's database, and so does uninstalling the app. Copies in your own device backups or in anything you exported remain under your control.
- Your account, with Supabase: while your account exists. Deleting your account removes it straight away; copies in Supabase's routine backups and security logs are removed as those expire.
- A recipe you share, with Supabase: 90 days, then deleted automatically within a day. The scrambled IP count is deleted within two days. Supabase's request logs, which include IP addresses, are kept for up to 1 day; Vercel's are kept for the short period its policy sets.
- At third-party sites you import from: under those sites' own policies.
7. Exporting and deleting your data
Export. Settings, then Export everything, creates a copy of your library in JSON format and opens your phone's share sheet so you can save or send it. The export includes every saved recipe (with ingredients, steps, notes, times, source link and author) and its make log. It does not include the saved pictures or your app settings.
Delete a recipe. A single recipe can be deleted from its own page. That deletes it from your phone; a copy you shared stays readable through its link until its 90 days are up.
Delete a shared recipe early. Because a shared recipe is not linked to an account, the app cannot delete it for you, and Delete account does not remove it. Email onepinkpotatodesign@gmail.com with the link and we will delete it.
Delete your account. If you signed in, Settings, then Delete account, deletes your account from Supabase and then erases everything in the app's database on this phone: recipes, pictures, notes, make log and settings. If you signed in with Apple, Apple asks you to confirm first, and Pakopya's access to your Apple ID is revoked before the account is deleted. Deleting needs an internet connection; if the account cannot be deleted, nothing is deleted. It cannot be undone, so export first if you want a copy.
If you never signed in, there is no account to delete: uninstalling Pakopya removes everything it saved on the phone.
You can also ask us to delete your account without the app, by emailing onepinkpotatodesign@gmail.com from the address on your account, or telling us which Apple or Google account you used.
8. Children
Pakopya is not directed at children under 13, and some recipes people save are for alcoholic drinks. You must be at least 13 to create an account, or have a parent or guardian's permission where the law requires it. We do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us at onepinkpotatodesign@gmail.com and we will delete it.
9. Your rights
Under the Philippine Data Privacy Act
As a data subject, you have the right to:
- be informed whether and how your personal information is processed;
- access your personal information;
- object to processing, including processing based on consent or for direct marketing;
- correct inaccurate personal information;
- have your personal information erased or blocked when it is incomplete, outdated, false, unlawfully obtained, no longer needed, or processed without a valid basis;
- data portability, to get a copy in an electronic, commonly used format;
- be indemnified for damages caused by inaccurate, incomplete, outdated, false, unlawfully obtained or unauthorised use of your personal information; and
- file a complaint with the National Privacy Commission (privacy.gov.ph).
Elsewhere
Depending on where you live (for example the European Union, the United Kingdom, or US states such as California), you may have similar rights: to access, correct, delete or port your data, to restrict or object to processing, to withdraw consent, to know whether your information is sold or shared (we do neither), not to be discriminated against for using these rights, and to complain to your local data protection authority.
How to use them
Your library is on your phone, so you can see, correct, export and delete it yourself in the app, and Delete account removes your account too. For anything else, including a copy of what your account holds or deleting a recipe you shared, write to onepinkpotatodesign@gmail.com. We will reply within 30 days. We may ask you to confirm the request comes from you.
10. Security
Your library is protected by your phone's own security: its lock screen and the operating system's app sandboxing and storage encryption. Pakopya does not add a separate password or encryption layer. Anyone who can unlock your phone can open the app. The connections the app makes use encrypted HTTPS.
Your account data and shared recipes are encrypted in transit and at rest with Supabase. A shared recipe can be read by anyone with its link, and only through our share service, which never lists them. Access to your account data is limited to us and to Supabase as our service provider, and we will notify the National Privacy Commission and affected users of a personal data breach as the Data Privacy Act requires.
11. Service providers and international transfers
We use Supabase, Inc. to run sign-in, store your account, and store the recipes people share. Supabase stores that information on our behalf in Singapore, under a written agreement and its own privacy policy. Requests to Supabase, from the app or a browser, reach the Supabase server nearest the person making them, so a request may pass through another country on its way to Singapore. We use providers that commit to protecting personal information to a standard comparable to the Data Privacy Act.
We use Vercel Inc. to host the Pakopya website, including the page that shows a recipe someone shared as a link. When that page is opened, Vercel receives the request details listed in section 4 and keeps them in its server logs under its own privacy policy. It never receives the recipe inside a longer shared link, and a short link's recipe comes from Supabase, not from Vercel.
The sites your phone contacts when you import (section 4) may be located outside the Philippines.
12. Changes to this policy
We will update this policy when the app changes what it does with information, before the change reaches you in an update. The effective date at the top will change. If a change means we start receiving personal information we did not receive before, we will tell you in the app before it applies.
13. Contact
Luigi-John Canosa, trading as Pink Potato Design
Data Protection Officer: onepinkpotatodesign@gmail.com