Vela pilot: privacy notice

Version privacy-notice.v12 · last updated 27 October 2026 · This invitation-only research trial runs in English or Traditional Chinese (繁體中文), on Telegram or LINE. Each person uses Vela in the language they choose, and Vela translates between the two when a family uses both.

In short

Who runs Vela

Vela is a small pilot run by Timur Aiusheev (in this notice, "the founder"), a private individual in Taipei, Taiwan. There is no company yet. Timur Aiusheev decides how your information is used and is responsible for it. If a company takes the service over, we will tell you before anything changes.

Contact: support@vela-light.com, which reaches the founder.

Who this notice is for

What we collect

From everyone in the family's Vela group

App setup and local preview: The new onboarding asks for the relationship, interests and preferred ways of replying, alongside the name, language, country, time zone and morning time. These help prepare the first week. Before saving, the preview answers stay in app memory; a chosen portrait can leave a temporary local file. The in-memory draft is cleared on sign-out or account changes, except for the one explicitly accepted preview being saved into its intended first signed-in session. Replaced or abandoned portrait previews are removed; interrupted portrait previews are swept on the next app start. If local file deletion fails, a cache file may remain until cleanup succeeds or the app cache is removed. Saving sends the setup answers and chosen questions to Vela; it does not record the invited person's consent. Relationship, interests and reply preferences are kept with their member profile for the same period as their name and morning settings. You can ask the founder to correct or remove them.

Notification choices: You may choose whether Vela sends a notification when a parent answers your question and whether it reminds you before your turn. Vela saves those choices with your account to honour them across your phones. They are not shown to other family members or sent to an AI provider. You can change them in Settings. Vela clears the saved choices when your account is deleted. They do not switch off Vela Light quiet-morning notices, which are explained separately.

Optional parent portrait: The organiser can choose a photo for a parent's window. The cropped portrait is stored on that device, scoped to the signed-in account and family, and is not uploaded to Vela or sent to an AI provider. Remove or replace it in the parent's settings. Signing out or changing accounts clears Vela's local portrait storage. This is different from a photo deliberately sent in an ask or reply, which is uploaded and follows the 30-day media rule. Choose a photo you have permission to use.

About the person the light is for

From each week's messages between the person the light is for and the family: what our software reads in the week as a whole, described under "The weekly read": for the founder only, up to three possible readings of what may lie beneath the words; and, for each organiser who asked or replied that week, a few words on their own messages.

Questions Vela drafts: a suggested question for each of the next few mornings of the person the light is for, drafted from their recent answers and from the recent questions one organiser wrote to them; whether that organiser chose to have it sent in their name; and, on each question sent that way, a mark that Vela wrote it. See "Questions Vela writes for an organiser".

Optional calling number in the iPhone app: With the person’s permission, an organiser may save their calling number on that device to open its dialler from a quiet notice. Vela does not upload that number. It is removed when cleared, when the organiser signs out or switches accounts, and when this app’s private storage is removed. The organiser can contact the founder to request help with deletion. Temporary audio and photo downloads in the app are scoped to its signed-in account and removed on account changes. Audio playback files are removed on completion or cancellation, with a startup sweep for interrupted sessions.

About nearby contacts: the name and how they know the person, which the organiser gives; once the contact has said yes, also their phone number and the messaging app they use; and whether they agreed.

Before setup, about the person the light is for and each family member in the Vela group: the country where they live (for the United States, the state) and whether they are a Russian citizen. The organiser gives these to the founder, who uses them only to decide whether the family can join the pilot now (see purpose 8), and keeps them in the founder's pilot notes as codes and yes or no answers under the family code, never with names.

Only with a separate yes, on the founder's calls: answers to a few short questions, such as how connected someone feels (at weeks 0, 4 and 12), how the organiser would feel if Vela stopped (at days 14 and 30), and whether the organiser would pay for Vela Light, a paid plan Vela plans to offer later (at day 30). Skipping them changes nothing.

App permission: The app shows a notice, in English or Traditional Chinese, naming OpenAI and Deepgram before sign-in or saving. Your own choice is recorded with the text version, a fingerprint of the exact notice and a server timestamp when your account is provisioned or you accept on an existing account. This app record stays with your active account and is cleared when the account is deleted. It is separate from your parent’s consent, the health-words choice and the longer-lived consent records below. Declining keeps the preview on your device and does not authorise any family data sharing. Existing test families continue under their recorded pilot consent; a software update does not create new consent for them.

