Download on the App Store
Get it on Google Play
Privacy policy

Wetin we dey keep, wetin we no dey keep, and why.

Na rehearsal of conversations wey matter to you, na im you dey share. We dey treat am wit di respect wey e deserve.

Last update

Quippy App, Inc. ("Quippy", "we", "us") na im dey run di Quippy mobile app, di website wey dey for quippyapp.com, and oda features wey follow am (all together, di "Service"). Dis policy dey explain wetin data we dey collect wen you dey use di Service, wetin we dey do wit am, and di choices wey you get. E be part of our terms of service.

Na only wetin we need to run di Service we dey collect:

Information wey you give us. Your email address wen you create account, account details like display name, age, gender, profile photo, and authentication tokens, di scenarios wey you run, di lines wey you write or talk during practice, di feedback wey Quippy dey give you back, and any message wey you send us wen you contact support.

Voice input (wen you use am). If you practice wit your voice, we go send di audio go one speech-to-text provider so dat we fit turn am to transcript. Di transcript go become part of di session record; we no dey keep di raw audio for long time unless we tell you somtin else.

Device and usage data. Device type, operating system version, app version, language, time zone, IP address, crash reports, and events wey dey describe how you dey move through di app. Di full detail wey we dey collect for analytics, including session replay, dey explained for di next section. Dis one dey help us keep di app dey work and make flows wey dey confuse pipo better.

Website analytics. When you use this website, we collect the full page URLs you visit including their query strings, the referring URL that sent you here, your browser user agent, coarse browser, device, viewport, and language details, campaign parameters, and interaction events such as clicks on links to the app stores. Apart from job applications, described below, we do not ask for or collect your email address on this website. The waitlist closed when the app launched, and its signup form has been removed. Website analytics is anonymous: our analytics provider records your activity under a random browser identifier and does not create an identified profile of you. It also derives your approximate location from your IP address. The next section describes this in full.

