Your information, explained
Privacy Policy
Effective and last updated: October 18, 2026
Service scope: Supported mobile builds provide account sign-in, subscriptions, U.S. phone setup, AI call answering, chat, transcripts, summaries, recording playback, Spam filtering and live call controls, subject to eligibility, carrier support and completed setup. Store sandbox purchases are test payments.
Call recording: The setup agreement covers AI data processing and call recording. Recording is enabled by default for eligible AI-handled incoming and outgoing calls and may start as soon as the call connects, including the opening greeting. The assistant is instructed to give a brief recording notice naturally in its greeting; the app does not present a separate caller keypad approval. Recordings are stored privately by Twilio for up to 30 days. Only the authenticated account owner can request playback. Recording stops before the owner takes over. A spoken notice is not a guarantee that every use meets applicable recording or calling laws.
1. Who we are and what this policy covers
Shibi Sharkie (“we,” “us,” or “our”) is the developer operating shibisharkie.com and the Shibi Sharkie mobile application. This policy covers personal information handled through our website, pre-release application, account authentication, and support communications. For this processing, Shibi Sharkie is responsible for determining the purposes of use, subject to applicable law.
Contact the developer at support@shibisharkie.com. Independent platforms, carriers, and providers may also handle information under their own notices when you use their services.
2. Information handled in the current release
- Account information: email address, account identifier, sign-in provider, and basic profile information made available by the provider, such as name and profile image. Email sign-in uses a one-time code or the account password where configured. The app does not ask for your Google or Apple password.
- Phone verification: the U.S. phone number you enter, its country-validation result, verification request identifiers, request times, attempt counts, and verification status. We use Twilio to validate the number and deliver and check a one-time verification code. By requesting a code, you request a verification message; we do not send marketing messages through this flow. A successfully verified number and verification time are associated with your existing account. Our application database does not store your verification code.
- Authentication and device storage: session credentials, sign-in events, and the last successfully used sign-in method. The app stores session information on your device to keep you signed in. Its browser preview uses local storage for this purpose; native builds use platform secure storage.
- Technical information: hosting, delivery, authentication, and security providers may process IP addresses, browser or device details, request times, error information, and access logs to deliver and protect their services.
- Support information: your email address and information you choose to send us, including relevant troubleshooting details. Do not send passwords, one-time codes, full payment details, or other unnecessary sensitive information.
- Subscriptions: app-store transaction identifiers, product, status, environment, and expiration, associated with your account to verify access and prevent purchase reuse. We do not receive your full payment-card information from the app store.
- Call and inbox information: assigned receiving number, selected carrier, forwarding-check status, caller ID (which may be spoofed), call identifiers, time and outcome, conversation transcripts, AI summaries, your chat messages, AI replies, and answering instructions you save. Do not put unnecessary sensitive information in instructions or messages.
- Memory: after accepting the updated in-app privacy choices, Sharkie extracts explicitly stated personal facts, preferences and tasks from your own chat messages, summarizes earlier conversation context and retrieves relevant older messages and call summaries. Caller statements are not verified personal facts. Memory values and summaries are encrypted on our server before storage in Supabase and unavailable through client database APIs. Relevant non-secret memories are shared with OpenAI to answer you. Remembering a fact does not authorize disclosure to callers: disclosure requires purpose-specific authorization or review of a specific outgoing call message. Recognized SSNs and credentials in typed chat are masked and kept in a separate encrypted vault, not supplied to AI as memory. Detection is not comprehensive: do not use Sharkie as a password manager, and avoid sending secrets in files, images, speech or messages. Authorized operators can administer this data; encryption does not mean we cannot access it.
- Uploads and outgoing requests: photos/documents you choose to send, their names and types, the destination and approved message for a personal outgoing call, your permission attestations, request status, and recipient opt-out records. Contact access can resolve a person you explicitly ask the assistant to call. Access to contacts alone never authorizes calling everyone.
- Optional contacts access: after sign-in and the service agreement, the native app asks for system permission to access selected or all device contacts. A first grant syncs supported U.S. phone numbers over an encrypted connection for matching; the server stores account-specific keyed fingerprints rather than raw contact numbers. These fingerprints are personal matching data, not anonymous data. Contact names, photos, notes and other details stay on your device. Refusing access does not block AI answering. All forwarded calls go to Sharkie by default. Existing shared contact scope can refresh when the app returns to the foreground; you can revoke contact access in device Settings.
- Native calls and notifications: random device identifier, platform, call-routing preference, telephony identity, push token, and active call identifiers/status are associated with your account to deliver incoming calls or optional AI-call alerts and authorize listening or taking over. Notifications may be visible on your lock screen according to your device settings.
The website has no account form, payment form, advertising pixels, or analytics scripts added by us. Viewing its mascot does not request access to your microphone, address book, or calls. Native contacts, microphone, camera and notification permissions require their own system authorization. Refusing optional device access does not prevent AI answering. The service agreement cannot grant system permissions or authorize a caller's recording on their behalf.
3. Why we use information
We use information to create and authenticate accounts, maintain sign-in sessions, provide the functionality actually available to you, investigate technical problems, answer support requests, prevent abuse, and comply with applicable legal obligations. We do not collect information merely because a future feature might need it.
Where a legal basis is required, account and requested-service processing may be necessary to perform a contract or take steps at your request; proportionate security and troubleshooting may rely on legitimate interests; legal requirements may rely on legal obligations. The setup agreement explicitly states the purposes and recipients of AI data sharing and call recording before approval. System permissions, caller choices and individual outgoing-call authorization remain separate. You can request account deletion without first agreeing to AI use. Withdrawal applies to the relevant processing and does not make earlier lawful processing unlawful.
4. Google and other sign-in providers
Google sign-in is used for account authentication. The current integration requests basic identity scopes: openid, email, and profile. It does not request Gmail messages, Google contacts, Drive files, Calendar events, or permission to send email from your Google account.
We use Google-provided information to identify your account, authenticate you, and display basic profile details where supported. We do not sell it, use it for targeted advertising, or use it to train generalized AI or machine-learning models. Our handling of Google API information follows the Google API Services User Data Policy, including its Limited Use requirements.
Apple sign-in is enabled in supported builds. Apple may provide your name and email or a private relay address. We use those details for the same account purposes. A sign-in provider’s own privacy notice also applies to its processing.
5. Service providers and other disclosures
Providers involved in the current release include:
- Supabase: account authentication, account records, and related service infrastructure.
- Google, and Apple when enabled: identity verification and provider sign-in.
- Resend: delivery of transactional authentication email.
- Twilio: phone verification, number provisioning, forwarding checks, call routing, live audio, and private call recording and playback as described above.
- Expo, Apple, and Google: device push registration and delivery of supported call alerts, including device tokens and call-event identifiers. Native incoming calls use Twilio and the platform's push service; alert delivery is not guaranteed.
- OpenAI: live call audio for AI answering and transcription, selected conversation text for chat responses and call summaries, and photos/documents you submit for AI help. We ask for your permission in the app before this processing. We disable storage of chat/summary response objects in API requests; this is not a promise of zero provider-side retention. Provider security, abuse-monitoring, and legal retention may still apply under their policies.
- Railway: hosting of the call-answering, chat, and subscription-verification backend.
- Vercel: hosting and delivery of the public website.
- Cloudflare and our destination email provider: domain infrastructure and forwarding or receipt of support email.
We disclose information as needed for these functions, not for unrelated advertising. We may disclose information where legally required, to protect rights or investigate abuse, or in connection with a genuine business transfer, subject to applicable protections and notice requirements. A request to access your account or information must have a lawful basis; this policy does not authorize unrestricted disclosure.
We do not sell personal information or share it for cross-context behavioral advertising.
6. Forwarded calls, AI, and caller choices
After setup, carrier forwarding sends all incoming calls directly to Sharkie by default. The assistant uses OpenAI to process live audio and produce responses and transcripts. The greeting is instructed to identify the assistant as acting on the account owner’s behalf and briefly disclose recording when enabled. There is no separate caller approval or keypad menu in the current flow. If the caller refuses recording, the assistant is instructed to end the call. The model can be interrupted or make mistakes, so notices and delivery cannot be guaranteed. Caller IDs and claimed identities can be spoofed.
Saved text is accessible through the account owner’s authenticated inbox. Transcripts and summaries may be wrong or incomplete. During an AI-handled call, an enrolled user may listen with the microphone muted or take over after the AI disconnects and recording is stopped. A private instruction sent by the owner during a call is stored with the account; it is not directly shown to the caller, but may influence what the assistant says. Personal outgoing calls begin from the owner’s explicit instruction and can use optional on-device contact matching. Eligible outgoing calls are also recorded by default. Uncertain call requests are not automatically redialed. The service does not transfer calls to arbitrary third parties or send scheduled daily reports. An account agreement cannot grant another person’s legally required permission.
7. Retention and deletion
A verified phone number is retained with your account until it is replaced or your account is deleted, subject to applicable retention obligations. Short-lived verification-attempt records support abuse prevention and request limits; records older than one day are pruned when a new verification request is processed. Verification and infrastructure providers may retain their own operational or security records under their applicable notices and agreements.
Account records are retained while your account is maintained and as reasonably needed for the purposes above. Session credentials remain on your device until sign-out, removal, expiration, or app/browser data deletion, depending on the platform. Support records and technical logs may be retained to resolve issues, protect the service, or meet legal requirements; retention also depends on the provider and category of information.
Chat messages, call metadata, transcripts, summaries and answering instructions remain with your account until deletion, subject to justified legal and security retention. Suspected spam is classified using transcript evidence and kept in Spam calls without a chat summary; classification may be wrong and you can move a call between categories. Optional contact fingerprints and device-routing records are removed with your account. Canceling a subscription does not delete history. Optional recordings expire after 30 days; playback is denied after expiry and provider deletion is retried if unavailable. Recordings may be unavailable after expiry or provider failure. Independent provider operational retention is separate.
Use Menu → Account → Delete my account. We confirm your request and, for Apple sign-in, ask for fresh Apple authorization to revoke it. Deletion removes your authentication account, customer record, messages, call logs/transcripts/summaries, optional recordings held by Twilio, instructions, uploads, outgoing requests and associated subscription records. Active calls are stopped and new activity is blocked during cleanup. Failed cleanup is retried automatically. A minimal cleanup identifier normally remains about three hours for previously issued upload grants; outages may delay retries. A retired receiving number remains unlinked and quarantined, not reassigned.
Account deletion does not cancel an app-store subscription or disable carrier forwarding. You can do both separately using the links in account settings; neither is a prerequisite to requesting deletion. Independent provider records and backups may remain under their retention policies or justified legal obligations. We do not promise every independent provider record can be erased instantly. Contact support if you cannot access your account.
8. Your choices and privacy requests
Ask Sharkie to forget a saved fact, or ask it to forget all saved memory. Clearing memory removes remembered facts, rolling summaries and encrypted vault entries, not the visible chat/call archive. Earlier messages are excluded from memory reconstruction after clearing. Deleting your account also deletes this memory. You may contact support to correct or request access to account-linked information.
You can sign out, clear locally stored app/browser information, and revoke Shibi Sharkie’s Google access in your Google Account connections. Removing provider access is not itself a request to delete our stored account records; contact us if you want those removed too.
Depending on applicable law, you may have rights to request access, correction, deletion, a portable copy, restriction, or objection, and to withdraw consent for processing based on consent. You may also have the right to complain to your local data-protection authority. We will assess requests under the law that applies, verify identity where needed, and respond within applicable legal time limits. We do not require you to give up statutory rights to submit a request.
9. International processing
Our infrastructure providers may store or process information outside your country, including in the United States, depending on the service and project configuration. Privacy laws differ between countries. Transfers remain subject to applicable law and required safeguards; use of a cloud provider is not a waiver of your rights. Contact us for information about the arrangements applicable to your request.
10. Security
We use authentication and platform storage controls to help protect information and limit access. No service, transmission, or storage method is completely secure. Keep your device and accounts protected and do not share authentication codes or session credentials. Report a suspected security issue to our contact address without including unnecessary sensitive data.
11. Children
The pre-release service is intended for adults aged 18 or older, not children. If you believe a child has supplied personal information through the service, contact us so we can investigate and take appropriate action under applicable law.
12. Changes
We may update this policy when the service or its practices change. The date above identifies the current version. Material changes will be communicated as required by law; where new processing requires consent, posting a new policy alone will not replace that consent.
13. Contact and account deletion requests
Email support@shibisharkie.com with “Privacy request” or “Account deletion” in the subject. Include enough information to locate your account, but do not send your password or sign-in code. You may also use this address to ask about data processing or report a security concern.