Privacy notice

Who is responsible

Little Now is operated by Amalis Company for Designing and Programming Specialized Software, a Kuwait Single Person Company based in Rumaithiya, Hawalli, Kuwait (Commercial Registration No. 548750; Commercial Licence No. 2026/10199). For personal information that Little Now actually receives, such as a waitlist request or an email you send, Amalis Company for Designing and Programming Specialized Software is the data controller or business responsible for deciding why and how that information is used.

You may have seen a different name at the point of install. Google Play shows Amalys Co, which is the same company, as Play's verified trader record for that developer shows. The App Store shows Thekrayat Husain, an individual who holds the Apple developer account on the company's behalf. The company named above is the one responsible for your information in both cases.

Contact: support@littlenow.app. Please use the subject “Privacy request” for access, correction, deletion, objection, or consent withdrawal requests.

Little Now does not receive your on-device journal content. We cannot inspect, recover, correct, or delete a copy we do not hold.

Website, waitlist, and email data

This website has no user account. It has no advertising network, session replay, social tracking plug-in, or browser storage used for analytics. Neither the waitlist nor the contact form asks for precise location, payment information, or sensitive personal information, and please do not put any in the message box.

Why we use website, waitlist, and email data

Providing an email address is optional. If you do not write to us, by the contact form or by email, we cannot reply. There is no other consequence.

We do not use website or email information for automated decisions or profiling that produces legal or similarly significant effects.

How long data is kept

• Website request and security data: Cloudflare keeps this according to the service configuration and the retention periods in its own policies. Little Now does not export it into a separate visitor database.
• Support and other correspondence: normally for up to 12 months after the last exchange, then deleted unless the issue remains open or a longer period is reasonably needed for legal, fraud, or security reasons.
• Contact form messages: normally for up to 12 months after the last exchange, then deleted unless the issue remains open or a longer period is reasonably needed for legal, fraud, or security reasons. You can ask us to delete one sooner.
• Launch waitlist records: until the requested launch email is sent or 24 months pass from the request, whichever happens first. Records that reach 24 months are removed during the next monthly retention check, no more than 31 days later. If you withdraw, we mark the record unsubscribed and keep it only until that same deadline so another unverified form submission cannot reverse your choice.

Backups maintained by an email or hosting provider may take additional time to cycle out under that provider’s documented backup schedule.

Cookies and similar technologies

Little Now does not use advertising or analytics cookies and does not use local storage or session storage to track visitors. Cloudflare may set a strictly necessary cookie when a security challenge or traffic-protection feature requires it. These technologies are not used by Little Now for advertising or cross-site profiling.

Submitting a form on this site does not add a Little Now cookie, local storage, analytics beacon, or advertising tracker. Its D1 record is server-side storage, not storage placed in your browser.

Read the cookie and technology notice for the current categories, purposes, and choices. If a non-essential technology is added in the future, it will not be activated for visitors who require prior consent until an appropriate choice is provided.

Recipients and international processing

We disclose limited information only when needed to operate the services:

• Cloudflare provides website hosting, network security, waitlist processing and EU-restricted D1 storage, and email routing.
• The receiving email provider stores and delivers messages sent to support.
• Brevo delivers the launch email, and delivers contact form messages to our support address. It receives the address and the message at the moment of sending, and records whether delivery succeeded.
• Professional advisers or public authorities may receive relevant information when reasonably necessary to protect rights or comply with law.

We do not sell personal information. We do not share it for cross-context behavioural advertising or targeted advertising. We do not let third parties track you across unrelated websites through this site.

Little Now is operated from Kuwait, and service providers may process information in other countries, including the United States and the European Economic Area. Cloudflare states that its data processing addendum includes the European Commission’s Standard Contractual Clauses and the UK transfer addendum. You may contact us to ask for more information about applicable safeguards.

Waitlist records are stored in a Cloudflare D1 database restricted to the European Union. Cloudflare may still process ordinary request and security data at its network locations. The launch email itself is delivered by Brevo, a French company that stores and processes this data on servers in the European Union, so sending it does not transfer your address outside the EU. Your address is given to Brevo only at the moment the launch email is sent, and for no other purpose.

