This document describes the current implementation and proposed service terms. It is not yet an effective launch policy. The responsible legal entity, full postal address, launch regions, legal bases and provider arrangements require owner and legal approval.
Waitlist and launch communications
Waitlist registration is open. The form requests your full name and email address, with country optional. We use these details for the waitlist, early-access updates and launch announcements you request. Joining does not create a mobile app account or guarantee early access.
Submitting an email address displays whether its registration is new, already confirmed, pending confirmation or inactive. This status is visible without signing in; no subscriber name, consent choices or other account details are returned. Duplicate registration submissions do not send another email. Pending subscribers can explicitly request another confirmation, limited to one request per address every 20 minutes and three per connection per hour.
A confirmation email will ask you to verify ownership before launch communications begin. Confirmation links are designed to expire after 24 hours and be usable once. Separate optional consent for ongoing product news and promotions is unchecked by default. We record consent choices, the wording version and timestamps, confirmation status, delivery metadata and unsubscribe events.
Preference links let you stop optional promotions or all waitlist and launch messages. Bounced or complained-about addresses will be suppressed. The waitlist uses the existing Easywan Supabase project for protected storage and Resend for email delivery. A keyed, non-public representation of the connection address supports submission rate limiting; raw connection addresses are not saved in the waitlist tables. Provider infrastructure may process its own request logs.
Email is sent through the verified easywan.app domain. Promotional bulk sending remains disabled. Provider agreements, subscriber retention and deletion periods and applicable legal bases still require final review. The existing mobile account-deletion flow does not by itself remove an independent website waitlist subscription. Contact support@easywan.app to request removal of waitlist records. Suppression records prevent further sending to blocked addresses. No retention period or compliance guarantee is established by this draft.
Who we are and what this covers
Easywan is a mobile-first productivity platform owned by Sundifu Group & Technologies, based in Bo, Sierra Leone. This notice covers the Easywan mobile app, its connected account services, receipt verification and this public website. The registered entity acting as data controller and its full postal address must be confirmed before launch. The brand name alone does not establish that legal identity.
The public website provides product information and support. It is not a consumer document editor. This notice distinguishes information kept on your device from information sent to cloud services. The features you use and the choices you make determine which information is processed.
Account and profile information
When you create or use an account, the authentication service processes your account identifier, sign-in credentials or provider identity, email where supplied, confirmation status and session information. Profile information can include the display name and avatar you choose. Sign-in providers, where enabled, also handle information under their own privacy terms.
This information supports sign-in, account recovery, access control and account deletion. Do not share passwords or one-time sign-in codes with support. Only use your own account or one you are authorized to manage.
Business details and document content
The app can hold business names and contact information, customer records, products and services, prices, currency choices, logos, signatures and stamps. Receipt and invoice content can include line items, dates, amounts and customer details. CVs, letters, letterheads and business cards can contain names, contact details, employment history and other information you enter.
Certificates, school or organization ID cards and invitations are planned additions. Their content may include recipient or member names, photographs, organization details, award information, signatures, event dates, venues and contact details that you choose to enter. The website does not collect that content through its feature previews. Processing for these builders will be reviewed against the released mobile workflows before they become available.
Documents and drafts also have operational metadata such as identifiers, type, creation or update time and sync state. Information selected for supported cloud workflows is stored in the dedicated Easywan backend. Files can include avatars, logos, signatures, stamps, document assets, scans, exports and QR images. Local-only work and exported files are separate from cloud copies.
You decide what to enter about other people. Share only information needed for your task and ensure you have the right to use customer details, photographs, signatures and other personal information. Avoid unnecessary sensitive information in documents and support requests.
Scans, OCR, QR and device permissions
Camera, photo and file access support the actions you choose, such as scanning a document, selecting an image or saving an export. Permission can be changed in your device settings. Refusing a permission may prevent the corresponding feature from working.
Scans and extracted text can contain personal information. Check extracted text before using it and review the destination before saving or sharing a file. QR content can contain a website address, contact information, plain text or Wi-Fi credentials. Encoding content in a QR code does not make it confidential: anyone who receives a readable code may access that content.
A scan or QR code is not automatically a public receipt verification record. Cloud processing and sharing depend on the particular action you take. If you deliberately send extracted text to Smart AI, the AI processing described below also applies.
Local work and cloud sync
Easywan uses local-first drafting for supported workflows. Signing in and using cloud features can send your selected account data, records and files to Supabase infrastructure supporting Easywan. Authentication, sync and official receipt issuance require a connection.
A draft on a device and its cloud version can differ while synchronization is incomplete. Before switching devices, reinstalling the app or deleting data, check sync status and export important work. Local app storage, external Files or Photos storage, cloud records and copies held by recipients have different deletion boundaries.
Public receipt verification
An official verification reference allows its holder to retrieve the current receipt status and approved fields: official receipt number, issuance time, currency and total. The public lookup does not expose the receipt body, customer contact details, line items or account identifier. Treat the reference as shareable access to those limited fields.
A status check is not independent proof that payment occurred or that an issuer has a particular legal identity. Voided or revoked receipts must not be represented as valid. Under the current account-deletion policy, private receipt records and verification records are removed; an old reference then returns Not found. That result does not disclose why a record is missing.
Smart AI and Google Gemini
Smart AI is optional assistance for supported Easywan tasks. It is being prepared for release and is not currently offered through this website. When enabled and you consent to a request, Easywan sends the text you submit and the bounded conversation context needed for that request through its backend to the configured Google Gemini service. Selected document text or form context requires the corresponding context consent.
Smart AI does not receive your entire saved document library merely because you open it. Do not submit private information that you do not want processed for the task. The app presents supported document changes for review before applying them. A response can be inaccurate; check its facts and wording.
Explicitly saved conversation history is account-scoped on the device, rather than a cloud conversation archive. The current app limits saved history to 20 chats and 40 turns per chat, and prunes entries older than 30 days when history is accessed. This is not a promise that unused device storage is erased on an exact calendar date. You can remove saved history using the app controls.
The backend keeps usage metadata such as request status, model, token counts and estimated cost for limits and service operation, rather than a prompt or document transcript in its usage tables. Google processing is governed by the applicable Gemini service terms and account arrangement. Provider retention, abuse monitoring, training treatment and international processing must be confirmed before activation; this draft does not promise zero provider retention or no training under every plan. See the dedicated Smart AI privacy disclosure for more detail.
Notifications and operational information
Where notification delivery is enabled and permitted, the service uses a push registration token, a random installation reference, platform, app version and permission state to route messages and respect preferences. This is not an advertising identifier. Device permissions and in-app notification preferences control available categories.
Account, notification and security events may be recorded to operate the service and investigate failures. Infrastructure providers may process request metadata, including network addresses and technical logs, to deliver and protect their services. The reviewed public frontend includes no advertising, visitor analytics or session-replay integration. It does not ask for access to your mobile documents.
Why information is processed
Processing supports the functions you request: account access, document storage and sync, receipt issuance and verification, optional assistance, notifications and support. Security and usage metadata also support abuse prevention, reliability and resource limits. This implementation does not add advertising profiles or sell document content.
Where data-protection law requires a lawful basis, the proposed mapping is contract necessity for requested core services, consent for optional processing where appropriate, legitimate interests for proportionate security and reliability, and legal obligation where a specific duty applies. This mapping requires legal review for the launch jurisdictions, including an assessment of legitimate interests. A device permission is a technical control and is not by itself a complete legal-basis assessment.
Service providers and access
Supabase supports the dedicated Easywan authentication, database, storage and server functions. Vercel hosts the website. Resend handles outgoing email, incoming business messages and delivery events. Authorized communications staff can access messages sent to info@easywan.app and support@easywan.app, including their replies, attachments and delivery metadata. Google Gemini processes optional AI requests when the service is enabled. Store platforms, enabled sign-in providers and notification delivery providers may also process information needed for their functions. Their precise contractual roles and final provider list require confirmation before launch.
Access controls and database policies restrict routine access to account data. Administrative features are designed around permission-limited metadata rather than browsing private document bodies. The administration workspace requires an authorized role and two-step verification. Reporting exposes protected aggregates, not private document bodies. This design should not be interpreted as a guarantee that no authorized infrastructure operator can access data when necessary for support, security or legal compliance.
There is no public document gallery in this website. Information you export or share with another person leaves the private account boundary. Any legally required disclosure should be limited to the applicable requirement; the owner must finalize procedures for such requests.
Security and international processing
Easywan uses authentication, access restrictions and private storage boundaries to protect cloud information. No transmission or storage method can eliminate every risk. Protect your device and account, review recipients before sharing, and report a suspected compromise at support@easywan.app. This draft does not claim end-to-end encryption.
Service providers may process data outside your country. Before launch, the owner must confirm processing locations, provider agreements and any required transfer safeguards, such as approved contractual arrangements where applicable. This notice does not invent a residency guarantee.
Retention and deletion
Account data and cloud documents remain available for supported account use until removed through applicable controls or account deletion. The approved account-deletion workflow locks the account, removes sessions and push registrations, deletes owned cloud files and records, and removes the authentication account. Background cleanup retries incomplete work, so an accepted request is not a promise of immediate completion.
The current scheduled retention job removes old push registrations after 90 days without an update, notification records older than 90 days, account audit records older than 365 days and completed deletion-job records after 30 days. These are operational cleanup thresholds, subject to scheduled execution and failures, not absolute erasure deadlines. Account deletion can remove linked data earlier.
Minimal security/audit records may remain after account deletion with the account actor reference removed. They are not a retained archive of private documents. Retention for other operational logs, provider backups, AI usage metadata and any legal hold must be finalized and disclosed before launch. Backup expiry and restoration handling are not asserted in this draft.
Your choices and rights
You can limit device permissions, review notification preferences, choose whether to use Smart AI, control the context you submit, export documents and request account deletion. Removing the app alone does not delete a cloud account. See Account deletion for the documented in-app steps and assistance through support@easywan.app. Waitlist email preferences are separate from a mobile account.
Depending on applicable law, you may have rights to access, correct, erase, restrict processing, object, obtain a portable copy, withdraw consent and complain to a competent data-protection authority. These rights can have conditions and exceptions. Withdrawing consent does not undo processing already lawfully completed.
Send privacy requests to support@easywan.app. Reasonable identity verification may be needed to protect your account; do not send your password. Applicable response periods, authorized-agent procedures and the relevant authority depend on the confirmed launch jurisdictions and must be included in the approved notice.
Children and policy updates
Age eligibility and any parent or guardian requirements remain subject to owner and legal confirmation. The launch policy must identify the intended age group and any required controls; this draft does not silently choose an age threshold. If you believe a child has supplied personal information improperly, contact support@easywan.app.
Before launch, Easywan will publish an effective date and approved notice. Material changes should explain what changed and when they take effect, with additional notice or consent where required. This review date is not an effective date.
Contact Easywan
For help or a privacy request, email support@easywan.app. Do not include passwords or sign-in codes.