Privacy Policy

1. Scope and who we are

This Privacy Policy explains how NablaNotes ("NablaNotes," "we," "us," or "our"), operated from San Diego, California, handles personal information through the NablaNotes iPad app, related web app and extension features, and nablanotes.com (collectively, the "Service").

For privacy questions or requests, email nablanotescorp@gmail.com. This is our working privacy contact.

2. Information we collect and process

Account and authentication information

When you create or use an account, we process your email address, Supabase user ID, authentication records, and account metadata. If you use Sign in with Apple or Google sign-in, we also receive the provider identifier and information the provider makes available with your permission, such as your email or name. Apple may offer a private relay email address. We retain authentication credentials needed to support sign-in and, where configured, Apple authorization revocation when an account is deleted.

Notes, files, and workspace data

For signed-in users, supported page data may sync to Supabase. That data can include note and folder titles, hierarchy, ordering, timestamps, page index, template choices, typed text, drawings and stroke points, tool/color/size/shape information, inline image data or references, and recording duration or stroke-timing metadata. Inline content in synchronized page data leaves your device.

Native PencilKit files, packaged note media, imported PDF assets, audio recordings, and saved tutor-session files are generally stored on your device rather than mirrored as a complete Supabase backup. A reference to a local file in synced data does not itself upload that file. The Service is not a complete cloud backup, and offline changes may still be waiting to sync.

There are specific upload flows. Custom template uploads send the original file, rendered PDF page images, preview images, and template metadata to Supabase database and Storage services; community template sharing may make associated records or URLs available to others. Send-to-computer and browser-extension transfers upload screenshots and queue records. Issue reports may include descriptions and up to three user-selected photo or video attachments.

AI, OCR, and tutor information

When you choose math recognition, OCR, solver, or AI Tutor features, the Service sends the selected image or page snapshot and relevant prompt, OCR text, note context, and conversation history through a Supabase Edge Function to the Google Gemini Developer API (currently Gemini 2.5 Flash). Google returns recognized content or generated responses. The current handlers do not intentionally write the request image or chat body to a Supabase database or Storage bucket as part of the inference request, but provider infrastructure and security logs may retain them.

Saved tutor sessions remain locally on your device and can contain the scan image, analysis, messages, and generated cards. The app currently retains up to 20 saved tutor sessions subject to an approximately 25 MiB scan budget, although a newest oversized scan may exceed that budget. Tutor content inserted into a page can later become part of normal page sync. Saved sessions may also be included in exports and iCloud backups.

Analytics and diagnostics

Our Supabase database records account-linked product events, including the signed-in user ID, event name, subscription tier label, timestamps, and event metadata. Events can cover math solving, graphing, AI Tutor actions and chat sends, computer transfers, and recording starts. Ordinary feature events are not intended to include the text, image, audio, or chat body being used, but separately submitted issue reports and feature requests do include the text you enter.

The native iOS app also uses PostHog US Cloud. Before sign-in, its iOS SDK may assign an anonymous device identifier and collect app lifecycle, app version, device/operating-system, network, and similar technical event properties. After sign-in, the app calls PostHog identification with a stable account or sign-in-provider identifier, so later events are linked to a person profile. Native events include sign-in results, feature use, microphone permission actions, recording and iCloud-backup outcomes, issue reports, and feature requests. Our Supabase AI functions also send PostHog the AI token-usage counts for each request, linked to your user ID (or marked anonymous when you are not signed in), but not the prompt, image, or response. Issue-report descriptions and feature-request form fields are sent to PostHog; issue attachment files are not, although the attachment count is. We do not use this analytics data for third-party advertising.

Support, feedback, and website information

If you contact us or use in-app feedback, we process your message, contact details, app/build and platform information, and any files you choose to attach. A feature request may include your name, major, class or course, requested feature, and explanation. The email-verification page on this website reads the result of your confirmation link in your browser and then removes it from the address bar; it does not store the link's code or tokens. If you ask it to resend a verification email, it sends that email address to Supabase. The open-beta form on this website sends your name, email address, optional questions, and signup context to Formspree. Our hosting and service providers may also process IP address, request time, browser/device information, and security logs when you access the Service.

3. How we use information

• Provide accounts, authentication, note organization, supported synchronization, uploads, exports, and requested iCloud backups.
• Process OCR, math-solving, and tutor requests and return generated results.
• Operate, secure, debug, and improve the Service; understand account-linked feature use; enforce limits; and investigate misuse.
• Respond to support requests, issue reports, and feature suggestions.
• Send transactional account email, such as verification, password reset, magic-link, invitation, and account-change messages.
• Comply with law, protect users and the public, and establish or defend legal claims.

We do not sell personal information and do not use note content for third-party behavioral advertising. We do not currently offer paid production subscriptions, and Stripe is not part of the current production data flow.

4. When information is disclosed

We disclose information only as needed to operate the Service, at your direction, or for legal and safety reasons. Current service providers include:

• Supabase for authentication, database, Storage, and Edge Function processing.
• Google for the Gemini Developer API used by OCR, solver, and tutor features, and for optional Google account sign-in.
• Apple for Sign in with Apple, TestFlight/App Store distribution, and iCloud Drive when you request a backup.
• PostHog for native product analytics and diagnostics in its US Cloud environment.
• Resend for transactional authentication email sent on our behalf.
• Formspree for the website's beta-access form, and Netlify for public website hosting.

