Effective date: 17 October 2026.
1. Who is responsible for your information
Pipsy is a personal AI assistant for iPhone, with text and voice conversations, reminders and scheduled AI calls. This policy covers the Pipsy app and its product website. AiReminder is the app's technical project name.
The operator and data controller is Habil Demirci, an individual developer (“Pipsy”, “we”, “us”). You can contact us about privacy, account closure or support at habil@pipsyai.com.
This policy explains data handling; it does not itself constitute consent to optional processing or international transfers.
2. Information we process
The information involved depends on the features you use:
| Information | Why it is processed |
|---|---|
| Account information, such as name, email, profile information supplied through sign-in, and account identifiers | Sign in with Apple or Google, maintain your account and synchronize your data. We receive authentication credentials/tokens rather than your Apple or Google password. An automatically generated guest identifier may be used for access to AI services without signing into a main account. |
| Messages, images you submit, AI responses, speech transcriptions and conversation history | Answer your requests, interpret images, maintain conversational context and let you return to conversations. |
| Microphone audio and text used for speech | Provide voice input, live AI conversations and spoken responses. These features send relevant audio or text to speech and AI services; they are not exclusively on-device. |
| Reminder titles, details, schedules, time zone, completion/snooze history and call interactions | Create and deliver reminders and scheduled AI calls, and track changes you make. |
| Preferences, saved places/films/events, assistant name/avatar settings and memory summaries | Restore your settings and saved items, and personalize responses when memory is enabled. |
| Custom voice names, descriptions, provider voice identifiers and associated settings | Create and reuse synthetic voices from descriptions. The current custom-voice feature sends a description to the voice provider; it does not require a recording of a real person's voice. |
| Device location, if permitted, or a place you type | Answer local questions and search for places. The voice assistant receives a rounded approximate coordinate and place name. Place searches and reverse geocoding can send the search-area coordinates to Google; those requests are not necessarily rounded in the same way as voice context. |
| Push/VoIP tokens, installation/account identifiers, delivery status and technical request information | Route notifications and calls to the right device, authenticate requests, prevent abuse and operate the service. Network services also receive connection information such as IP addresses. |
| AI operation metadata, such as provider/model, timestamps, request identifiers, success/error status, token/character counts, duration and estimated provider cost | Monitor service usage, reliability and operating costs. The usage reporting component does not include message text, transcripts or audio; conversation storage is separate. |
| Messages you send to support | Respond to requests, resolve problems and handle privacy or safety reports. |
You control what you include in messages and attachments. Avoid submitting passwords, payment credentials, unnecessary sensitive information or another person's private information without permission. A reminder or conversation may reveal sensitive details even when it is not labelled as such.
3. How your content reaches AI and other providers
Relevant inputs and context are transmitted over the internet to generate responses and carry out the features you request. Requests may include your current message, attached image, recent conversation, reminder context, and, where enabled, memory or location context. During live conversations, permitted approximate location and reminder context can be supplied at session start, before you ask a specific local question.
The current integrations include:
- Google Firebase and Google Cloud: authentication, account data storage and synchronization, backend hosting and notification-related infrastructure.
- Apple: Apple sign-in, push/VoIP delivery, operating-system speech and location services and platform functions used by the app.
- OpenAI: live AI voice sessions and custom synthetic voice creation; OpenAI models may also be selected for text tasks through a routing service.
- Google Gemini: text, image interpretation and supported search-grounded responses, directly or through routing services.
- fal.ai and OpenRouter: routing and processing of supported text-model requests and speech generation. Depending on the selected model, an underlying model provider, including Google, OpenAI or Anthropic, may receive the relevant content.
- ElevenLabs through fal.ai: spoken responses generated from text.
- Google Maps/Places: place search, place information and reverse geocoding.
- Content and search services: queries and technical connection information may reach services used for web results, film information, sports information or externally loaded images, including OMDb and public information/image hosts. Opening a third-party link subjects that visit to the destination's own privacy practices.
Not every provider receives every conversation. The route depends on the feature, chosen model and service configuration. Provider retention, human review and model-improvement rules depend on the particular service, account tier, settings and contractual terms. We cannot currently promise that every route has zero retention or that every provider excludes all use for model training. Do not treat “Keep sessions” as a provider-wide no-training control.
4. Local storage, cloud sync and memory
Pipsy saves conversation history on your device. When account synchronization is active, conversations, reminders, preferences, saved items and related history can also be stored in Firebase under your account. The “Saved” status identifies saved conversations; it is not the only condition under which conversation history is stored.
“AI memory” controls use of previous information for personalization. Switching it off does not itself erase existing conversations or stored memories. “Delete AI memory” is a separate action.
“Keep sessions” controls the storage option sent for new live voice sessions. Switching it off does not erase local history, synchronized account data, existing provider records or operational logs. It is not an incognito mode and does not prevent audio processing needed for the call.
5. Other disclosures
We share information as needed with the service providers described above; to comply with binding legal requirements; to investigate abuse, protect people or defend legal claims; or with your specific direction or permission. If the service changes ownership, related information may be transferred subject to applicable law and appropriate notice.
The current app has no advertising or data-sale integration. We do not offer your conversations for sale or share them for cross-context targeted advertising. A system tracking-permission prompt, if displayed, does not constitute consent to AI processing.
6. Retention and deletion
Local content remains until you remove it or the app's local data is removed, subject to device backups. Synchronized account content and custom voices can remain on our services separately from the local copy. Uninstalling the app or signing out does not close an account or delete cloud/provider records.
Use the app's available conversation, memory and data deletion controls for the content they cover. The current “Delete my data” action does not close your authentication account or comprehensively remove custom voices and all operational/provider records. For account closure or a broader deletion request, email habil@pipsyai.com, identifying the account concerned. We may need proportionate verification; do not send your password or unnecessary identity documents.
We handle rights requests within the periods required by applicable law. Information that must lawfully be retained for security, a legal obligation or a specific dispute is restricted to that purpose. Deleting Pipsy's copy does not automatically prove deletion of a provider's copies or device backups.
We determine retention by the continuing need to provide your account and requested features, outstanding support requests, security needs and applicable legal requirements. Account content, custom voice records and usage records do not currently have a single fixed automatic expiry period. A verified deletion request is assessed across those systems; we will explain any records that cannot be deleted and the applicable reason. No fixed deadline for every provider copy or backup is promised by this policy.
7. Permissions and choices
You can manage microphone, speech recognition, camera, location and notification permissions in iOS Settings, and use Pipsy's available memory, voice and reminder controls. Denying a permission can prevent the feature that needs it from working. Revoking a permission stops future permission-dependent access; it does not erase information already processed. Stop a live session to end its ongoing voice transmission.
Reminder content can appear in push payloads, notifications and the incoming-call display, including while the phone is locked. Choose titles accordingly and review your device's notification preview settings; those settings may not hide every system call display.
8. International processing, legal grounds and your rights
Our cloud and AI providers operate internationally. Your information may be processed outside your country, including in Europe and the United States, according to the route used. The location of one gateway does not mean that every downstream service processes data in that region.
The applicable legal requirements for international transfers depend on your location, the recipient and the processing arrangement. You may contact us for information about the arrangements relevant to your request. This policy does not claim that all data remains in one country, that every destination offers equivalent protections, or that accepting the service replaces any legally required transfer safeguard or separate consent.
For users in Türkiye, the processing grounds, where their legal conditions are met, are: establishment/performance of the service contract for account access and requested features; legitimate interests, subject to balancing your rights, for proportionate security, abuse prevention and service-usage administration; compliance with an identified legal obligation where applicable; and separate explicit consent for optional processing that requires it. Where GDPR applies, the corresponding bases are Article 6(1)(b), (f), (c) and (a), respectively. Special-category data requires an additional applicable legal condition and should not be submitted unnecessarily.
Subject to applicable law, you may request access, correction, deletion, restriction or portability; object to processing, including applicable direct marketing; withdraw consent without affecting earlier lawful processing; and complain to the relevant supervisory authority. Under KVKK Article 11, you can also ask whether data is processed, obtain information on purposes and recipients in Türkiye or abroad, request notification of correction/deletion to recipients, object to a result against you produced solely through automated analysis, and seek compensation for unlawful processing. Contact the address in Section 1. KVKK requests are resolved as soon as possible and within 30 days, in accordance with the applicable procedure. Other jurisdictions may set different periods and conditions.
9. Website, children and security
The product website stores your language choice in browser local storage. Its demonstration does not create an account, record audio, schedule a real reminder or place a real call. Visiting the site still generates network information for its hosting infrastructure. The current product site has no advertising pixels or third-party analytics scripts. Email links open your email application. This notice must be updated before introducing additional tracking or collection.
Pipsy is intended for people aged 18 and above, subject to any higher local requirement. It is not directed at children below that age. Contact us if you believe an ineligible child's information has been submitted so we can address the situation under applicable law.
We use measures designed to protect information, including authenticated access, encrypted network connections and platform file protection for stored conversations. No system is completely secure. AI calls and cloud conversations are processed by servers; they are not end-to-end encrypted so as to exclude the processing providers.
10. Updates and contact
We will update this policy when relevant practices change, show the effective date and provide appropriate notice of material changes. Where a change requires consent or another legal step, notice or continued use alone will not replace it.
Privacy, account and safety requests: habil@pipsyai.com. Operator: Habil Demirci.