Flowlilt Privacy Policy

Effective date: 2026-10-18 App: Flowlilt (com.servenzo.flowlilt) Publisher/developer brand: Servenzo Privacy contact: [email protected] Public policy URL: https://servenzo.com/apps/flowlilt/privacy-policy

This policy describes the local sample Flowlilt R1 implementation. A future live market integration, account, cloud feature or another Servenzo app is outside this version's data practices.

Operator, hosting and internal testing

Servenzo operates Flowlilt. Contact [email protected] for privacy questions. This release is fully local: it does not contact the shared app API, create a cloud account or upload app records. Its market records remain fictional samples; no external market provider is connected.

The public policy and support website is hosted in the United Kingdom. Cloudflare provides its DNS and traffic proxy and processes network addresses, request timing and security information when you visit the website. Google Play separately handles app distribution and tester accounts. Opening a website, sending a support email or deliberately exporting information uses the provider you select; these actions do not grant Servenzo access to the app's local database.

Information handled locally

The app bundles original fictional options prints, finite replay datasets and educational examples. Sample execution and expiry dates belong to those fixtures; the app does not obtain live market records or a brokerage portfolio.

The app stores your filter and visible-field preferences, time-display settings, presets and default workspace, immutable bookmarked sample snapshots, private notes, working drafts and captured failed-save requests, saved replay positions, setup choices and optional recent symbol/contract searches. Search history is enabled initially and can be turned off and cleared separately. There is no age, identity, account, brokerage, holding or provider-credential form.

Optional local task diagnostics are off by default. If enabled, the app keeps bounded event categories, duration buckets and generated opaque local IDs. The diagnostic event schema excludes note bodies, raw searches, symbols, contracts, holdings and credentials. Turning diagnostics off clears its retained events and leaves core features available.

Use and transfer

Local data supports inspection, research, replay, recovery and your selected presentation choices. No live API, login, server synchronization, telemetry upload, advertising, purchase or billing flow is configured in this R1 runtime. The selected Realtime Options backend was reviewed as a future contract reference only; this app does not call it.

An export is initiated by you after scope and JSON preview. The app sends the selected export bytes to your chosen system document destination, or requests a browser download on web. That destination may be a cloud provider under its own practices. Support summaries are separately previewed and omit raw private research and sensitive identifiers by default; counts and consented content-free events are optional. The app does not automatically send the summary or a support message to Servenzo. Raw recovery is a separate explicitly sensitive export that may include unknown private records.

Storage and security

Research is stored locally in an app-isolated transactional database. It is plaintext, not a separately encrypted vault, and no local PIN or encryption service is provided by Flowlilt. Platform isolation and your device/account protections apply. Avoid storing secrets, credentials or sensitive financial documents in notes or recovery exports.

A successful acknowledged save is retained across restart. Ordinary working drafts are separate from immutable failed-save requests; a newer edit can coexist with a captured failed save. Retry commits only the captured request, while an ordinary draft requires explicit Save. Canceling Retry is durably acknowledged and retains working text as an ordinary draft. Unsupported or damaged data is retained for read-only recovery rather than silently reset. Legacy source preferences are preserved during migration; no historical market prints are invented.

The reviewed Android application source disables ordinary automatic app backup. Final signed-artifact and platform backup/restore behavior must still be verified; OS snapshots, device management, browser storage and independent copies are outside an app-level deletion guarantee.

Retention, capacity and deletion

The visible sample window retains at most 200 prints and the pause queue at most 100, with disclosed dropped-history counts. The bundled catalog is finite and versioned. Local research capacity is limited to 100 presets, 2,000 bookmarks, 2,000 notes, 2,000 working drafts and 2,000 captured pending requests with a 16 KiB UTF-8 body limit, 20 recent searches and 32 replay versions. Capacity failures are visible; private research is not silently evicted to simulate a successful save. Optional diagnostics retain at most 256 rolling events.

Use the privacy centre to review selected export/deletion scopes and current counts. Preset deletion offers a bounded Undo. Clearing searches does not delete bookmarks or notes. Removing bookmarks alone keeps independent notes; removing notes also removes their working drafts, captured pending requests and preserved note-bearing recovery material within the selected app scope, with durable cancellation to prevent an old Retry from reviving deleted text. External exports, source copies and OS/provider backups must be managed separately.

You can also clear installation data using Android Settings > Apps > Flowlilt > Storage > Clear storage (wording varies). Uninstalling normally removes that installation's app-local data. Neither action can delete independently controlled exported files or backups. There is no Flowlilt server account to delete, no server retention process to claim completed and no current billing subscription to cancel. If accounts or billing are introduced later, account deletion, server retention and separate billing cancellation must be explained before release.

Device access and external links

The reviewed main Android manifest requests no runtime or special permissions. Flowlilt does not request camera, microphone, contacts, location, photo-library or advertising-ID access. A user-selected export uses the system document destination rather than broad file access. Actual merged release permissions and SDK behavior need separate qualification.

Source URLs in educational cards and planned support/privacy URLs identify external resources. The sample app does not automatically fetch their contents or authenticate to those services. If you independently open a link or send email using another app, that provider handles the request under its own terms.

Audience and financial-information boundary

The publisher intends Flowlilt for ages 13 and older. It does not ask for a birth date or create child profiles. Fictional records and source-linked candidate explanations are for interface exploration and education; they are not investment advice, a suitability assessment, authentic historical exchange data, trading orders or a performance promise. Independent educational review and human usability qualification remain release gates.

Privacy questions and changes

Contact [email protected] with privacy questions. Do not include note bodies, account credentials, holdings or sensitive identifiers in an initial message. A support email is sent through your selected provider, not automatically by the app; it does not grant access to your local database.

Before adding a live provider, account, analytics, advertising, cloud synchronization, notification or billing feature, update this policy, the in-app explanation and the applicable store declarations to match the actual distributed behavior.

Current local R2 increment — 20 October 2026

The isolated local case workspace stores private questions, hypotheses/alternatives/contradictions, typed observation/assumption/inference/unresolved entries, exact fictional source/dataset/version/as-of references, versioned checklist templates and done/skipped reasons, review/snooze/outcome/reflection choices, private replay checkpoints and selected weekly summaries. Case edits do not alter source prints or reveal unseen replay data. Missing evidence stays unavailable. Everything remains fictional/sample research UI; no selected external backend, market socket, login or provider API is contacted. Export/hide/delete of owned reflection remains free; there is no profit ranking or prediction claim.

The new feature state remains app-scoped and local. Explicit JSON/file/clipboard exports are independent private copies; recovery can contain active or captured unacknowledged inputs. Deleting local feature data does not erase exports, OS/provider originals, separate app accounts or another product. Provider, installed-device, signed-release and store/public-policy qualification are not inferred from local tests.