Privacy Policy

Effective 13 September 2026

Second Take is provided by Mateusz Zajac. This policy explains the handling of information in the iPhone and iPad app and on this website. For privacy questions, email matteo.zajac@gmail.com.

1. Practice and local storage

The app stores your sessions, response choices, feedback, prep cards, a minimal practice record, saved lessons and learning material, and preferences locally on your device. Rehearsal files and the practice record use iOS data protection and are excluded from backups. There is no Second Take cloud account, rehearsal server, iCloud sync, or remote model processing.

You can manage retention and delete saved work through the app. The default rehearsal retention period is 30 days. Eligible closed rehearsals and their linked prep cards are removed when you next open the app after the retention period. Open rehearsals are excluded until closed. Choosing Keep explicitly excludes the entire rehearsal, all its takes, and its saved prep card from automatic expiry. Turning Keep off starts a new normal retention period from that choice. Explicitly deleting a rehearsal still removes its private content and card, even if it was kept.

The separate practice record remembers which authored stories you completed and which you completed a rewind take for, without storing your wording, feedback, readiness answers, or activity dates. Saved lessons remember the authored lessons you deliberately bookmarked. Previously saved learning cards and notes, and any review schedule, are also kept in protected local storage. These records stay on this device. The app uses lesson progress to select the authored lesson label shown by the widget; the widget does not receive the underlying practice record. Reminders remain generic. Completion facts survive automatic expiry or individual rehearsal deletion. They begin with available saved history and cannot reconstruct rehearsals already removed.

Delete all rehearsal data clears every rehearsal and prep card, including kept work, as well as the practice record, saved lessons, and saved learning material. An ordinary preference reset preserves that saved work and the separately managed reminder schedule. Deleting the app or losing your device can remove access to the local practice store, including kept work. We cannot retrieve it for you. Restoring purchases restores eligible library access, not practice data.

If you choose to copy or share a prep card, its contents leave the app through the destination you select. That destination’s privacy practices apply. Please use fictional details while practicing and avoid including confidential workplace information.

Optional conversation check-in

A saved prep card may show a follow-up after a day. You can record that you tried it, choose Not yet, or skip it. An optional reflection stays with the card in the protected local rehearsal store. Answers and reflections are not sent to analytics, diagnostics, or a model and do not appear in widgets, reminders, or prep-card exports. Answering or skipping stops the automatic prompt for that card. You can edit or remove your check-in yourself.

Deleting the card, its rehearsal, or all rehearsal data removes the linked reflection. It also follows rehearsal retention; Keep preserves the parent rehearsal and its reflection. Saving that you tried it refreshes rehearsal activity, while Not yet or skipping does not.

Optional local reminder and widget

Reminders are off by default. If you choose to schedule one, the app requests notification permission and stores your selected daily or weekly time locally. The iOS notification system handles a generic authored reminder, without a story-progress record, personal note, transcript, or prep-card text. There is no remote push server or push token. The reminder may appear on your Lock Screen according to your system settings. You can disable it in the app; deleting rehearsal data or resetting ordinary app preferences does not change this separate reminder schedule.

The optional Home Screen widget shows your current lesson’s title, number, and existing illustration. The app selects the open lesson, otherwise the next incomplete lesson, or the last completed lesson when the path is complete. It shares only that authored lesson’s identifier, title, and number locally with the widget. The widget does not read your rehearsal store or receive your writing, transcript, feedback, prep cards, reflections, readiness answers, bookmarks, completion list, dates, or purchase state. The selected lesson can reveal which topic you are practicing to someone who can see your Home Screen or other widget surface.

Tapping the widget passes only the authored lesson identifier into the app and uses normal navigation and purchase access checks. Deleting all rehearsal data resets the selected lesson to the first lesson. The system controls widget refresh timing, so an older lesson label may remain visible until a refresh. The local widget snapshot is not sent to a server. You can remove the widget using iOS controls.

