NoteLog, the operator and scope of responsibility
NoteLog is a cross-platform note-taking and handwriting service delivered through the app, APIs, notelog.website and supporting infrastructure/integrations. Depending on the context, the operator may act as a personal-data controller, processor or another role defined by applicable law. This policy covers data processed through the NoteLog service.
To enable user requests and regulatory contact, the verified legal operator, business address and privacy contact must be published on the website/app before formal release. This policy does not invent an unverified legal entity, email address or mailing address.
The operator/contact details remain subject to verification. This document does not replace legally required identification and accessible data-request channels.
Scope, personal data and local/cloud distinction
This policy applies to website visitors, signed-out users, signed-in users, purchasers and invited collaborators. Personal data is information relating to an identified or identifiable individual under applicable law; your documents may also contain other people's data.
- Local: notebook/file data stays in device storage and is not automatically sent to NoteLog cloud.
- Cloud: content you choose to store in the cloud is transmitted to API/storage services and may sync based on account and sharing permissions.
- Platform data: authentication, sessions, push tokens, transactions or advertising information may be processed even if no notebook is uploaded.
- Integrations: enabling AI/MCP or sharing may transmit the selected content to relevant services or recipients.
Categories of data that may be processed
The table differentiates data by function and origin. Whether a data type is accessed or transmitted depends on user actions, device permissions, app version and server configuration. “May” does not mean NoteLog automatically reads all of your personal information.
| Category | Examples and when generated | Main purpose |
|---|---|---|
| Accounts and identity | User ID, name, email, optional phone, Google/Apple sign-in identity, profile status | Register/sign in, show profiles and link entitlements |
| Authentication and sessions | Authentication records, verification values, session markers/tokens, sign-in time | Protect access, resume sessions and prevent impersonation |
| Notebooks and canvas | Notebooks/projects/pages, strokes, objects, titles, descriptions, notes and indexes | Display, edit, search and synchronize |
| Documents and media | Photos, PDFs, scans, audio, video/files you intentionally import | Import, view, process, store, export/share |
| Sync metadata | Notebook/page IDs, revision numbers, operation commands, sync status and timestamps | Resolve updates, errors and collaboration |
| Collaboration and access | Owner/member IDs, invitations, view/edit/delete permissions and workspace information | Enforce authorization and deliver shared content |
| AI and MCP integrations | Prompts, selected pages/files, generated results, connection identifiers, task logs | Process requests, meter allowances, enforce access and diagnose errors |
| Purchases and entitlements | Plan/product IDs, store, verification records, purchase/expiry time, status and quotas | Validate purchases, renewals and allocate plans |
| Devices and notifications | FCM/APNs tokens, platform, permission state and notification delivery context | Send notifications and route to devices |
| Ads and SDK measurement | Advertising identifiers where available, SDK device/app/ad event information | Serve, limit and measure advertising as applicable |
| Website and security | IP, user agent, HTTP requests, login/language cookies, error codes and server logs | Serve pages, remember preferences and secure systems |
Data sources and whether providing data is mandatory
- You provide it: registration, profile edits, notes, attachments, support requests, AI prompts and sharing choices.
- Your device/OS supplies it when you grant permission or use a feature: selected images, camera/micro data, push tokens, files and device attributes.
- Identity providers or stores supply it: permitted sign-in information and transaction identifiers/proof/status.
- The system generates it: notebook/page IDs, revisions, connection status, timestamps, errors and authorization logs.
Information needed for authentication, payment, cloud synchronization or security may be technically necessary for the relevant feature. Refusing optional data or device permissions should only limit dependent features rather than automatically blocking all local content.
Purposes and legal bases of processing
Data is processed as necessary to provide the service, perform user requests, secure systems, manage subscriptions and meet legal obligations. The precise legal basis depends on the activity and applicable law, not one blanket basis for every data type; optional processing needs consent where the law requires it.
| Activity | Purpose | Basis to assess |
|---|---|---|
| Account, cloud, synchronization | Deliver the feature requested by the user | Contractual necessity/other applicable lawful basis |
| Plans and transaction records | Validate/settle payments and prevent fraud | Contractual performance and legal obligations |
| Security and abuse prevention | Stop unauthorized access and diagnose faults | Data-security duty or legitimate interest where lawful |
| AI, sharing and integrations | Process user-initiated instructions and necessary transmissions | User instruction/consent and appropriate legal basis |
| Optional advertising/tracking | Ad delivery and measurement by SDK/region | Consent or another basis if law permits |
Device-only data, caches and backups
Local notebooks, SQLite/Drift databases, caches, previews, image resources and preferences may be stored in the app sandbox or operating-system-managed folders. Working on local-only content does not automatically upload all of it to the cloud; independent services such as sign-in, FCM or advertising SDKs may still operate.
Clearing caches can remove temporary files, while clearing app data or uninstalling can lose local content without an export. OS backup, if enabled, is subject to Apple/Google policies and is not a separate NoteLog backup guarantee. Files you export outside the app are not within NoteLog's deletion control.
Cloud storage, R2, revisions and real-time sync
When you choose cloud storage, page contents, objects, attachments and necessary metadata may pass through APIs, WebSocket/SignalR, databases and object storage such as R2. Notebook/page identifiers, revision numbers and operations support updates to authorized devices and users.
A pending or rejected operation is not equivalent to durable persistence. Queued objects, backups, caches, logs and disconnected sessions may have different deletion lifecycles. A UI deletion action should not be treated as proof that every technical copy disappeared immediately.
Device permissions: triggers, use and denial
The app includes a pre-permission explanation flow before OS authorization. Users can inspect, grant or revoke permissions in iOS/Android settings; limited grants (for example photo library access) limit access to the OS-selected scope. Declared permissions are not used solely because they exist.
| Permission/source | When used | If denied |
|---|---|---|
| Camera | Photo capture and multi-page document scans that you initiate | Camera capture/scanning unavailable; other features can still work |
| Photo library | Select images for notebooks/attachments | Images outside the allowed scope unavailable; limited access stays limited |
| Microphone | Recording or audio features you explicitly start | Microphone recording unavailable |
| Files/PDF | OS picker for importing PDF/other files; exporting through supported actions | Import/export to restricted locations may be unavailable |
| Notifications | Push via Firebase Cloud Messaging/APNs and local notifications if used | Denied notifications will not appear; notebook functions can remain available |
| Location | Only when a location-requiring feature is used and permitted | Dependent location feature unavailable |
| Advertising tracking (iOS ATT) | Request tracking permission where relevant under Apple's rules | Tracking denied; ads may still be shown |
Location and advertising-tracking permissions must be checked against actual feature use before declaring data collection in App Store Connect or Google Play Console.
Photos, PDFs, video, audio and scanned documents
Selected images, scans, PDFs, recordings and attachments can contain names, signatures, faces, addresses, photo location metadata or other sensitive information. NoteLog processes them to decode, display, edit, convert and store them where you choose. Do not upload confidential documents to the cloud or send them to AI without appropriate authorization.
Scanning, rotation, previews and PDF handling may create intermediate files. OS temporary storage, app caches and cloud objects can have different lifecycles and deletion schedules. Files exported to other apps are subject to recipients' practices.
AI: submitted data, output and controls
AI features may process selected text, page images, prompts, chat history, metadata and files to produce summaries, titles, solutions, questions or responses. Depending on the task and configuration, selected content may be transferred to model providers outside NoteLog. Verified provider identity/category, processing region, retention and training-use terms must be disclosed when established.
- Send only data necessary for the requested task; avoid secrets, other people's data, or health/financial information without a lawful basis.
- Verify AI output before storing/sharing it; AI logs may be needed for troubleshooting and token metering.
- Personal data sharing with AI providers outside NoteLog requires explicit disclosures/permissions where law or platform rules demand.
- Do not assume that content is never used for model training without verification of every provider's terms and configuration.
MCP connections, external AI access and tool logs
Authorizing an application/agent through MCP or an applicable authorization flow may allow access to and operations on cloud notebooks. The backend must enforce scope for each tool call; logs may include time, tool name, outcome, notebook/page IDs and operation metadata for security, support and troubleshooting.
Review the connected application's identity, scope and write/delete capabilities before consenting; revoke unneeded access through connection management when available. Disconnecting prevents future access but may not recall content previously sent to external systems governed by their own policies.
Google Mobile Ads and tracking choices
The iOS/Android app integrates Google Mobile Ads. Subject to SDK behavior and settings, ads may involve app/device information, IP addresses, ad-delivery signals, interactions and advertising identifiers when permitted. Exact data types and sharing must be validated against SDK disclosures and production configuration before completing App Privacy/Data safety labels.
iOS supports App Tracking Transparency (ATT), but ATT differs from regional legal consent for advertising/data processing. Denying ATT does not necessarily remove all ads; nonpersonalized ads may remain. The app has preference logic for premium users to toggle ads where a control is provided, while regular users cannot disable ads through that preference. The actual user interface must be verified before claiming the toggle is available.
Regional advertising consent management (for example EEA/UK) and all advertising sub-processors have not yet been fully verified. Appropriate consent/disclosure must be in place before considering this policy and store declarations complete.
Push notifications, FCM/APNs and device association
When notification services are configured and permission is granted, Firebase Cloud Messaging/APNs may generate device tokens and registration state to route notifications. The backend may associate tokens with user IDs for relevant account/content notifications; tokens may refresh during the SDK lifecycle.
You can disable notifications in device settings. This can stop visible push messages but may not immediately remove server-side token records; token revocation, sign-out and account deletion require separate handling. Local-only notebook content is not used in a notification without a relevant feature workflow.
Payment data and entitlement verification
In-app purchases are handled through Apple App Store or Google Play billing. NoteLog may receive store, product IDs, transaction IDs/receipts/purchase tokens, purchase/expiry times, status and entitlement information to verify purchases and prevent receipt fraud. Store purchases do not require you to enter full payment card details directly into NoteLog.
Cancellation, refunds, charges, taxes, transaction-record retention and billing support are governed by applicable store terms and laws. You can also purchase plans from the NoteLog homepage using bank payments. This payment method is currently available only to users in Vietnam. In the future, we plan to expand payment options for users worldwide.
Recipients, processors and third parties
Data should be transferred only as needed for a feature, legal compliance or sharing choices. Embedded SDKs may process information directly through their providers; NoteLog must reconcile provider documentation and agreements with actual use.
| Recipient/category | Potential role | Data involved |
|---|---|---|
| Apple / Google Play | Subscription billing, renewal and refunds | Store account, purchase proof and transaction status |
| Google / Firebase | Authentication and push notifications | Related identifiers, tokens and authentication/notification data |
| Google Mobile Ads | Ad delivery and measurement | SDK/ad data according to configuration and permissions |
| Cloudflare R2 / cloud infrastructure | Storage of cloud notebook objects/files | Files and necessary technical metadata |
| AI model providers | Processing user-selected prompts/context | Task-specific AI input |
| Applications/agents via MCP | Authorized notebook operations | Content and metadata within granted scope |
| Invited collaborators | View/edit within access permissions | Shared notebooks, pages and related sharing information |
Specific AI processors, infrastructure locations, data-protection agreements and final SDK inventory must match production configuration; this table is not a claim that all providers host data in Vietnam.
International transfers and regional protections
APIs, R2 infrastructure, Firebase, Apple/Google and AI or integration providers may process data in countries or regions different from your residence. The actual transfer depends on deployment and provider selection; consider this before placing sensitive documents in the cloud or AI.
Transfer assessments, disclosures, lawful bases, agreements and safeguards must comply with applicable rules, including Vietnam's Personal Data Protection Law 91/2025/QH15 and Decree 356/2025/NĐ-CP where relevant. This policy does not replace the operator's legal compliance documentation or filings.
Security safeguards and technical limitations
Observable architectural safeguards include account/token authentication, server-side authorization for notebooks/workspaces and tools, HTTPS for the production website, HttpOnly/SameSite authentication cookies, logging and transaction verification. Session management, updates and infrastructure operations also affect security.
No online system is absolutely secure. Cloud content may be processed by the service to deliver features, so this policy must not be read as a promise of zero-knowledge end-to-end encryption. Protect your device and account, review sharing permissions and avoid publishing confidential material through public support channels.
Retention periods, temporary files, backups and logs
Retention depends on purpose: while an account/notebook is in use, to complete queued tasks or incident handling, and as needed for disputes, fraud prevention or legally mandated records. Data removed in the UI may require additional time to clear R2 objects, caches, processing queues and backups.
| Data | Retention end principle | Must be finalized before launch |
|---|---|---|
| Profile/authentication | Account lifecycle, security and lawful duties | Account deletion workflow and specific SLA |
| Cloud notebooks/R2 objects | Notebook/storage lifecycle, queues and cleanup | Soft-delete, object and backup purge periods |
| Local notebooks/caches | Device data state and user action | Reliable export, backup and deletion guidance |
| AI/MCP history and API logs | Only as needed for support, fraud prevention and cost control | Retention by log table and purge mechanism |
| FCM tokens/connections | Until expiration or account-related revocation | Revoke on logout/account deletion |
| Purchase records | Accounting, tax, fraud prevention and applicable law | Minimum/maximum retention period |
| Website cookies | Login 7 days sliding; language preference 1 year | Keep aligned with server configuration |
Accounts pending deletion have a 90-day period during which users may cancel the request by signing in again, as described in the Account Deletion section. Retention periods for other data, apart from the cookies above, depend on system settings and applicable legal obligations.
Access, correction, erasure, withdrawal and complaints
Subject to applicable law and data category, you may request notice, access or a copy, correction, withdrawal of consent, objection/restriction, deletion or assistance from competent authorities. Some rights may be limited lawfully to protect others' rights or comply with retention duties.
- Determine whether the request concerns your entire account or a specific notebook, page, file, transaction, AI history or MCP connection.
- Use available self-service controls or the officially published support/privacy request channel when established.
- Provide only the minimum identity verification data necessary; never publicly disclose passwords, tokens or OTPs.
- NoteLog must assess the request, data scope and lawful retention obligations and communicate the outcome or grounds for refusal where required.
Account and associated-data deletion requests
Deleting your account is an action that permanently ends your future use of NoteLog. After requesting deletion, you have 90 days to change your mind by signing in again. During that period, signing in will display a warning that your account is pending deletion. If you confirm that you want to sign in, the deletion request will be canceled. If you request deletion again, a new 90-day waiting period will begin.
You can request account deletion in either of the following ways:
- In the NoteLog app: Profile → Privacy & Security → Delete Account.
- On the NoteLog website: Sign in → Profile → Delete Account.
When you choose to delete your account, a confirmation warning will appear. After you confirm, you will be signed out and your account will enter the pending-deletion state.
If you do not sign in again within 90 days, your account and its associated cloud data will be permanently deleted through the data-deletion process. Back up all important data before proceeding. To the extent permitted by law, NoteLog is not responsible for data permanently deleted at your request and cannot restore it after your account has been completely deleted.
Deleting your account does not automatically cancel subscriptions billed through the App Store or Google Play. Cancel them in the relevant store. Some transaction records or other information required by law may be retained to the extent legally necessary.
Privacy choices, permission withdrawal and local deletion
- In device settings: revoke camera, microphone, photos, location, notifications or ATT where applicable.
- In the browser: clear authentication/language cookies and adjust Accept-Language.
- Within NoteLog: choose local/cloud storage, control sharing/revoke MCP connections and adjust advertising when your plan permits.
- In App Store/Google Play: manage subscriptions, cancel renewals and review or request refunds.
- For device-only content: use available export/delete controls and back up before clearing data.
Withdrawing consent for optional processing does not automatically erase all data lawfully processed beforehand. Where no lawful retention basis remains, users may request deletion through applicable procedures. Revoking device permissions can disable the affected feature from that point.
Children's information and minors
NoteLog must not be used to unlawfully collect children's data. Where required by law, minors or processing of children's personal data require guardian authorization and additional safeguards. Users, teachers and organizations entering children's information in notebooks must have an appropriate lawful basis and purpose.
If children's information was entered unlawfully, an authorized guardian may request review and deletion through the official privacy channel once published; the request must include appropriate identity/authority verification.