Your privacy choices and rights

You may ask us to access, correct, or delete personal information we control. Depending on where you live and which law applies, you may also have rights to restrict processing, object, receive portable data, withdraw consent, appeal a decision, and complain to your local privacy regulator. We will not discriminate against you for exercising a privacy right.

Send the contact form with “Privacy request” chosen as the subject, or email support@littlenow.app with the same words in the subject line. We may ask for information needed to verify that the request concerns you. Where GDPR or UK GDPR applies, we aim to respond within one month, subject to lawful extensions.

The launch email carries an unsubscribe link, and mail apps that offer their own unsubscribe button will use it. Either one takes effect immediately and needs no reply from us. Before the email is sent, or if a link does not work, email support@littlenow.app with the subject “Unsubscribe” and we will remove the address by hand. Withdrawal does not affect processing that was lawful before withdrawal.

Do Not Track and Global Privacy Control

Browsers may send Do Not Track or Global Privacy Control signals. Because this site does not sell personal information, share it for targeted advertising, or run cross-site advertising trackers, those signals do not change the site’s behaviour. We will reassess this if our practices change.

For on-device journal content, use the app’s own export, edit, and delete controls. Little Now cannot fulfil a server-side request for content it never receives.

The Little Now mobile app

The app has no Little Now account, content server, advertising service, or third-party analytics service. It does not upload your journal entries, child details, photos, voice recordings, videos, or face measurements to Little Now.

What stays on your device

• Your children’s names, birthdays, and optional photos.
• Your memories, dates, favourites, prompts, snapshots, and answers.
• App-owned copies of photos, voice recordings, videos, and thumbnails.
• People you name and the optional face measurements described below.
• Your settings and small on-device usage counts used to adjust the interface.
• A short list of any failures the app hit, which you can read out to us or clear.

Optional on-device face recognition

If you deliberately add a photograph of someone for recognition, a model inside the app reads it on your phone. The app keeps 128 numbers describing the face. It does not upload the photograph or those numbers. Removing the person erases their numbers. A possible match is presented as a question and is never attached to a memory without your confirmation.

A device backup may copy the numbers, and a Little Now export includes them. Treat an export with the same care as a family photo album.

App update requests

The app checks Expo for corrected app code at launch and when it returns to the foreground. The request includes ordinary network information such as an IP address, plus the platform, update protocol and API versions, update environment, runtime version, production channel, and a persistent random EAS client identifier. If an early startup failure occurred, Expo Updates may also include a technical fatal-error message limited to 1,024 characters.

No journal field, photo, recording, video, or face measurement is attached to the update request. Expo’s privacy policy applies to its processing: expo.dev/privacy.

Permissions

• Photos: a system picker lets you choose an attachment without broad library access. Older library references may require access when reopened.
• Camera: used only when you capture a photo or video inside the app.
• Microphone: used only when you record audio or video that needs it.
• Notifications: reminders are scheduled locally. Little Now does not register a remote push token.

Subscriptions and payment

When the billing provider connects, the app asks Apple or Google for available products and active purchases. Apple or Google handles subscription payment. Little Now does not receive your card or billing address. The app receives product identifiers, localised prices, entitlement status, and available renewal details needed to show and restore the subscription. Apple’s or Google’s privacy terms apply to the store connection and transaction.

Backups and exports

iPhone and iPad: eligible app data can be included in iCloud Backup if you enable it and the backup completes. Little Now cannot see whether it is current or guarantee what Apple restores.

Android cloud backup: beginning with build 4 on runtime 2, the database is eligible while six app-owned media folders are excluded. A restore may bring back writing, dates, people, and settings without app-owned photos, thumbnails, recordings, videos, avatars, or old face crops.

Android device-to-device transfer: on Android 12 and later, separate transfer rules leave eligible files, including media, available to a direct transfer. Actual results depend on Android and the device maker. Earlier Android versions exclude the same media folders.

Your export: Export everything creates one portable file with active journal records and every present app-owned media file referenced by those records. Deleted, unreferenced, or already missing files are not included. Once you move that export elsewhere, the destination service’s terms apply.