Records we create: when and how each person agreed or said no, to which version of which text, and, for a button tap, a fingerprint of that text; delivery records; a log of each AI call (which call, when, whether it worked, its cost); a log of every time the founder opens or changes a family's records; usage events without any message content, such as "an answer arrived at 08:12, by button".

What we do not collect

No location. No access to a phone's contacts, camera or microphone beyond the voice notes people choose to send. Vela does not ask for medical records; words about health that someone chooses to say in an answer are handled as described under "Health words". Nothing from anyone's device other than what they send to Vela. No advertising identifiers. No payment information: the pilot is free.

In the family's Vela group, Vela keeps only the messages meant for it: replies to its evening message, /ask and /later messages, replies to the posts of answers, reactions to those posts, and taps on "I've read it". It also notices when someone leaves the group, which the messaging app tells Vela.

Why we use it

  1. To carry the exchange: deliver each ask at the person's morning hour in their language, then bring the answer and the family's replies back.
  2. To keep the light: tell the family when the person has answered. Learn from their answer times when they usually answer, on each day of the week. When a morning is still unanswered a while after that, send them a short check-in; when they tap "Not okay", tell every organiser and the founder at once (see "The check-in"). When a day stays quiet, send the organiser the facts (when the morning message went out, when the person usually answers) and the names and numbers of the nearby contacts who have agreed, so the organiser can decide what to do.
  3. To work across languages and voices: turn voice into text, translate between English and Traditional Chinese when the family uses both.
  4. To pass on words that matter: if an answer mentions something like a fall, pain, a stranger at the door or a request for money, the organisers hear about it that day: with the person's own words if the person the light is for has agreed to that (see "Health words"), and otherwise in a short note, with none of their words, saying that something they said may be worth a call. Vela does not diagnose, and it does not send these words to anyone else.
  5. To send the organiser a short weekly read on Sunday: what the person told the family that week and what changed in how they answered, compared only with their own earlier weeks, and, with the separate yes under "Health words", their own health words that came up on two or more days. That account is never a score, a diagnosis or advice. Each organiser's copy may also carry feedback on their own messages, with one suggestion for the week ahead. The founder alone also sees a reading of what may lie beneath the week's words, to understand the family's week while checking the read, and to judge whether readings like these are accurate and kind enough ever to share. Both are described under "The weekly read".
  6. To run the service safely: send every message once and on time, fix failures, prove that deleted information was deleted, and show what each person agreed to.
  7. To learn whether the pilot works: answer rates, answer times and how often days stay quiet, counted without names. Results are shared only as totals.
  8. To decide who can join the pilot: the founder's family in Vietnam took part first; up to 10 families in Taiwan, most of them on LINE and in Traditional Chinese, follow for about 30 days. Each family takes part only once the founder has approved it on Vela's admin page. This describes the proposed cohort, not legal clearance. The founder checks each participant’s residence and any relevant citizenship restrictions before approving participation. The Vietnam family waits until the review of its actual participants, consent and processing flows is complete. Existing restrictions remain in force until that review is recorded.
  9. To suggest questions, and send one for an organiser who chose it: draft a question the family could ask the person next, in the style of one organiser's own recent questions, for the family to use, change or ignore in the app; and, only for an organiser who chose "Send it as me", send it as that organiser's question on a morning when nobody in the family wrote one (see "Questions Vela writes for an organiser").

We do not sell information, show advertising, or use anyone's words or voice to train AI models. We do not use a real answer or voice note to test or improve Vela's AI unless the person who said it agrees separately, for that one item.

What we rely on in Taiwan (Personal Data Protection Act):

Health words

Words about health, such as a fall, pain, not eating, a visit to the doctor or what a doctor said, need care. Under Taiwan's law some of them may count as medical information, which may be used only with the person's own written consent (Personal Data Protection Act, Article 6(1)(6)). So Vela asks the person the light is for about them separately.

The check-in

The morning message has no buttons: the person answers it in their own words, by voice or in writing.

The weekly read

Every Sunday Vela drafts the weekly read, and the founder checks it before anything is sent. It has three parts. For the feedback and the readings, Vela's AI reads that week's messages only: the person's answers (what they wrote, the written version of what they said, and the buttons they tapped), each morning's ask and who sent it, and the family's replies and reactions to the person, each with the family member's first name.

