Where information is processed

Drafts, normal Card Studio work and static QR codes are processed in your browser. Roman Urdu transliteration suggestions and optional whole-text conversion use the Google transliteration service when available, so submitted words or passages may be sent to Google. Urdu web fonts are requested from Google Fonts; the font request does not contain your editor or card text. Public sharing is different: nothing is uploaded for a public share until you explicitly choose Publish & Share.

FeatureProcessingStored or shared
Basic and rich editorsDrafting and formatting run locally; transliteration may use Google.Drafts may use browser storage; text is sent for conversion only when transliteration is used.
Urdu Voice TypingWrite Urdu asks the browser or operating platform to recognize Urdu speech after you press Start voice typing.Depending on the browser or platform, microphone audio may be processed by a provider-operated recognition service and an internet connection may be required. Write Urdu does not create its own audio recording or upload pipeline for this tool.
Product usage telemetryInstrumented product pages send first-party aggregate interaction events to Write Urdu. Public pages may also classify the current arrival into a coarse source such as Google Search, other search, direct/unknown, referral, campaign or internal navigation.Event type, normalized route/tool, coarse text-length and active-time buckets, input mode, export format, device class and an ephemeral tab-session identifier may be processed. Public-share telemetry normalizes all individual share routes to one generic route and does not transmit the share ID. Written text, filenames, clipboard contents, email, full referrer URLs, campaign values and user-agent strings are not part of these telemetry events. The arrival signal adds no persistent cross-session identifier.
Card StudioText and local backgrounds render in the browser during normal design work.Projects and source assets may be stored locally. They are not uploaded merely because you edit, download or share an image file.
Public share linksOnly after you explicitly choose Publish & Share, Write Urdu uploads the selected rendered card snapshot and the public data needed to display its short share page.The rendered PNG, public Urdu text, optional enabled attribution, source-tool/preset information, a random share identifier, a hash of the private management token and limited operational/moderation fields are stored using Write Urdu's Cloudflare services. If a local photo appears in the rendered card, it is naturally visible inside the uploaded published PNG; the original local source file and unrelated drafts are not uploaded as separate assets. A parent-share relationship may be stored when a recipient creates and publishes a new share so aggregate reproduction can be measured without linking that relationship to an analytics session.
Urdu web fontsFonts are delivered by Google Fonts.Normal request data such as IP address may be processed.
QR GeneratorYour QR content and logo are processed on your device.Projects may be saved in IndexedDB; no external QR service receives the content.
Contact and feedbackSubmitted form fields pass through a Write Urdu Cloudflare Pages Function and Cloudflare Turnstile before a private email notification is delivered.Only fields you submit are sent. Editor drafts, local images and browser-stored projects are not attached automatically. Cloudflare and Turnstile may process normal request data needed to deliver and verify the request.
Analytics, ads and embedded mediaThird-party providers may load on pages that include them.Providers may process technical information, cookies or ad events under their own policies. User-created public share pages are ad-free in the initial sharing release.

How to clear local data

Use the editor draft-history controls, Card Studio reset controls or QR Generator reset controls. You can also clear site data for write-urdu.com in browser settings. Downloaded files must be deleted separately from your device. The anonymous product-telemetry session identifier is stored only in session storage and expires with the browser tab/session. Coarse arrival telemetry does not create a browser-storage identifier.

If you have published public share links, clearing local browser storage can remove the management tokens used for self-service deletion. It does not automatically remove the already-public server snapshot. Delete managed public links before clearing site data when you want those published snapshots removed.