The automatic copy: in Your data you can turn on an automatic copy. On iPhone it writes a Little Now folder into your own iCloud Drive; on Android it writes into a folder you pick once, such as one synced by Google Drive or Dropbox. The copy holds the same readable JSON as an export beside every app-owned media file, is kept current while you use the app, and only ever adds: deleting in the app does not delete from your copy. It lives in storage you own, under your own account and that provider’s terms; nothing is sent to us. Turning it off stops future runs and touches nothing already there.

Deleting app data

• Deleting a memory erases its app-owned recordings and photos.
• Deleting a child erases their memories and related app-owned files after confirmation.
• Removing a person erases their face measurements.
• Deleting the app removes its on-device container. Exports, the automatic copy in your own cloud storage, and copies already held in a platform backup remain until deleted there.

Biometric data: retention and destruction schedule

This section is the written, publicly available schedule for the face measurements the app can create. Some biometric privacy laws require one to exist and to be published rather than described on request, so here it is, separately from the general account of deletion above.

What is covered

Only what the app creates when you deliberately add a person so it can recognise them later. Two things:

• A face signature: 128 numbers describing one face, stored packed in the app’s own database. Enough to spot the same person in another photograph, and not enough to rebuild the photograph.
• A person’s photo, if you chose one for them.

An earlier version of the app also kept a small crop of the face each signature came from. It keeps none now, and updating the app deletes any it had kept.

Where it is held, and by whom

In Little Now’s private storage on your own device. The photograph is read on the phone by a model that ships inside the app. Nothing is uploaded and nothing is looked up anywhere, so Little Now is never in possession of these measurements and holds no copy of them to retain, disclose, or destroy. The copies that exist are yours: the one on your device, one inside any export you made, one in an automatic copy you turned on, and one in a platform device backup if your phone made one.

How long it is kept

For as long as that person is in your list, and no longer. The purpose is to offer you that person in a later photograph, and the measurement exists only while the purpose does. There is no separate calendar period held by us, because there is nothing held by us.

What destroys it

• Removing one face note erases that signature.
• Removing a person erases every signature they have, and their photo. It is an erasure, not a hiding: the rows are deleted and the files are queued for removal from the device rather than being left behind unreferenced.
• Deleting a child erases their memories and the app-owned files that went with them, after you confirm by typing their name.
• Deleting the app removes its private container from the device, and everything above with it.

Destruction on the device is immediate. Copies you made yourself are outside our reach and remain until you delete them where they are: an export you sent somewhere, a folder in your own cloud storage, or a backup held by Apple, Google, or your device maker under their terms.

Disclosure

We never sell, lease, trade, or otherwise profit from biometric information, and we never disclose it, because we never receive it. There is no circumstance in which we could hand it over, including on request from anyone, since it is not ours to hand.

Consent, including for other people

The app creates a measurement only when you deliberately add a person, never in the background and never from a photograph you simply attached to a memory. A face the app thinks it recognises is offered to you as a question, and is never written into a memory on its own.

Many of the people a parent adds are not the parent: a grandparent, a sibling, a friend at a party. Please ask that person before you add them, and remove them if they ask. The licence agreement asks you to confirm you have their permission for exactly this reason.

Children

Little Now is made for parents and other adult caregivers. The website and app are not directed to children and do not offer a child account. Information about a child in the app is entered by the adult using it and is not sent to us.

Children should not use the contact links or send us personal information. If you believe a child sent us an email, contact us so we can review and delete it where appropriate. The United States COPPA rule does not treat information submitted by a parent about a child as information collected online from the child.

Security

The website uses HTTPS, restrictive browser security headers, and Cloudflare’s network protections. Access to the waitlist database, received email, and provider accounts is limited to what is needed to operate and support Little Now. No method of storage or transmission is risk free, so please do not send sensitive family content by email.

Changes to this notice

We will update the date at the top when this notice changes. If a change materially affects how information already provided is used, we will give additional notice where required, such as on the website or by email to a person directly affected. We will ask for consent before a new use when the law requires it.