Questions Vela writes for an organiser

Every night Vela's AI drafts a question for each of the next few mornings of the person the light is for. It starts from Vela's own list of questions, and may draw on people, places and plans the person mentioned in recent answers and on the recent questions one organiser wrote to them, so that it sounds like that organiser. The family sees it in the app as a suggestion, and anyone in the family can use it, change it or ignore it.

Who sees it

ProviderWhat it does for VelaWhat it receivesWhere
ClerkApp sign-in and session verificationAccount identifier, name/email supplied for sign-in, session activity; no family message contentUnited States
Neon (part of Databricks)DatabaseEverything we store except voice notes and photosSingapore
CloudflareRuns Vela's software; stores voice notes and photosEverything while it is processed; voice notes and photos at restStored in its Asia-Pacific region as we request, which Cloudflare treats as a preference, not a guarantee; processed on its worldwide network
OpenAIAI: summaries, translations, suggested questions in an organiser's style (see "Questions Vela writes for an organiser"), drafts of the weekly read with each organiser's feedback and the founder's readings (see "The weekly read"), noticing words that matter. Vela sets store: false on its requests. OpenAI does not use API data for training by default, but may keep inputs and outputs in abuse-monitoring logs for up to 30 days, with longer retention where required by law or necessary for safety. This setting is not Zero Data Retention; no approved Zero Data Retention arrangement is recorded for this pilotAnswers, asks, replies and reactions, with when they were sent, family members' first names, roles and languages, and whether the person the light is for agreed to health words. Never phone numbersUnited States
DeepgramTurns voice notes into textVoice notesUnited States
Sentry (planned, not connected)No current processing for Vela; error reporting would need its own setup and notice before activationNone at presentGermany (EU), planned
TelegramCarries the messages of families who use Telegram, as an independent messaging platformEverything sent in the chatIts own data centres, under its own privacy policy
LINE (LY Corporation)Carries the messages of families who use LINE, as an independent messaging platform, under its own termsEverything sent in Vela's chats and in the family's Vela group, including what Vela then discards. LINE keeps its own copies of voice notes and photos for a period it does not publish; Vela copies them to Cloudflare at once and deletes its copy after 30 daysIts own data centres, under its own privacy policy
Google Drive, in the founder's own Google accountThe founder's pilot notesOnly a family code instead of a name, dates, the versions of the texts people agreed to, yes or no answers, the country (or US state) where each person lives and whether they are a Russian citizen, as codes, and questionnaire scores; never quotes or anything about health. In a private folder shared with no oneOn Google's servers in the United States and other countries, under Google's own terms for personal accounts

Expo delivers app builds and checks for app updates; it receives technical installation/update identifiers and network details. Push notifications are separately controlled and are not enabled merely because the app shows a permission prompt. If enabled, Expo and Apple (APNs) or Google (FCM) also receive device push tokens and notification text/identifiers, never family answer text or health words.

Telegram and LINE are the messaging apps used in this trial, each under its own terms. Messages in those chats stay in the app until you delete them there; deleting your information in Vela does not remove them from your chat history.

We will tell organisers at least 14 days before a new provider starts receiving family messages.

Where it is stored

Our database is in Singapore. Messages on Telegram or LINE also pass through that app's own servers. We ask Cloudflare to store voice notes and photos in its Asia-Pacific region; Cloudflare treats this as a preference, not a guarantee. Vela's software runs on Cloudflare's worldwide network, so a message may be processed for a moment in the Cloudflare data centre nearest to the person who sent it. The AI and voice-to-text providers work in the United States. The founder's pilot notes are kept in Google Drive, on Google's servers in the United States and other countries. Your information is therefore used in Singapore, the United States and other countries where these providers operate, not only where you live.

How long we keep it