2. Purchases and restoration

Apple processes your App Store payment. RevenueCat helps verify purchase history and determine whether the Core Library is unlocked. RevenueCat uses an anonymous app user identifier and purchase information, such as the product, transaction, purchase status, and related store metadata. This processing supports receipt validation, fraud prevention, restoration, and purchase reporting.

Second Take does not send your name, email address, rehearsal content, or advertising identifier to RevenueCat, and does not create a personal account for you. We do not receive your payment-card details. Purchase verification and restoration operate separately from analytics and diagnostics. Purchase records may need to be kept to maintain your entitlement and meet applicable transaction requirements.

Read RevenueCat’s privacy policy and Apple’s privacy policy.

3. Usage analytics

Google Analytics for Firebase receives a limited set of app interaction events to help us understand which features work and where people encounter difficulty. These events use predefined names and limited values. They do not include your rehearsal text, prep-card text, search text, scenario facts, readiness answers, personal contact details, or RevenueCat identity.

The analytics service can process a pseudonymous app-instance identifier, app lifecycle and session events, interaction information, StoreKit purchase metrics, app and operating-system versions, device characteristics, language, and approximate location derived from a masked IP address. Second Take disables advertising-identifier and vendor-identifier collection and does not use analytics for advertising, remarketing, or linking your activity across other companies’ apps and websites. We do not ask for precise location access.

Usage analytics starts automatically when the app runs. There is no analytics permission prompt or switch in the app. For questions or requests about information already processed, contact us using the details below. See how Google uses data from partner apps and Firebase privacy information.

4. Technical diagnostics

Sentry receives limited technical error reports and crash reports that help us investigate failures. Reports contain predefined technical error categories, crash stack traces, app and operating-system versions, basic device characteristics, and the release environment. We exclude private practice content, contact information, and user identity.

Second Take does not enable session replay, screenshots, screen recordings, or tracing of your rehearsal activity. Diagnostics starts automatically when the app runs. Crash reports can be stored locally and sent after the app next opens. There is no diagnostics permission prompt or switch in the app. Previously received reports remain subject to service retention and deletion settings. See Sentry’s privacy policy.

5. Support messages and external links

If you email support, we receive your email address and the information you choose to include. We use it to answer you and resolve the request. Please do not send passwords, payment-card details, confidential workplace material, or private rehearsal text. We retain support correspondence only as needed to handle the request and related records.

Further-reading and legal links open only when you choose them. The website or service you open then handles your visit under its own policy.

6. This website

These pages are hosted on GitHub Pages and load their typeface from Google Fonts, following the rest of matteozajac.com. Those providers receive ordinary network information, such as your IP address and browser request, to deliver the pages and font files. These pages do not add analytics scripts, advertising cookies, forms, or a login. Email links open your chosen email app. See the GitHub Privacy Statement and Google Fonts privacy information. Website visits are separate from app analytics.

7. Service providers, retention, and your choices

Apple, RevenueCat, Google, Sentry, and GitHub may process information in countries other than yours under their applicable service terms and safeguards. We use the services described above for purchases, product measurement, diagnostics, and website delivery. We do not sell your rehearsal content or use it for advertising.

Service data is retained under the configured retention settings and the providers’ policies. Local deletion does not delete purchase records or information already sent to a service. To request access, correction, deletion, or object to processing of information we can identify, or to ask about retention, contact matteo.zajac@gmail.com. Because we do not operate personal app accounts, we may not be able to connect anonymous technical information to an individual. We will explain any limitation.

Where applicable law gives you additional privacy rights, including a right to object to processing or to complain to a data protection authority, those rights remain available. Contact us using the details above to make a request.

8. Audience and changes

Second Take is designed for workplace learning and is not directed at children. If you believe a child has sent us personal information, contact us so we can address it.

We will update this page when the app’s practices change. The effective date above identifies this version. A material change to data collection will be reflected in the app’s disclosures.