Pinqo Privacy Policy
Effective date: 27 September 2026
1. Who we are
Pinqo is operated by FOP Konoz Polina Oleksandrivna (ФОП Коноз Поліна Олександрівна), a sole proprietor registered in Ukraine, tax number 3474505463 (“Pinqo”, “we”, “us”, “our”).
Registered business address:
83-B Ukrainska St., Apt. 7, Irpin, Bucha District, Kyiv Region, Ukraine
Privacy contact:
2. Scope
This Privacy Policy explains how we collect, use, disclose, store and delete personal data when you use the Pinqo mobile application and related services (the “Service”).
Pinqo is a personal library that allows users to save and organize content for their own use. A user may also intentionally create an unlisted dashboard share link as described below.
Pinqo is intended for users aged 16 and over.
3. Data we process
Depending on the features you use, we may process the following categories of data.
Account and authentication data
This may include:
- email address;
- internal Pinqo user identifier;
- authentication-provider identifiers;
- display name provided by an authentication provider;
- authentication and session information;
- Apple or Google authentication information where those sign-in methods are used.
When Sign in with Apple is used, Pinqo may securely store a server-side Apple refresh or access token for the limited purpose of revoking Apple authorization if the Pinqo account is deleted.
Saved-content data
When you save content to Pinqo, we may process:
- URLs;
- titles and descriptions;
- source or platform information;
- author or creator metadata where available;
- categories and tags;
- favorites;
- timestamps;
- thumbnails and preview metadata;
- text extracted from saved content;
- other metadata associated with the saved item.
Pinqo does not download or store standalone copies of third-party video or audio files as part of its content-enrichment process.
Unlisted dashboard sharing
If you create a dashboard share link, anyone who possesses the valid link can open the shared dashboard without signing in. The link is unlisted and is not described by Pinqo as searchable or publicly indexed, but it can be forwarded by a recipient.
A recipient may see the dashboard name, your display name where available, and shared items’ source URLs, canonical URLs, content types, titles, creator names or handles, thumbnails, descriptions, summaries and save dates. A signed-in recipient may add a reference to the shared dashboard to their own library and later remove it.
You can revoke the share link. Revocation makes that token unavailable through Pinqo, including to recipients who previously saved a reference, but cannot retract information that a recipient already viewed, copied or forwarded.
Share Extension and Save Action data
When a save or authentication flow cannot finish inside the Share Extension or Save Action, a pending URL or shared text and limited non-secret extension state may be stored temporarily on the device in storage shared with the main app. The data is used to resume the requested flow and is cleared when consumed, when the relevant account data is cleared, or according to the implemented replacement lifecycle. Pending images are not queued in this way.
Images and screenshots
If you choose to save or share an image or screenshot to Pinqo, we may store:
- the image itself;
- image metadata;
- edited or cropped versions;
- text extracted from the image using optical character recognition (OCR).
Pinqo does not request broad photo-library access. Camera permission is optional and is requested only if you choose Take Photo. A captured photo can then be uploaded and stored as saved user content. Pinqo does not use continuous or background camera access and this feature does not request microphone access. Images can also be provided through supported sharing or file-selection flows.
Automatically generated organization and search data
Pinqo may generate and store:
- suggested categories;
- suggested tags;
- summaries;
- extracted text;
- OCR text;
- language information;
- embeddings used for semantic search;
- AI-generated organization metadata.
Subscription and purchase data
If paid subscriptions are enabled, Pinqo may process:
- subscription status;
- product identifier;
- entitlement status;
- store transaction identifiers;
- purchase environment and status;
- store notification identifiers.
Payment-card numbers, CVV codes and similar card data are handled by Apple App Store or Google Play and are not stored by Pinqo.
At the date of this Policy, billing functionality exists in the software but may be disabled until subscriptions are activated.
Technical, security and diagnostic data
We may process limited technical information required to operate and secure the Service, including:
- app and operating-system version;
- timestamps;
- request and processing status;
- sanitized technical errors;
- security events;
- IP address used ephemerally for rate limiting and abuse prevention.
Pinqo does not maintain a dedicated database field containing your IP address. Infrastructure providers may process network information as part of providing their services.
Analytics data
When the distributed version of the app is configured with an Amplitude project key, Pinqo sends the following explicit product-usage events to Amplitude:
- free-plan warning shown and free limit reached;
- paywall viewed and upgrade clicked;
- dashboard share created, opened, added to a library, removed from a library or revoked.
Event properties are limited to save counts, remaining-save counts, the current free/Pro plan value when the free limit is reached, paywall or profile source, and monthly/yearly purchase interval. These are product-interaction and subscription-state analytics.
Pinqo does not send an email address, Pinqo user UUID, Supabase UUID or other account identifier to Amplitude. The Amplitude SDK supplies a random device identifier that is held only in memory for the current app launch and a session identifier. Pinqo disables persistent Amplitude identity storage and keeps unsent analytics events in memory rather than cookies or local storage.
Pinqo disables Amplitude autocapture, default events, page/form/file/network/performance capture, remote configuration, SDK diagnostics, IP-property tracking, language tracking, platform tracking and custom enrichment. No advertising identifier, IDFA, ATT permission, session replay or cross-app advertising tracking is used.
Pinqo does not send search terms or query length, saved titles, URLs, descriptions, OCR or AI content, category or tag names, creator names or handles, images, transaction identifiers, app-account tokens, authentication tokens or error details to Amplitude.
Exact search terms are processed separately for search functionality as described in section 8; they are not analytics data.
Support communications
If you contact us by email or another support channel, we may process the information you choose to provide in that communication.
4. Data we do not intentionally collect as product fields
Pinqo does not currently request or intentionally collect as dedicated product data:
- precise or approximate location;
- contacts;
- phone number;
- date of birth;
- health data;
- payment-card numbers;
- advertising identifiers such as IDFA;
- ATT tracking permission;
- push-notification tokens;
- microphone data;
- biometric data.
Saved screenshots or text may incidentally contain information of any type chosen by the user. Pinqo treats that material as user-provided content rather than as a dedicated sensitive-data category.
5. How we obtain data
We obtain data:
- directly from you;
- from your device when you use the Service;
- from authentication providers such as Apple, Google and Supabase;
- from Apple App Store or Google Play if billing is enabled;
- from public web pages, content platforms, oEmbed endpoints, Open Graph metadata and other public metadata sources when you ask Pinqo to process a saved link.
For some supported platforms, Pinqo may also process publicly available metadata contained in public HTML pages associated with the saved content.
Pinqo does not claim ownership of third-party content.
6. Why we use personal data
We use personal data as necessary to:
- create and maintain your account;
- authenticate you;
- save and display your private library;
- organize, categorize and search saved content;
- generate metadata, OCR text, categories, tags and semantic-search data;
- process images and screenshots you choose to save;
- provide and restore subscriptions if billing is enabled;
- secure the Service and prevent abuse;
- diagnose technical problems;
- measure product usage where analytics is enabled;
- provide customer support;
- comply with applicable law;
- enforce our Terms of Use.
7. Legal bases for EEA and UK users
Where the GDPR, UK GDPR or similar European data-protection law applies, we process personal data on one or more of the following legal bases:
- performance of a contract, where processing is necessary to provide the Service you request;
- legitimate interests, including operating, securing, maintaining and improving Pinqo;
- consent, where consent is legally required;
- legal obligations, where processing is necessary to comply with applicable law.
Where we rely on legitimate interests, we consider the impact on users and the nature of the processing.
8. Automated and AI-assisted processing
Pinqo uses automated and AI-assisted processing to help organize and search saved content.
This may include:
- extracting text from screenshots using OCR;
- generating suggested categories and tags;
- generating summaries or organizational metadata;
- creating vector embeddings for semantic search.
Pinqo currently uses OpenAI services for certain text-processing and embedding functions.
Data sent to OpenAI may include limited text derived from saved content, such as:
- titles;
- descriptions;
- captions;
- OCR text;
- text excerpts;
- category names;
- tag names;
- author names;
- source/platform information.
Pinqo does not currently upload screenshots or image files to OpenAI.
Pinqo does not include your email address or Pinqo internal user UUID in the OpenAI request body used for these functions.
When you use semantic search, Pinqo may send the exact search terms to OpenAI to create a query embedding. Pinqo may cache normalized query text and the corresponding embedding for approximately 24 hours. This is search-functionality processing, not product analytics, and the query-cache row does not contain your Pinqo user identifier.
AI-assisted outputs are used to help organize and retrieve content. They are not used to make legal, employment, credit, healthcare or other similarly significant decisions about you.
9. Service providers and recipients
We use third-party service providers to operate Pinqo.
Depending on the feature used, these may include:
- Supabase — authentication, database and storage;
- Fly.io — backend hosting and infrastructure;
- OpenAI — text-based AI processing and embeddings;
- Amplitude — product analytics, if enabled;
- Apple — Sign in with Apple and App Store billing;
- Google — Google OAuth and Google Play billing;
- Meta / Instagram / Facebook / Threads — public content metadata and oEmbed services;
- YouTube / Google APIs — public YouTube metadata;
- TikTok — public oEmbed metadata;
- Pinterest — public oEmbed metadata;
- public websites and content delivery networks required to retrieve public metadata or preview images.
These providers process data according to their own contractual and privacy obligations.
We may also disclose personal data:
- where required by law;
- to protect users, Pinqo or third parties;
- to investigate fraud, abuse or security incidents;
- in connection with a merger, acquisition, financing or transfer of the business, subject to applicable law.
We do not sell personal data.
We do not use Pinqo user data for third-party advertising, and the current app does not use IDFA or ATT-based tracking.
10. Third-party platforms and links
Pinqo allows users to save content originating from third-party services and websites.
Those services are independent of Pinqo and have their own:
- privacy policies;
- terms;
- content rules;
- availability and technical restrictions.
Pinqo is not responsible for the privacy practices or availability of third-party services.
11. International transfers
Pinqo is operated from Ukraine and uses service providers that may process data in other countries.
The current Fly.io production and staging backend configuration uses the London region (lhr). Other service-provider regions may vary or be provider-controlled.
Where European data-protection law requires safeguards for international transfers, we rely on applicable transfer mechanisms, such as:
- adequacy decisions;
- Standard Contractual Clauses;
- other lawful transfer mechanisms available under applicable law.
12. Data retention
We retain personal data only for as long as reasonably necessary for the purposes described in this Policy.
In general:
- account and library data are kept while your account remains active;
- saved content and private stored images remain until you delete the item or your account;
- semantic-search embeddings associated with saved items are deleted with the related content;
- temporary search-query embedding-cache entries normally expire after approximately 24 hours;
- signed image URLs normally expire after approximately 1 hour;
- completed account-deletion tombstones are retained for approximately 90 days and then eligible for deletion;
- certain non-user-specific operational records or shared assets may be retained after account deletion;
- billing-notification records may be retained in de-identified or unlinked form;
- a minimal billing ownership record containing the store provider and original transaction or subscription-lineage identifier is retained indefinitely after the account association is removed, to protect subscription ownership and prevent fraud or cross-account rebinding;
- infrastructure logs, backups and third-party copies may remain for periods determined by operational requirements or provider retention policies.
Retention periods controlled by third-party providers, including OpenAI, Amplitude, Apple, Google, Supabase and Fly.io, may differ from Pinqo’s application-level retention.
13. Account and data deletion
You can initiate account deletion from the Pinqo application.
The account-deletion process is designed to remove:
- your Pinqo account record;
- your saved items;
- categories and tags;
- private images stored under your user account;
- user-scoped AI and organization data;
- stored Apple authorization token, where applicable;
- your Supabase authentication account.
Where a stored Apple authorization token is available, Pinqo attempts to revoke that authorization with Apple before completing account deletion.
If an older Apple account has no stored revocation token, Pinqo may still complete deletion of the Pinqo account and authentication record.
After account deletion, Pinqo may retain a limited deletion record containing the authentication subject identifier for up to approximately 90 days to prevent deleted accounts from being automatically recreated by an old authentication token.
If a store subscription has been associated with a Pinqo account, Pinqo removes the Pinqo user/account association during deletion but retains the provider and original transaction or subscription-lineage identifier indefinitely. This minimal record may remain linkable to the Apple subscription lineage and is used to prevent the same subscription from being claimed by a different or newly created Pinqo account. Deleting and recreating a Pinqo account therefore does not make the previous subscription lineage claimable by the new account.
Some information may remain outside Pinqo’s direct control, including:
- third-party analytics history already stored by an analytics provider;
- data previously processed by AI providers under their own retention rules;
- infrastructure backups;
- platform logs;
- app-store transaction records held by Apple or Google.
Deleting your Pinqo account does not automatically cancel an active App Store or Google Play subscription. Subscription cancellation must be managed through the applicable store.
For privacy or deletion questions, contact:
14. Your privacy rights
Depending on where you live, you may have rights to:
- request access to personal data;
- request correction;
- request deletion;
- object to or restrict certain processing;
- withdraw consent where processing is based on consent;
- request a portable copy of personal data where applicable;
- lodge a complaint with a competent data-protection authority.
Pinqo does not currently provide a self-service data-export feature in the app.
You may submit a privacy-rights request by contacting:
We may need to verify your identity before fulfilling a request.
15. Security
We use technical and organizational measures intended to protect personal data.
Current measures include, where applicable:
- HTTPS transport;
- authenticated access to private user data;
- private storage for user screenshots and images;
- time-limited signed URLs for private images;
- user-scoped backend queries;
- secure storage of authentication credentials on supported devices;
- restricted server-side storage of secrets;
- token and secret redaction in application logs;
- rate limiting and request-size controls;
- protection against certain unsafe outbound requests.
No system can guarantee absolute security.
16. Children
Pinqo is intended for users aged 16 and over.
Pinqo does not currently collect date of birth or operate child accounts or parental-consent flows.
If we learn that personal data has been collected from a person below the permitted age contrary to this Policy, we will take reasonable steps to delete it.
17. Israel
For users in Israel, Pinqo processes personal information in accordance with applicable Israeli privacy and data-security requirements.
Where additional legal requirements become applicable to Pinqo’s activities, we will take appropriate steps to comply with them.
18. Changes to this Policy
We may update this Privacy Policy as Pinqo evolves, including when we change:
- product functionality;
- hosting providers;
- analytics services;
- AI providers;
- payment functionality;
- data-processing practices.
If required by law, we will provide additional notice of material changes.
The effective date at the top of this Policy indicates when it was last updated.
19. Contact
FOP Konoz Polina Oleksandrivna
83-B Ukrainska St., Apt. 7
Irpin, Bucha District
Kyiv Region, Ukraine
Email: pinqoapp@gmail.com