InformationHow long
Voice notes and photos (in answers, asks and replies)30 days, then deleted
The words of answers, asks and replies: text, transcripts, translations, suggested answers, suggested questions, and health mentions where the person agreed to them30 days, then deleted
Existing stories previously kept in the family book (the book is unavailable in this trial)Until the family removes them or leaves Vela. Saying "don't keep that one" removes a story
One-line summaries of answers, answer times, records of quiet days, weekly reads (except the parts in the next row)While the family uses Vela
The founder's readings of what may lie beneath the words, and each organiser's feedback, in the weekly read30 days after the end of the week they are about, then deleted. Feedback that was sent stays in the organiser's own chat until they delete it there
Names, greeting, language, time zone, wake-up time, messaging accountWhile you are in Vela; deleted 30 days after you leave (leaving the family's Vela group counts, except for organisers, who tell the founder), or within 24 hours if the family is deleted
What the organiser gave about the person the light is for, before the person answers the invitationDeleted at once if the person says no; deleted 30 days after the invitation link expired if the person never answers
Nearby contacts' name, how they know the person, and messaging appUntil the contact or the organiser removes them, or the family leaves Vela. Deleted within 7 days if the contact says no, and 14 days after they were added if the contact has not said yes
Nearby contacts' phone numberStored only once the contact has said yes; removed from Vela's list of contacts as soon as their no is recorded. A quiet-day notice sent to the organiser before the no may hold the number: Vela deletes its copy within 30 days of that notice, and the message stays in the organiser's own chat until they delete it
Records of consent: who agreed or said no, to which text, whenWhile the consent is in force. Once it stops (the answer was no, it was withdrawn, or the information it covers was deleted), 5 more years, then deleted. Once the information it covers is deleted, the record keeps only reference numbers, the version of the text, the times and a fingerprint of the text, never the person's words, name or number
Delivery records: what was sent to whom, when, and whether it arrived24 months, and deleted with the person's information; the message text inside them is deleted after 30 days
Log of AI calls: which call, when, whether it worked, its cost24 months, with names removed when the person's information is deleted; what the AI returned is deleted after 30 days
Usage events and daily counts without message content24 months
Error reportsUp to 90 days
Log of the founder opening or changing family records24 months
Deletion fingerprints5 years
The founder's pilot notes (including where each person lives and whether they are a Russian citizen) and research answersUnder a family code, not a name; deleted within 12 months after the pilot ends
When the pilot endsIf your family does not continue, we delete your family's information within 30 days. The only things kept longer are those this table already keeps longer, for the periods it gives: usage events and daily counts without content, the AI call log without names or content, error reports, the log of the founder opening or changing records, records of consent without anyone's words, name or number, deletion fingerprints, and the founder's pilot notes under a family code. If the family already has retained stories, the founder handles requests for them directly
BackupsDeleted information can stay in the database's restore history for up to 7 days before it is gone

When we delete something, we keep a short record of what kind of record it was, its reference number and when it was deleted, with a fingerprint (a hash) of the kind and the number, never of what it said. We keep records of consent and of deletions for 5 years because Taiwan's law makes us prove what people agreed to, and a claim for damages can be made for up to 5 years after the damage (Personal Data Protection Act, Articles 7 and 30).

Your rights

At any time, free of charge, you can:

The person the light is for can also ask "what does the family see" in the chat, and receives the one-line summaries of their last seven answered days and the lines about their week from the most recent weekly read sent to the organisers. It does not show the organisers' feedback or the founder's readings (see "The weekly read"). For those, or for anything else the family has seen, ask the founder.

How: write to support@vela-light.com, or tell your organiser, who passes it on to the founder. We may ask one simple question to make sure the request comes from you. Stopping takes effect immediately. We aim to complete every other request within 7 days, and always within the time Taiwan's law allows: 15 days for access or a copy, 30 days for a correction, a stop or a deletion (each extendable once, with a written reason). These rights cannot be waived or limited by agreement.

If you are unhappy with how we handled your information, please tell the founder. You can also complain to the data protection authority where you live.

If you do not give us this information

Every part of Vela is a choice.

Not a medical or emergency service

Vela cannot tell whether anyone is in danger and cannot send help. Messages can be late or fail. If someone may need help now, call them, and call emergency services (119 in Taiwan, 911 in the United States, 112 in Europe). A quiet day in Vela is information, not an alarm, and a "Not okay" tap reaches the family, not emergency services, and words or notes passed on to the organiser, the weekly read and its readings are not a diagnosis.

Changes to this notice

This notice may change during the pilot; the date at the top says when it was last updated. If we change what we collect, why we use it, who receives it or how long we keep it, we will tell everyone in the pilot before the change applies, and ask again where consent is needed. Every version has a number and a date.