Privacy Policy
This policy takes effect on the date it is published at recitpro.app/privacy.
SupportWho is responsible
Giancarlo Severino, based in California, United States, is the data controller for RECITPRO. This policy covers the RECITPRO website at recitpro.app, the Web App at app.recitpro.app, the iOS and iPadOS apps, and Phone Remote. For privacy questions or requests regarding your personal data, email support@recitpro.app.
What we process and why
- Account and sign-in. We use Auth0 to authenticate users. Depending on where you sign in, Auth0 may offer email and password, Google, or Apple. When you enter a password, you enter it on the Auth0 sign-in page. RECITPRO receives an Auth0 user identifier, your email address, your email verification status, your display name when provided, and information about your sign-in provider. We use these details to identify and protect your account. We also process authentication tokens and session identifiers and expiration times to keep you signed in and verify access. The Web App uses a secure session cookie.
- Scripts and reading settings. RECITPRO lets you create, import, and read scripts. Scripts can be stored locally on your device or in your browser. Where Script Sync is enabled, scripts associated with your RECITPRO account are stored on our servers to make them available across supported devices.
- Remote control. During a Phone Remote session, RECITPRO transmits the active script title and text, along with reading and control state, through Cloudflare over HTTPS and secure WebSockets. This lets the controller display a live preview and send commands. The live script state is held temporarily in session memory. Keep the room link private and end the session when finished.
- Purchases. We use purchase information to verify payments and manage access to paid features. Stripe processes payments for subscriptions purchased within the RECITPRO Web App at app.recitpro.app. Apple processes payments for App Store subscriptions. The payment provider collects your payment details. RECITPRO uses purchase and subscription records, including transaction identifiers, subscription status, and relevant dates, to verify purchases, manage Studio access, and handle billing inquiries.
- Support. If you contact us, we use your email address and the information you provide to respond and investigate the issue.
- Website and app activity. We use session cookies to keep you signed in, device or browser storage to save local content and preferences, and technical logs to operate and protect the service and investigate errors.
Optional website analytics
With your permission, we use Microsoft Clarity on RECITPRO’s public pages to analyze clicks and scrolling, generate heatmaps, and record browsing sessions. Microsoft receives this data. Recordings are generally available for 30 days. Heatmaps and some recordings may be retained for up to nine months. You can change your choice under Cookie preferences in the footer.
Com sua permissão, usamos o Microsoft Clarity nas páginas públicas do RECITPRO para analisar cliques e rolagens, gerar mapas de calor e gravar sessões de navegação. A Microsoft recebe esses dados. Em geral, as gravações ficam disponíveis por 30 dias. Mapas de calor e algumas gravações podem ser mantidos por até nove meses. Você pode alterar sua escolha em Preferências de cookies no rodapé.
Con tu permiso, usamos Microsoft Clarity en las páginas públicas de RECITPRO para analizar clics y desplazamientos, generar mapas de calor y grabar sesiones de navegación. Microsoft recibe estos datos. Por lo general, las grabaciones están disponibles durante 30 días. Los mapas de calor y algunas grabaciones pueden conservarse hasta nueve meses. Puedes cambiar tu elección en Preferencias de cookies en el pie de página.
Sharing and international processing
We share the information needed to provide the service with Auth0 for authentication, Cloudflare for hosting and Phone Remote, and Stripe and Apple for purchase processing and verification through their respective channels. Service providers may process information outside your country. Where applicable law requires safeguards for those transfers, we use the safeguards required for the transfer. We may disclose information when required by law.
Retention and account deletion
Where Script Sync is enabled, account deletion removes synced scripts associated with your account from active account storage. Deleting your account also removes locally stored scripts from the app on the device where you delete the account. You can export your scripts before deleting your account. Exported files remain in the location where you saved them.
We keep your account information and synced scripts while your account is active. Copies in backups expire according to the applicable backup schedule. We retain technical logs as needed for security and troubleshooting, support records as needed to resolve and follow up on requests, and transaction records as needed to meet legal and accounting obligations and handle refunds or disputes.
To start deleting your account, open Account Settings in RECITPRO and select Delete Account. Follow the confirmation steps shown in the app.
Your privacy choices and rights
Depending on applicable law, you may have rights to access, correct, delete, or obtain a copy of your personal data, restrict or object to certain processing, or withdraw consent where processing relies on it. To submit a request, email support@recitpro.app. We may verify your identity before acting on a request.
Where applicable law requires a legal basis, we process information to provide the service you request, comply with legal obligations, and pursue legitimate interests such as securing the service and resolving disputes. We rely on consent where required. Where applicable, you may lodge a complaint with your local data protection authority.
Changes to this policy
We will post updates to this policy on the RECITPRO website and update the effective date. When applicable law requires notice or renewed consent for a material change, we will provide the notice or request consent before applying that change.