Privacy policy: your local workspace and site account

The short version

The handwriting studio renders your text and imported fonts in your browser. Its latest draft is stored on the current browser and device. That draft is not automatically synchronized with a site account or sent to an AI model for handwriting training. Account, support and payment features are separate services and can require server-side processing.

This policy describes the current product workflow. It does not mean that loading a website creates no network activity: the browser still requests pages, images, bundled fonts and other site resources.

Text, TXT imports, fonts and exported pages

When you type, paste or import a plain TXT file in the studio, the text is used to render your handwritten-style pages locally. Imported font files are loaded for that browser workspace. The studio currently accepts text up to 12,000 characters and does not directly import Word or PDF documents.

Downloading a PNG exports the selected page to your device. Printing or saving all pages as a PDF uses your browser and the print destination you select. If you choose a network printer, a system print service or a third-party destination, that destination handles the document according to its own settings and policies.

Local drafts and browser preferences

The studio uses browser storage to keep a local draft. Clearing site data, using private browsing, resetting a browser profile or changing devices can remove access to saved work. A site login does not create cloud draft synchronization. Save important text and exports separately, and keep any font file you need to recreate the result.

The site can also use cookies or browser storage for language, appearance, authentication and other functional preferences. You can manage these through browser settings, but disabling them may affect sign-in or preference persistence. On a shared device, remove personal drafts and sign out after use.

Accounts and support

If you create an account, the service processes the account details you provide, authentication information and records needed to maintain access. A connected sign-in provider can share the identity details required by its sign-in flow. Account access is separate from the browser-local studio draft.

If you send a contact request, submit a support ticket or attach material to a support conversation, the information you deliberately submit is processed to handle that request. Do not include passwords, payment card details or confidential text that is unnecessary for support. Sending a screenshot or draft through support is different from simply editing it in the studio.

Payments and optional services

The public studio does not require payment to begin. If a separately offered paid service is enabled and you choose to purchase it, the service and the selected payment provider process the transaction details necessary to handle the order, settlement and related support. Payment records are separate from your local handwriting draft. Review the displayed product and provider terms before purchasing.

Optional integrations or analytics, if enabled by the site operator, can process usage information according to their configuration. This policy does not promise that every deployment uses the same providers. Do not assume that a local studio draft is automatically included in analytics or payment records.

Operational information and access

Serving the site can create technical records such as request time, IP address, browser information and errors. These records help operate the service, investigate failures and protect account access. Server-side account, support and order information is available only through the service’s configured access controls and providers needed for those functions.

There is no single retention period for all information: browser drafts remain subject to your browser storage, while server-side records depend on their purpose and applicable requirements. We do not promise that deleting a browser draft deletes an account or an order, or that closing an account removes a copy you previously downloaded.

Questions and requests

Use the contact page for questions about this policy or requests concerning account and support information. Describe the relevant account or request without sending passwords. We may need enough information to verify that a request concerns your own records. Options and rights can depend on your location and the information involved; this page does not replace any rights that apply to you.

Updates

We may update this policy as the product changes. The date at the top identifies this version. Review changes before using newly introduced connected or paid features.

Signature tools and PDF files

The signature generator processes your typed name, freehand strokes, signature photos and PDFs in your browser. It downloads self-hosted font files but does not send your entered name or document to a signature service. Photo cleanup creates a local vector of detected ink. PDF signing inserts a visible signature image and optional date; it does not issue a cryptographic signing certificate.

Using “Save on this device” stores the selected signature and appearance in this browser’s local storage. Saving is optional. Use “Remove saved signature” to delete it, especially on shared devices. Clearing browser storage also removes it. A saved signature does not sync across devices. Exported files are managed by your browser and operating system.