These providers process information under their own terms and privacy notices. Information may also be disclosed when required by law; to address fraud, security, or threats to rights and safety; during a merger, financing, acquisition, or transfer of assets subject to appropriate protections; or with your consent.

If you intentionally publish or share a community template, export, note package, screenshot, or other content, recipients can retain their own copies. Do not include information you lack the right to share.

5. AI provider processing and retention

AI input and output do not stay only on your device. They pass through our Supabase function and Google's Gemini infrastructure. Google's published Gemini terms distinguish paid and unpaid services. Depending on the billing tier and optional data-sharing settings applied to our Gemini project, Google may use submitted content and responses for product improvement and may permit human review. We therefore do not promise that AI content is never used for training or review.

Google states that abuse-monitoring records can retain prompts, contextual information, and outputs for 55 days and may be reviewed by authorized personnel. That period is not a universal deletion guarantee for every Google processing purpose. Avoid submitting confidential information, regulated records, or personal information about someone else through AI features unless you have the right and a sound reason to do so. See the Gemini API terms and usage policies.

6. Local storage, iCloud, exports, and security

NablaNotes uses a mixed-storage design. Some content is stored locally, some supported data synchronizes to Supabase, and files you explicitly upload use Supabase Storage. Do not assume a file is backed up merely because a note appears in your account.

When you manually choose an iCloud backup, the app writes full note archives and an index to your own iCloud Drive container. Those archives can include ink, media, imported assets, audio, and tutor material and use your iCloud storage. Upload may remain pending, and older backup generations currently accumulate rather than being automatically pruned. NablaNotes backend administrators do not have general access to browse your private iCloud container, but the installed app can read and write its container and the archives do not have additional app-level encryption. Manage or delete those copies through the app, iCloud, or your Apple account.

Exports and files you save or share are controlled by you and the destination you choose. Account or note deletion cannot reach copies already exported, downloaded, shared with another person, or retained in iCloud.

We use reasonable technical and organizational safeguards, including platform data protection and provider access controls, but no storage or transmission system is completely secure. Keep your device and account credentials secure and maintain independent copies of important work.

7. Retention and deletion

We generally keep account and synchronized workspace information while your account is active and as needed to provide the Service. Specific records may remain longer when reasonably necessary for security, fraud prevention, dispute resolution, legal obligations, backup integrity, or enforcing agreements. Service-provider logs and backups may age out on their own schedules.

You can start account deletion from the account menu by completing the in-app confirmation. The automated process attempts to revoke an available Apple credential, remove certain user-owned Storage objects, delete account rows for supported workspace and subscription/settings records, and delete the Supabase Auth user. It is not a promise that every copy disappears immediately.

Known limits include non-recursive or capped Storage listing, cleanup that can continue after an individual removal error, and records or provider data that are not currently covered by the automated handler, including some analytics, community-template/favorite, promotion, provider-log, and historical backup data. Local notes, media, audio, tutor history, exported copies, recipients' copies, and iCloud backups remain until separately removed from those locations. Account deletion does not instruct Google to erase prior inference records.

After using in-app deletion, email nablanotescorp@gmail.com if you want us to review and complete deletion of data under our control. We may ask you to verify account ownership. We will respond within the period required by applicable law and will explain any lawful exception.

8. Your privacy choices and rights

Depending on where you live, you may have rights to request access to, correction of, deletion of, or a portable copy of personal information; to object to or restrict certain processing; to withdraw consent where processing relies on consent; and to appeal or complain to a privacy regulator. You will not receive discriminatory treatment for exercising a privacy right.

You can edit certain account information in the Service, delete individual content, export note packages, and request account deletion in the account menu. For any other request, email nablanotescorp@gmail.com. Please identify the account email and the right you want to exercise, but never send a password or authentication token. We may verify your identity and authority before acting.

There is currently no in-app control that disables all necessary operational analytics while preserving the same account-based Service. You may stop future app collection by discontinuing use and deleting the app, subject to the separate deletion limits above.

9. Age, children, and education use

The Service is intended only for people who are at least 18 years old. It is not directed to children, we do not knowingly offer it to anyone under 18, and a parent or school cannot consent on a minor's behalf under these current terms. If we learn that an under-18 user provided personal information, we may suspend the account and take reasonable steps to delete information under our control. Contact us if you believe this has happened.

NablaNotes is a general study tool, not a service operated for a school or institution. We do not currently enter student-data agreements or claim to act as a "school official" under FERPA. Schools, teachers, and organizations should not require students to use the Service or submit education records without a separate written agreement and their own legal review. Do not upload another student's work, grades, disability information, or other education records without authorization.

10. International processing

NablaNotes is operated from the United States, and our providers may process information in the United States and other countries where privacy protections differ. If applicable law requires a transfer mechanism or additional protection, we and our processors will use the mechanism required for the relevant processing.

11. Changes to this policy

We may update this policy as the Service or law changes. We will post the revised version at this stable URL and update the date above. If a change materially affects how we use information already collected, we will provide additional notice when required.

12. Contact

Questions, concerns, or privacy requests can be sent to nablanotescorp@gmail.com.

NablaNotes
San Diego, California, United States