Job applications. If you apply for a role on our careers pages, the application form comes from Ashby, our applicant tracking system, and runs inside the page. What you enter there, such as your name, email address, resume, and any answers, goes to Ashby and to us. We use it only to consider you for the role and to contact you about your application. It is not sent to our analytics provider. Ashby handles it under its own privacy policy (https://www.ashbyhq.com/resources/privacy).

Purchase data. If you subscribe, na di Apple App Store dey handle payment and e go share receipt wit us, and one subscription management provider (RevenueCat) go check say di receipt correct so we fit give you access and manage am. We no dey receive your full payment card details.

Google Analytics for Firebase. The production iOS app uses Google Analytics for Firebase for a small set of product and conversion events. The app sends sign_up, tutorial_complete, quippy_lesson_completed, and quippy_subscription_activated. These client events do not include your email address, phone number, name, account ID, conversation content, or other user-provided text. We use this data to understand app activity and measure conversions for our Google Ads campaigns. Firebase collection is limited to production App Store builds. We exclude staging builds, TestFlight builds, and simulator runs, except when a developer explicitly enables Firebase diagnostics with -FIRDebugEnabled.

Adjust remains the owner of the iOS App Tracking Transparency (ATT) request. Firebase does not show a second tracking prompt. Unless you authorize tracking, Firebase keeps ad_storage denied. We keep ad_user_data and ad_personalization denied, and we do not use Firebase for personalized remarketing.

Subscription measurement. RevenueCat also sends subscription lifecycle events to Google Analytics for Firebase through Google's GA4 Measurement Protocol. Events can include purchase, rc_trial_start, and related subscription lifecycle events, along with product, transaction, revenue, and currency details. This server-side feed uses the native Firebase app instance ID and an existing opaque RevenueCat/Firebase account ID. It does not include your email address, phone number, name, conversation content, or user-provided text. RevenueCat remains our source of truth for subscription lifecycle and revenue records; Firebase receives a copy for conversion measurement.

Install attribution and ad measurement. We dey use Adjust to measure which marketing efforts dey bring app installs and subscriptions. For iOS, Apple App Tracking Transparency (ATT) framework dey ask whether you allow tracking. If you allow am, Adjust fit use your device advertising identifier (IDFA) to connect app activity and subscription events wit ad interaction. If you no allow tracking or identifiers no dey available, Adjust no dey receive IDFA wey e fit use. Adjust fit send app events go Meta wit di Advertiser Tracking Enabled parameter set to false or no. Meta dey use dat signal for privacy-preserving Aggregated Event Measurement and e dey limit how e dey use dose events. Adjust fit also use probabilistic measurement wia dem allow am. Apple SKAdNetwork and AdAttributionKit systems dey also provide aggregate attribution. For Android, Adjust fit use di Google Play Install Referrer and di Android Advertising ID (GAID) wia dem allow am. Adjust fit share attribution and conversion data wit our advertising partners, wey be Google Ads, Meta, TikTok, X, and Reddit for now, to measure and improve campaign performance. You fit manage or withdraw Quippy tracking permission any time for iOS Settings (under Privacy & Security > Tracking) or opt out of personalised ads for Android Settings. We no dey ever send raw conversation content, including your practice transcripts, voice audio, and session feedback, for ad attribution.

Store buttons for dis website. Di App Store and Google Play buttons for dis website na Adjust links. When you tap one, Adjust go record di tap, plus di IP address and device details wey your browser send, then e go carry you go di store. If you come from Google ad and di page address get click ID (gclid, gbraid, or wbraid), di button go add dat ID to di Adjust link so Adjust fit connect di install to dat ad. Di button go also add some more details so Adjust fit match di install to your visit: di random browser ID wey our analytics provider give you, di campaign details for di page address (utm_source, utm_medium, utm_campaign, and Facebook click ID), di page wey you dey without im query string, and which button you tap. If your browser dey send Global Privacy Control opt-out signal, di button no go pass any of dis one.

Communications. If you email us or you reply Quippy email, we dey keep dat correspondence so we fit follow up and make support better.

We dey use PostHog, Inc. (PostHog US Cloud, wey dem host for United States) as our analytics provider for both di app and dis website, including session replay. We don choose to collect detailed record of how pipo dey use di Service so we fit understand am and make am better. Dis section dey explain wetin dat record contain.

For inside di app. We dey send PostHog detailed record of how you dey use di app. Dis one include which screens and features you dey use, di profile details wey you enta like your age, gender, goals, and progress numbers, and internal identifiers for di content wey you dey touch. Your email, name, and account id dey attached to your analytics profile. Di record also include di text of di practice messages wey you dey send during session, di search words wey you type, and di answers wey you give during onboarding. Our analytics provider dey take your rough location, like your country, region, and city, from your IP address.

Session replay. In both the app and on this website, our analytics provider records how you move through the screens, including what you type and the images shown on screen, so we can see where the experience is confusing. Recordings also include the text your browser writes to its developer console and the details of the network requests it makes, including the content those requests send and receive. Password fields, cookie and authorization headers, and bearer tokens are left out of recordings. Other text is recorded as it appears.

For dis website. We collect the full page URLs you visit including their query strings, the referring URL that sent you here, your browser user agent, and the campaign parameters that brought you to a page. Website analytics is anonymous. Our analytics provider records this activity, and keeps a visitor profile of it, under a random browser identifier, and we do not link it to a name, email address, or account. If you joined the waitlist before the app launched, the email you submitted may remain in your own browser's local storage. We use it only to mark visits from our own team so they do not distort our statistics, and the address itself is not sent to our analytics provider.

Checks for di website. We dey also use OnePatch to measure how pages dey load, clicks, network requests, and website errors. E dey receive browser and device details wit a random session identifier, without name, email address, or account. We dey remove query strings and fragments from page and referrer URL details before we send dem. OnePatch no dey record session replay or collect wetin you type for forms or console output.

This analytics data pass wetin plenty products dey collect. We dey treat am as personal data and we no dey sell am. We no dey use am to advertise to you. The only part wey dey reach our advertising partners na wetin the store buttons dey pass to Adjust, like the Google Ads click identifier, campaign details, and your random browser identifier, so Adjust fit credit the install to the correct ad or visit (check "Store buttons for dis website" wey dey up). You fit ask us make we delete am with the options wey dey for the Your rights section.

We dey use wetin we collect to:

Na wit help from third-party language model providers dem dey produce Quippy scene partners and feedback. To generate response, we dey send di relevant parts of your session (like di scenario setup and di dialogue wey just happen) go dis providers through encrypted connection.

We choose providers that contractually agree not to train their general-purpose models on the content we send them. Providers may retain inputs and outputs for a short period for abuse monitoring and trust-and-safety review, then delete them. We do not use your session content to train any model that is shared across users, and we do not share your session content with model providers for any purpose other than generating your own scene partner responses, feedback and practice summary.

Di conversation content wey we dey send go dis providers and wey we dey collect from dem, wey fit include your practice messages, di replies wey dem generate, and di free text wey you enta during onboarding, dey also logged to our analytics provider (PostHog) so we fit review di quality of wetin di Service dey produce. See Analytics and session replay to sabi more.

Quippy dey allow you connect apps wey you don already dey use, so your practice fit follow di conversations wey dey really come up for your life. To connect app na your choice, and you fit disconnect any app anytime inside di Quippy app. Quippy dey only read from di apps wey you connect. E no dey ever post, send message, or change anything for inside dem, and e no dey send your Quippy data go dem.

Wetin we dey read from Google. When you connect Google account, Quippy fit read your Google Calendar events (dia titles, times, and di people wey go attend), your Google Meet meeting transcripts, and your YouTube subscriptions. Only if you choose to connect dem, Quippy fit also read your Gmail messages and di titles and wetin dey inside di Google Drive files wey you pick. Dis access na read-only. Quippy no dey ever send email for you, edit your calendar events, or change your files. Quippy dey use YouTube API Services (di YouTube Terms of Service: https://www.youtube.com/t/terms) to read your subscriptions, and Google Privacy Policy (https://www.google.com/policies/privacy) dey apply to dat data for Google side. Apart from to disconnect for Quippy, you fit remove Quippy access to your Google data anytime for https://security.google.com/settings/security/permissions.

Wetin we dey read from other apps. Depending on di apps wey you connect, Quippy fit read: from iPhone Calendar, Calendly, Cal.com, and Eventbrite, your events wey dey come and di ones wey don pass, bookings, and tickets, wit dia titles, times, and di people wey go attend; from Zoom, Fathom, Fireflies, tl;dv, Granola, Otter, Read.ai, Circleback, and Fellow, di titles, summaries, and transcripts of your meetings; from Slack, messages for di conversations wey you fit see; from Notion, di pages wey you share wit Quippy; from Linear and Jira, di titles, statuses, projects, and due dates of di issues wey dem assign give you; and from X, your profile and di accounts wey you dey follow. Na for your phone we dey read your iPhone calendar, and e go reach Quippy only after you turn am on. Content from apps wey you connect fit get information about other people, like di names of people wey you meet and wetin dem talk for meeting.

Di link to your LinkedIn profile. If you add di link to your public LinkedIn profile, Quippy dey check dat profile through People Data Labs, one data provider. Quippy no dey sign in to LinkedIn, and na only di link wey you give am e dey use. From wetin come back, Quippy dey keep your current role, company, industry, seniority, and city, up to 5 past roles, up to 10 skills, and di names of your schools, and e dey save dem as short facts di same way as facts from apps wey you connect. Quippy dey check di link again at most once every 6 months. If you remove di link, e go delete those facts.

How we dey use am. We dey use information from apps wey you connect only to make your own conversation practice fit you. Quippy dey turn wetin e read into short facts about di conversations wey dey come, di people wey dey inside dem, and di topics wey matter to you, and e dey save those facts for your Quippy memory. Di raw content, like di full text of email or meeting transcript, na to produce those facts we dey process am, and Quippy no dey store am. Na only di short facts we dey keep.

Who dey process am. Composio dey manage di connections to your apps and di access tokens wey follow dem, and Anthropic dey provide di language model wey dey turn di content into short facts. After dat, di short facts fit go to di language model providers wey we describe for Language model providers, including Anthropic, to run your practice. We no dey sell data from apps wey you connect, we no dey use am for advertising, and we no dey share am wit data brokers, and nobody dey ever use am to train language models or any other machine learning models.

How to delete am. If you disconnect app, Quippy go stop to read anything new from am, e go cancel Quippy access, and e go delete di facts wey come from dat app within 7 days. If you remove Quippy access from inside di other app, for example for your Google Account settings, Quippy go do di same thing within 30 days. If you delete your Quippy account, e go delete di facts wey we store and cancel Quippy access to di apps wey you connect. You fit also ask us to delete dis data if you email hello@quippyapp.com.

Quippy's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

We no dey sell your personal information. We no dey share your transcripts wit advertisers, researchers, or oda companies for dia own purpose. We no dey use your conversations to train models wey go benefit oda users or oda companies. Quippy no be social network: you no dey follow oda users, and oda users no fit see your activity or your content.

If you dey for European Economic Area, United Kingdom, or Switzerland, na dis legal bases under di GDPR we dey rely on:

Na only wit service providers wey dey help us run di Service we dey share data, and na only as much as dem need am. Di kain providers wey we dey use include:

Contract dey bind each provider wey require dem to handle your data only to deliver dia service to us, and to follow correct security practices. People Data Labs dey handle lookups under di terms wey e don publish.

We fit also share data wen law require am, to enforce our terms, to protect di safety of users or di public, or as part of company transaction like merger or acquisition. If di company wey dey run Quippy change hand, we go tell users, and privacy policy wey dey protect you at least as much as dis one go continue to protect your data.

We dey keep your data only as long as we need am for di purposes wey we tok about for up:

We dey keep your data wit our cloud infrastructure provider, and e dey encrypted for transit (wit TLS) and wen e dey rest. We dey follow standard security practices for small product team: access wey be only wetin pesin need, audit logging, secret management, regular dependency updates, and quick response to any issue wey pipo report. No system dey perfectly secure, so we no fit promise say security go complete, but we dey treat your data wit di care wey e deserve and we go tell you if any breach touch your data, as di law require.

Na from United States we dey run Quippy. If you dey use di Service from anoda kontri, your data go move go United States and dem go process am for dia, and for any oda kontri wia our service providers dey work. Wia dem require am, we dey use proper safeguards like Standard Contractual Clauses for international transfers.

Depending on wia you dey live, you fit get right to see di personal data wey we hold about you, to correct am if e no correct, to delete am, to collect copy wey you fit carry go anoda place, to object to or limit certain processing, and to withdraw consent wey you don give us. You get right too to report complain to your local data protection authority.

You fit delete your account for inside di app. See how you go delete your account for di steps and exactly wetin dem go remove. You fit also email hello@quippyapp.com to make any of dis requests. We go respond within thirty days, or faster wia di law require am. We fit need to confirm say na you bifor we act on any request.

If you dey live for California, you get di rights wey we tok about for up under di California Consumer Privacy Act, including right to sabi di categories of personal information wey we dey collect and disclose, right to delete personal information, right to correct information wey no correct, and right say dem no go discriminate against you becos you use dis rights.

We no dey sell personal information, and we no dey share personal information for cross-context behavioral advertising as di CCPA define dose words. You fit send your requests by emailing hello@quippyapp.com.

Quippy no be for pikin wey neva reach 13 years, and we no dey knowingly collect personal information from pikin wey neva reach 13. If you tink say pikin wey neva reach 13 don give us im information, abeg email hello@quippyapp.com and we go delete am.

We dey send small number of optional product update emails. Every marketing email get unsubscribe link, and if you opt out, e no go affect transactional messages like receipts and security alerts.

Di Quippy app fit send push notifications (for example, daily practice reminder). Na you dey control dem for di app settings or for your device notification settings.

Our website dey use cookies and browser storage for three reasons: small set wey the site need to work well and remember wetin you like; analytics storage wey PostHog dey use to measure how people take use the site and record how you dey move from page to page, as we describe am for Analytics and session replay; and, if na Google ad bring you come here, the click identifier wey that ad get. The click identifier go stay for your browser session storage until you close the tab, so the store buttons fit pass am to Adjust (check "Store buttons on this website" wey dey up). We no dey use third-party advertising cookies. The Quippy app no dey use web cookies, but e dey use device identifiers and local storage to keep you signed in, to sync your data, and for the analytics wey we describe for up.

We fit update dis policy as di product or di law dey change. If any update really affect how we dey handle your data, we go tell you inside di app or by email bifor e start to work. Di "last updated" date wey dey di top of dis page always dey show di most recent change.

You get question about anytin for dis page, or you wan use your privacy right? Send message go hello@quippyapp.com and we go reply within few days.