Privacy

What the website does now

This is a static website. It sets no advertising cookies, runs no third-party analytics, and does not track visitors across sites. The access chooser has no form and sends no access request by email. It does not collect a name, email address, LinkedIn profile, or password.

Three pages sign you in. The account page, Friends and Pricing send the email or username and password you type there from your browser to the Alelyon identity service, which checks them against the hash of the password it stores and gives the page a session kept in its memory, and keeps your browser signed in with a cookie described below. A sign-in with a provider happens in a popup on the provider's own page. Creating an account, resetting a password and deleting an account happen on the identity service's own pages, which send the emails involved. Nothing is sent until you submit, and simply opening a page collects nothing. An account is not required to download the build. Until 10 October 2026 the account page made a separate account at Supabase instead (see Processors below).

The identity service's cookies. The identity service sets the cookies that sign-in needs on its own address, id.api.alelyon.com, not on this site's. Each is HttpOnly, so no page can read it, and Secure. __Host-alelyon-site, set when you sign in on one of the pages above, holds an opaque handle that keeps your browser signed in (SameSite=Strict). It ends when you sign out, when you close the browser, after 8 hours without using the site, or 24 hours after you signed in. If you tick "Keep me signed in", it outlives closing the browser and ends when you sign out, after 30 days without using the site, or 30 days after you signed in. Either way it ends at once when you change your password or sign out everywhere. __session, set by the service's own pages (creating an account, resetting a password, deleting an account) and during a sign-in with a provider, holds that form's or sign-in's one-use security check, for 30 minutes at most. Neither is set for anyone who does not use them.

Friends messages. New messages are sealed on your devices before they reach Alelyon, for your friend's devices and yours, so the service stores them in a form it cannot open; an independent review of this is pending. The service still sees who wrote to whom and when, and how long each message is. Messages sent before sealing began, and messages to a friend who has not yet opened Friends on an updated app or this website, are stored in plain text until 22 October 2026 (00:00 UTC), when they are deleted and unsealed messages end. To seal and open messages, a browser signed in on Friends keeps one key in this site's storage, which the page cannot read out, and the ids of your friends' devices it has seen; Sign out everywhere deletes them. Since 22 October 2026 it also keeps, and the app keeps on your computer: which of a friend's devices you accepted, the safety code you verified with each friend, and a fingerprint and number for each recent message, so that it can tell you when the service left a message out, showed it twice or changed it. These stay on your device; the service learns only that your device can check messages this way.

The developer console keeps, in this site's storage on your browser, how you arranged it: the products you pinned, the pages you opened there lately, the account you work in, and the charts and views you saved. The site's search keeps the last pages you opened while signed in, to offer them first. None of it leaves your browser, except the charts pinned to the console's Home, which are added once to a board kept with your account (see Boards); it belongs to the account that made it: signing out, or another account signing in on that browser, removes it.

Nexus chat on this website. While your browser is signed in (through the pages above), Nexus keeps your chat in your Alelyon account: each message you send there, the answer the model gave, the model's name, each topic's title, and a short summary of each topic that the model you are using writes after every few messages. The identity service stores them as text, so Alelyon can read them; they are not sealed like Friends messages. They are shown to you only, on any device where you sign in, and are kept until you delete a topic, use Forget everything, or delete your account. Alelyon may use them to train its models unless you opt out: untick “Let Alelyon use this chat to train its models” under Topics. Opting out keeps your chat out of training from then on, and stays until you tick it again or delete your account. To find which earlier topic a message belongs to, the page compares your topics' words in your browser, and it sends the model you chose your message with the closest parts of earlier topics and their summaries, as the model receives every message. Signed out, the chat stays in the tab and nothing is kept.

The free model. When you are not signed in and have not chosen a model, Nexus on this website answers with Gemma 4, an open model made by Google, which Google Cloud runs for Alelyon. Each message you send it goes from your browser, with the earlier messages of the conversation, the files you add to it and the instructions the page adds, through Alelyon's free-chat service at free.api.alelyon.com to Google Cloud, and the answer comes back the same way. The service passes them on and keeps none of them. Google processes them for Alelyon under its cloud terms: it does not use them to train or fine-tune models, does not log them, and keeps them only for limited periods. It may process them in any region where it runs the model. Before your first message, the page asks the service for a pass: a random identifier the service signs, with no account, IP address or device attached. The page keeps the pass only in its memory, so it is gone when you close or reload the tab. To keep the free model within its limits, the service records for each pass how many messages it answered that day (UTC) and what they cost. A later day's first free message replaces that record, and copies kept by Google's storage against accidental deletion are deleted 7 days after that. The service also keeps the month's total cost. A model you choose yourself is called as described below, not through this service.

The second free model. In the model menu you can choose gpt-oss 120B instead, an open model made by OpenAI, which Amazon Web Services runs for Alelyon through Amazon Bedrock in itsus-east-1 region (United States). Your messages to it go the same way, through Alelyon's free-chat service at free.api.alelyon.com/bedrock, to Amazon, and the answer comes back the same way. Amazon processes them for Alelyon under its service terms: Amazon Bedrock does not store or log them, does not use them to train models, and does not share them with the model's maker. That service has its own pass and its own count of each pass's messages and their cost, kept and deleted as described above.

Developer tokens. In the developer console you can make developer tokens for your own programs and AI agents. Alelyon keeps each token's name, the scopes you chose, when it was made, when it expires and when it was last used, and only a fingerprint of the token itself. For each call a token makes, Alelyon records the route, its answer, the time, how long Alelyon took to answer and the request id it answered with, never what was sent, and keeps that record for 30 days. It also counts those calls by minute, hour and day, with how long they took, and keeps the counts for 2 days, 32 days and 400 days; the counts name no request and no address. If you limit a token to certain addresses or networks, Alelyon keeps that list, and checks each call's address against it without storing the address. When you roll a token, Alelyon keeps a fingerprint of its old secret for as long as you chose to let it keep working (up to 24 hours). Alelyon also keeps a record of what you did to your tokens (made, changed, rolled or revoked, with the names, scopes and networks you set, never a secret) for one year, so you can audit them. A post made with a token shows the token's name to everyone who can see the post. Revoking a token stops it at once; deleting your account deletes your tokens, their records and those labels.

Webhooks. In the developer console you can add up to 10 web addresses (webhooks) to which Alelyon sends the Pages events you choose as they happen, such as a reply to you or a mention of you. Alelyon keeps each address, the events it takes, whether it is on, and the secret that signs what is sent to it, encrypted. Each delivery carries the event, the name and username of the person who acted and the post's identifier, and goes to the address you gave, which may be a service run by someone else; what happens to it there is up to that service. Alelyon keeps what it sent for 7 days, so you can send it again (longer only while a delivery still waits to be sent), and each delivery's event, answer and times for 30 days. Deleting an address deletes its deliveries; deleting your account deletes your addresses and their deliveries, and the deliveries to others that name you.

Apps you allow (Sign in with Alelyon). You can let an app sign you in with your Alelyon account and act for you. Before it can, Alelyon shows you the app, whether Alelyon has reviewed it, where you will return and what it asks for; nothing is shared unless you allow it. An app you allow receives an identifier for you that is different for every app; your name and username if it asks for your profile; your email address only if it asks for it and you allow it; and, if it asks for Pages, can read Pages and post or act on Pages as you allowed, with its name shown on what it posts. It never gets your password. What the app does with what you share is governed by its own terms and privacy policy, not Alelyon's. Alelyon keeps which apps you allowed, what each may do and when it last used your account, and only fingerprints of the codes and tokens it holds: a code lasts minutes, an access token an hour, a refresh token 30 days. Disconnecting an app under Connected apps on your account page stops it at once.

Apps you register. If you register an app in the developer console, Alelyon keeps its name, home page and redirect addresses, a fingerprint of its secret, its review, how many people allowed it, and a daily count of its Pages calls and refusals for 90 days, with no person or route. For each call it makes (on Pages, through Alelyon's MCP server, or to exchange a code or refresh a token), Alelyon also records, for you, the route or tool, its answer, the time, how long Alelyon took and the request id, for 30 days, and counts them as it does a token's calls; never the person it acted for, and never what was sent. An app that registers itself keeps the same and belongs to no account; if no one allows it within 30 days it is deleted. Deleting your account deletes the apps you allowed and the apps you registered, with everything others allowed them.

Monitors and alerts. In the developer console you can make monitors that watch your keys', apps' and webhooks' measured calls and the addresses on your projects, and tell you when they cross a threshold you set. Alelyon keeps each monitor's settings, its latest state and value, and when it changed state, for 90 days. An alert can go by email to your account's address, to one of your webhook endpoints, or to a chat channel (such as a Slack or Discord incoming webhook) whose address Alelyon keeps encrypted; what an email or chat alert said, where it went and whether it arrived is kept for 30 days. A chat channel's service receives what the alert says and handles it under its own terms. Deleting your account deletes your monitors, their history and alerts, and your channels.

Projects on your account. While you are signed in, the Alelyon app keeps your projects with your account, so that they follow you to every device where you sign in and to the website: each project's name, the description you give it, and a summary of what its scan found (its languages, its stack, its license and how many files it has). Alelyon never keeps a project's files, code, folder paths, git address or commands. You can share a project with friends: you invite a friend, or you make it public and open to join, so that your friends can see it and join it. Everyone in a project sees its name, description and summary, and the names and usernames of the others in it. In a project shared with others, the Alelyon app also keeps the names of your task threads in it with your account, with whether each is at work, waiting on you, quiet or done, how many sessions it holds and when it last changed, so that the others in the project can see what is active. It never keeps what a thread or its sessions say. A thread's entry is removed when it has not changed for a week, when you leave the project, and with your account. You delete a project you made, or leave one you joined, in the app; deleting your account deletes the projects you made, everyone's places in them, and your places in other people's projects. If you attach an API key or a service account to a project, Alelyon keeps which one, so that its calls show with the project. Only someone who can already see those calls sees it; everyone else in the project is told nothing of it. Detaching it or deleting the project deletes the link, and leaves the key or the service account as it is.

Addresses you watch. If you add a web address to a project, Alelyon keeps the address and reads its domain's public registration record, its certificate and its DNS records. Once you show the address is yours, Alelyon also checks whether it answers, with what status, how quickly and where it redirects. These reads go to the domain's registry, to Google's public DNS service and to the address itself, and carry nothing about you. Results are kept for 30 days, and Alelyon never keeps the pages it receives. Everyone in the project sees the addresses and results. Removing an address, deleting the project or deleting your account deletes them; a deleted copy can remain in a backup for up to 7 days.

Services you connect. If you connect another service to a project, such as Cloudflare, Alelyon keeps the read-only token you give it, sealed so that only Alelyon's service can open it. Alelyon uses the token only to read that service's figures for your project, about once an hour, and keeps summaries of them for 30 days, never the service's raw logs. Only you see them. Forgetting the connection, deleting the project or deleting your account deletes the token and the summaries; a deleted copy can remain in a backup for up to 7 days. Revoking the token at the service stops Alelyon's reads at once.

Dashboards and SLOs. Alelyon keeps the dashboards and service level objectives you save in the developer console: their names, what each widget or objective measures, and its target. They are drawn from the measured calls described above when you open them; nothing more is recorded for them. Deleting your account deletes them.

Endpoint checks. When you turn on a health check for one of your webhook endpoints, Alelyon sends it a signed test event on the schedule you choose, no more often than every five minutes, and keeps what each check found for 30 days: when it ran, whether it passed, the status your endpoint answered, how long it took and a short reason when it failed. It does not keep your endpoint's reply. Turning the check off stops it; deleting the endpoint or your account deletes its results.

The console's change record. Alelyon keeps a record of the changes you make in the developer console, beyond your tokens: to your webhooks, chat channels, monitors, SLOs, dashboards, endpoint checks, the addresses on your projects, what you attach to them and the services you connect to them, and when you show or rotate a webhook's secret. Each entry says when, what was changed and the settings you chose; it never holds a secret, and a chat channel's address, an address on a project, or which key or service account you attached, is left out. It is kept for one year, so you can audit your console; a token you give the console:read permission can read it too. Deleting your account deletes it.

Boards. In the developer console you can arrange boards of your own: a name for each, the time it shows and the calls it is narrowed to, and the charts on it (what each chart counts and how it is shown, the kind of call, key, app or route it is narrowed to, what it is set against and when it should warn you). While you are signed in, Alelyon keeps your boards with your account, so that they follow you to every device where you sign in; at your sign-in, the charts this browser had pinned are added once to a board of their own. A board holds no call, log or figure: those are read again each time it is shown. You remove a board in the console; all of them are deleted with your account.

Kept copies of your console's setup. You can keep a copy of how your developer console is set up, to return to later: its boards, dashboards, service level objectives, monitors and how often your endpoints and the addresses on your projects are checked. It holds no key, endpoint, address on a project or chat channel's address, and no call or figure. Alelyon keeps it until you delete it, until your account goes, or until an update cannot carry it forward, when a new copy of the setup as it stands takes its place and you are told. A kept copy you delete can remain in a backup for up to 7 days.

Service accounts. An organization's owners and admins can make service accounts: members of the organization that are not people, whose developer keys act for it. Alelyon keeps each one's name, username, page, which organization it belongs to and who made it, and what it posts, which is public like any page's and shows the key's name. A service account has no email address or password and cannot sign in. Removing it, or closing its organization, deletes it with what it posted as itself; what it posted as the organization stays the organization's. If you made one and delete your account, it stays with the organization, without your name as its maker.

Your own keys for model providers. When you connect a model provider in Nexus on this website with your own key, your browser calls that provider with it directly; Alelyon never calls a provider with your key, except for background tasks you start with a key you let background agents use (below). If you are signed in and leave “Remember with your Alelyon account” ticked, as it is at first, the key is sent to Alelyon and kept with your account, encrypted, with its last four characters and whether its last check worked, so that it follows you to every device and app where you sign in. Alelyon can read it only to give it back to your own signed-in browser or app, or to use it for your background tasks as described below, and never shows it to anyone else. It is deleted when you forget it under Connections on your account page (Forget or Forget all), or with your account. If you are signed out, “Remember on this browser” keeps the key only in this site's storage on that browser, encrypted under a key the page cannot read out, and nothing of it is sent to Alelyon; it stays until you forget it or clear this site's data in your browser. Keys a browser kept before you signed in stay there until you choose to move them to your account. Unticked, the key is forgotten when you leave the page.

The models you chose last. The model menu's Recent list names the models you chose last. While you are signed in, the last 10 you chose (each one's provider and model name, and when you chose it) are kept with your Alelyon account, so that they follow you to every device where you sign in; at your sign-in, the ones this browser listed are added once after them. They are deleted with Forget all under Connections on your account page, or with your account. Signed out, they are kept only in this site's storage on that browser. They are never a message or a key, and are not part of the usage counts below.

Phone notifications. If you turn notifications on for a device on your account page, your browser gives Alelyon an address at that browser's own push service (Apple's, Google's, Mozilla's or Microsoft's) and the keys to encrypt to it. Alelyon keeps them with your account, with the name you give the device and when it was added and last sent to, for up to 10 devices. When a session needs your answer, a task finishes or stops, or a change waits for your word, Alelyon sends that device a short notice: one of a fixed set of sentences, with at most a session's or group's name, never a chat's text. Each notice is encrypted to the device, so the push service carries it without being able to read it; it sees the device's address, when a notice is sent and its size. Notices are not kept after they are sent. A device is deleted when you choose Forget, when its push service says it has unsubscribed, or with your account.

The cloud workspace. If you start a cloud workspace from the Nexus chat on this website (signed in), it is a small computer for your account where you, and the agent when you allow it in Edit mode, run commands on a copy of the folder you opened. The files you send are copied to the workspace: the ones the chat lists, never what the folder's .gitignore or .latticeignore ignores and never secret-looking files such as .env or keys. They are kept 14 days after you last use the workspace and then deleted, or at once when you delete the workspace or your account. Changes made there come back to you only for review. The commands you or the agent run, and their output, are not kept by Alelyon beyond the running workspace. The workspace can reach the internet, so a command can send what it can read wherever that command sends it. The minutes the workspace runs are kept for each month with your account, to measure them against your plan's hours.

Background tasks. If you start a background task from the Nexus chat on this website (signed in), an agent works on the goal you wrote, with the model you chose, in its own cloud workspace holding a copy of your open folder, sent as for the cloud workspace above, and keeps working after you close the tab. Alelyon's agents service calls that model's provider with your key, which is kept with your account: only for tasks you start, and only after you turn on “Background agents” for that key (in the chat, or under Connections on your account page, where you can turn it off). What the agent sends the provider (your goal, the conversation of the task, and what it reads from the copy of your folder) goes to that provider under its terms, as when your browser calls it. Each time the service is given your key, the provider and the task are recorded with your account, never the key. A task's goal, its events (the agent's messages, a short summary of each tool it used, its questions and your answers), its to-dos and its summary are kept 30 days after the task ends, and then deleted, or at once when you delete the task or your account. Its workspace's minutes count against your plan's hours. Changes it makes come back to you only for review.

Plans, trials and usage counts. Your account records which plan you are on. When an organization you belong to on Pages is given a trial of a paid plan, you are on that plan until the trial ends, which the account page shows. While you are signed in, the website and the app count a few moments of using Alelyon: connecting a model, opening a folder, keeping an edit, reaching a plan's limit, pressing Upgrade, inviting a colleague, a step of the first-visit checklist, and starting a cloud workspace. What is kept is the moment's name and how many times it happened that day, under your account; never a message, a file, a path, a reply or a model's name. Alelyon reads these counts per organization to see whether Alelyon is useful and how to improve it.

The site is served by Google Firebase Hosting, which may process standard request information such as IP address, user agent, requested URL, and timestamp for delivery, security, and operations. Alelyon does not receive that request log as a separate record and does not join it to any account.

Following an external link, including the open-toolkit repository, takes the visitor to a separate service whose operator may process the request under its own terms.

The app on your computer

The app on your computer covers the local Terminal interface and Nexus, plus the separately published alelyon-os toolkit. Getting it does not use LinkedIn, and it does not by itself connect the visitor to a hosted Alelyon backend.

The installer and portable artifact links are not configured, so the current page renders them as unavailable controls. There is no email fallback and no download request record.

Alelyon Terminal (desktop)

Alelyon Terminal is a desktop application. A local account, workspace layout, watchlists, research artifacts, history store, and any position data are stored on the user's machine by the desktop application. Running the application alone does not send those records to Alelyon. The packaged preview's local sign-in is not remote identity.

The application can make requests to third-party market, economic, filing, and model providers when the user selects and configures those features. Content sent to a selected provider is processed under that provider's own terms and privacy practices. Alelyon does not publish a provider-by-provider inventory for the desktop application, because which providers are contacted depends on which features the user configures; the application names the provider at the point of configuration.

Pages and public posts

Pages is the public side of an Alelyon account, used from the Alelyon app and, where it is offered, from this website. It is opt-in: nothing about you is public until you open a page.

What a page makes public. Your name; your username; your title, the organization it names, and whether that organization confirmed it; the organizations you choose to show after your name; your biography; and everything you post (posts, articles, replies, quotes and reposts), with when you posted them and how many replies, reposts and reactions of each kind each has, who may reply to it, and any poll it asks with the poll's totals; the post you pinned to the top of your page; and your experience, education and skills, with how many people endorsed each skill and whether an organization confirmed a position; and the photos you post, with the descriptions you give them, and your page's photo and banner; the communities you are a member of, with whether you own or moderate each; and the products you own or are a maker of. It also shows how many people follow you and how many you follow. Anyone can read these, signed in or not, and search engines and others outside Alelyon's control may copy them.

Signed records. What your page makes public is also kept as a signed repository: records signed with a key Alelyon makes for your page and keeps, so that anyone can check that a post is what your page published, unchanged. Your page's identifier (adid:plc), its public key and the signatures are public with it. The identifier is sent to a directory outside Alelyon only if you put your page on the open network (below). The repository holds only what your page already shows, never who you follow or what you react to, and you can download it from your page's Privacy settings.

The open network. You can put your page on the open network that Bluesky and other apps share (AT Protocol), from your page's Privacy settings. It is off until you switch it on. While it is on, your page answers to a handle, your username followed by.alelyon.com, and people using those apps can see and follow it. Your page's identifier, its public key, its handle and the address of Alelyon's service are published in the network's public directory of identifiers (plc.directory), which anyone can read. What your page makes public (your profile, your posts and your reposts, with photos and their descriptions) is also served in the network's own formats, and services on the network copy it as it changes. Who you follow, what you react to and how you vote stay private and are never published. The directory keeps every change to your identifier, publicly and for good, and Alelyon cannot remove it. Switching the open network off stops Alelyon serving your page to the network and answering to your handle, as does a suspension while it lasts; it does not remove the directory's record or the copies others have made. If you delete your account, Alelyon tells the directory that your identifier has ended and tells the network that your account is deleted; services that copied your posts may keep them.

What stays private. Your email address; who follows you and whom you follow (only the numbers are shown, though the person you follow is told); what you liked or reacted to, and how (only totals are shown, though a post's author is told who reacted and how); the posts you save to your Bookmarks; whose skills you endorsed (only totals are shown, though the person is told who endorsed them) and how you voted in polls (only totals are shown); which products you follow, which launches you supported and which feedback you voted for (only totals are shown); your asks to test a product (only its makers see them); whom you mute (they are not told) and whom you block; your lists and who is on them (nobody on one is told); your drafts and scheduled posts, until they are posted; what you report; your choice about AI training; and moderation records. A reply in a conversation open only to its first author's followers shows that you follow that author. Your chats with friends are never part of Pages.

Photos. Before a photo you upload is stored, Alelyon removes its metadata, such as where it was taken and the camera's details, keeping only how it is turned, and checks it against lists of known child sexual abuse material. A photo that matches is not posted: Alelyon keeps it privately as evidence for a year, stops the account's uploads until a moderator reviews them, and reports it as United States law requires. Photos are stored with Cloudflare. One you upload and do not use is deleted after a day; one you delete, or that goes with its post or your account, leaves storage within about ten minutes and Cloudflare's cache within an hour. A photo whose post a moderator hides, or whose page is suspended or closed, is taken out of public storage until it is shown again.

Notifications. Alelyon tells you when someone likes, reposts, quotes or replies to one of your posts, mentions you by your @username, follows you, invites you to an organization or accepts you into one, asks to join an organization you run or a community you own or moderate, accepts your request to join a community, confirms your title or a position you list, endorses one of your skills, applies for a job at an organization you run, lists you as a maker of a product, launches a product you follow, changes the status of feedback you posted or voted for, posts feedback on or reviews a product you make, asks to test it, or invites you to test one. A notification is shown only to you and names who did it. None is made across a block, and none is shown from someone you block or who blocks you, or whose page is suspended. Notifications are deleted 90 days after they were made, and when either account is deleted.

Applying for a job. Organizations can post job openings on Pages, and these are public like any post. When you apply for one, its owners and admins see your page, the note you write and when you applied; nobody else learns that you applied. You can withdraw an application, which deletes it. It is also deleted when the job's post is deleted, when you delete your account, and 180 days after the job closes.

Search and suggestions. Anyone can search Pages by name, username, organization, product, hashtag and the words of posts; Trending counts the hashtags used in public posts; and Explore ranks the day's and the week's product launches by how many people supported them. Who-to-follow suggestions and the For you feed are built from what is public (the organizations people show, public replies and quotes, and follower and like totals) and from whom you follow and the hashtags you used. They never use whom someone else follows or what anyone liked.

Organizations. An organization's page shows its name, ticker and description, and the members who choose to show its ticker. A post made as an organization stays on the organization's page when its author leaves. It also stays when its author's account is deleted while the organization continues, or when a moderator suspends the author's page, but it then shows no author, and the organization's owners and admins are told which of the two happened.

Communities. A community is a public group: anyone, signed in or not, can read its name, description and rules, its members and its posts. When you join one, you appear on its list of members with your role. A post you make in a community shows the community's name, and only its members can reply to it. When you ask to join a community that is joined by request, its owners and moderators see your request until they decide it. They can remove you, and stop you joining again; they see that ban, and nobody else does. They can take a conversation out of the community, and its posts stay yours. If you delete your account, your memberships, requests and bans are deleted; a community whose only member you are is deleted with it, and one you are the last owner of passes to its longest-standing moderator, or else its longest-standing member.

Products. A product's page is public: anyone, signed in or not, can read its name, tagline, description and links, the platforms it runs on and the technologies it is built with, its logo and screenshots, its stage, its makers, and its updates, launches, feedback and reviews. A product belongs to a person or to an organization, whose keepers can list makers; a maker appears only after confirming. Updates and launches are posts by its makers. Anyone with a page can post feedback on a product (an idea, a bug report or a question), which others can vote for; its makers set its status, which tells its author and its voters. A review gives one to five stars with a text, one per account and product; a product's makers and the members of the organization that owns it cannot review it, and no review may be bought or rewarded. While a product is in testing, you can ask to test it: its makers see your page and your note, and may invite you with a note of how to join, which only you see. If you delete your account, your follows, support, votes, asks to test and maker listings are deleted with your posts; a product you own whose only maker you are is deleted with it, and one with other makers passes to the longest-standing of them.

Lists. You can make lists of people and organizations to read their posts together. A list is private: only you see it, its name and who is on it, and nobody on it is told. Your lists are deleted when you delete your account, and you are taken off anyone else's.

Drafts and scheduled posts. A post you are not ready to send can be kept as a draft, with its photos, and a finished one can be scheduled. Only you see your drafts. A scheduled post is posted as you at the time you chose, if it could be posted then; if not, it stays a draft with the reason. Alelyon keeps which post a scheduled draft became for 90 days, so your app can show it. Your drafts are deleted when you delete your account, and a draft of someone else's that quotes a post of yours that goes loses the quote.

Short links. When you share a post to another network from the Alelyon app, Alelyon can make a short address of that post for that network. When someone opens it, Alelyon sends them on to the post, adds one to that short link's count and notes the time of that visit. Visits by a network's preview fetcher and by programs are not counted. Alelyon does not keep the visitor's address, browser or anything else about who they are: their address is used only for the moment's rate limit, as for anyone reading Pages. Only you see your short links and their counts, and you can delete a short link, with its count, at any time. A short link leads only to a Pages post, and stops working if you delete it or the post is deleted or hidden.

Your CRM. The Alelyon app's Agora page keeps a CRM with your account: the leads, contacts, companies and deals you put in it or import from a spreadsheet, and the tasks, calls, meetings, notes and emails you log on them. It also keeps what you set up in it: your own fields and what they hold on each record, your products and prices and the products on each deal, your saved views and reports, your automation rules, and monthly goals. In an organization's CRM, its owners and admins can set a goal for a member, and its members see each goal and how far it has got. A CRM is your own, or an organization's, which every active member of the organization can read and change. Alelyon keeps it for you, or for the organization, and uses it only to show it back to you. It is not shown to anyone else or used to train AI models, and the people in it are not told. You decide who is in your CRM and what it says about them.

Kept copies of your CRM. You can keep a copy of your whole CRM, and an organization's owners and admins can keep one of its CRM, to return to later. A kept copy holds everything the CRM holds at that moment, including the people in it, and, like the CRM, it is shown to nobody else and not used to train AI models. Alelyon keeps it until you delete it, until the CRM goes with your account or the organization, or until an update cannot carry it forward, when a new copy of the CRM as it stands takes its place and you are told. Returning to a copy changes the CRM for everyone in it. Someone who deletes their account, or turns off being added to CRMs, is taken out of every kept copy as they are out of the CRM itself. A kept copy you delete can remain in a backup for up to 7 days.

Being added to someone's CRM from Pages. Someone on Pages, or an organization's owners and admins, can choose to have Alelyon add as a lead in their CRM a person who, from then on, follows their page, follows or asks to test one of their products, leaves feedback on one, or replies to one of their posts. What is added comes only from that person's public page: their name, username, title and the organization after their name, with a note of what they did and when. Nothing else, such as their email address, is added, and they are not told. You can turn this off at any time in the Alelyon app, under Pages, My page, Privacy (Let people add me to their CRM automatically), or by writing to privacy@alelyon.com. Turning it off stops it for every CRM, and removes the leads it added about you that have not been made into a contact. It does not stop someone adding you to their CRM by hand from what your page shows.

Writing to a product's makers. If a product's page has Write to its makers and you use it, Alelyon adds your name, email address, organization and message to its makers' CRM, as a lead, so they can answer you, and only after you tick that you agree. You need no account to use it. Your internet address is used only to limit how many messages can be sent, and is not kept with your message. The makers decide what they keep and for how long; Alelyon keeps it for them, and passes any request about it to them.

Email from your own mailbox. The app can send email to someone in your CRM from your own iCloud Mail, Gmail or Outlook mailbox. The app password you make for it, or for Outlook the permission you give in Microsoft's sign-in, is kept in Windows Credential Manager on your computer and is never sent to Alelyon. A message goes from your computer to your mail provider, which handles it under its own terms and privacy practices; your CRM keeps the message's subject and words on that person's timeline. If you switch on Log the email people in this CRM send you (iCloud Mail and Gmail), the app also reads your inbox on your computer, without changing anything in it, for messages from the leads and contacts in that CRM, and logs each one on that person's timeline: who sent it, when, its subject and its first words. In an organization's CRM, its people see them too. To find who is in your CRM, the app sends Alelyon only a short code made from each sender's address, which many thousands of other addresses share, so Alelyon does not learn who else writes to you. No other mail leaves your computer, and you can switch it off at any time.

Drafting an email with Sinai. If you ask Sinai to draft an email in your CRM, the app sends that record's name, title, company, stage and newest activities (for a deal, also its amount and products), your name, and what you wrote, to the model you chose on Sinai's page: on your computer, or at the provider you set up. Alelyon receives none of it.

Reports and moderation. A report you file is kept for Alelyon's moderators: what it names, your reason and note, and that you filed it. The person you report is not told who reported them. Each moderation act (hiding or restoring a post, suspending or restoring a page, an organization, a community or a product, dismissing a report) is kept in a log that cannot be edited, naming the moderator, the act, what it applied to and any note. A hidden post is kept, out of every read, rather than deleted. If you delete your account, the note of a report you filed stays with the moderators.

If an account whose page was suspended is deleted, its username stays reserved, and so does the ticker of a suspended organization that closes. The reservation is linked to the moderation act and to a keyed digest of the account's email address, never the address itself, so that an appeal can be checked; it is released after an appeal. Anyone who tries a reserved name is told that it is taken, so a name that is taken but cannot be found can reveal that a deleted account had been suspended.

Your choice about AI training. Unless you turn it off ("Your posts and AI" on your page in the Alelyon app, or on your account page at alelyon.com), Alelyon may use your public posts to develop and improve its services, including training and evaluating AI models. It never uses your chats, your email address or your sign-in details this way. Turning it off keeps your posts out of anything built from then on; what was built before is not rebuilt. Only posts that are visible, whose author's account is active and allows it at the time, are used.

Purposes and legal bases

• Running your Alelyon account. Creating your account; signing you in, by password or with an identity provider the service offers, such as LinkedIn; emailing the code that confirms your address and the email that resets a forgotten password; keeping your session, including when you choose to stay signed in; and deleting your account when you ask. Processed to provide the service you signed up for. Rate limits and the other checks that keep accounts and the service secure and prevent abuse are processed under Alelyon's legitimate interests in securing the service.
• Running Pages, organizations and posts, and showing your page. Processed to provide the service you ask for when you open a page and post.
• Keeping your model-provider keys with your account. Processed to provide the service you ask for when, signed in, you leave Remember ticked: giving the key back to you on each device where you sign in. The models you chose last are kept with your account on the same basis, so that they follow you.
• Projects on your account. Processed to provide the service you ask for when, signed in, you keep your projects with your account, share one with a friend, join a friend's, add an address to one, attach a key or a service account to one, or connect another service to one.
• Keeping your boards in the developer console. Processed to provide the service you ask for when, signed in, you arrange a board.
• Keeping your CRM. Processed to provide the service you ask for when you use it. For the people in it, you, or the organization, decide what is kept and why, and Alelyon processes it for you. Adding people to a CRM from Pages, when its owner switches that on, is processed under that owner's legitimate interests in following up on interest shown in their page, products or posts, limited to what a public page shows, and you can object at any time by turning it off.
• Phone notifications. A device's push address and keys, processed to provide the service you ask for when you turn notifications on for it: sending it the notices you chose to get.
• Running a cloud workspace you start. Its files and the minutes it runs, processed to provide the service you ask for when you start it and send your folder to it.
• Running background tasks you start. A task's goal, events, to-dos and summary, its workspace, and your key used for it, processed to provide the service you ask for when you turn on Background agents for a key and start a task.
• Answering with the free model. Your messages, processed to provide the answer you ask for when you send them. The pass and its counts, processed under Alelyon's legitimate interests in keeping the free model within its daily and monthly limits and preventing abuse.
• Understanding whether Alelyon is useful, and offering plans. The usage counts and the plan and trial records, processed under Alelyon's legitimate interests in improving the service and in offering it to organizations. No content is part of them.
• Moderation, safety, and a record of decisions. Processed under Alelyon's legitimate interests in keeping the service safe and its decisions accountable, and to meet legal obligations.
• Improving Alelyon, including AI, with public posts. Processed under Alelyon's legitimate interests in developing its services. You can object at any time by turning the choice off, and your objection applies from then on.

Personal data is not sold and not used for advertising. It is not used to train models, except public posts as described under Pages and public posts, unless you opt out. It is not disclosed to anyone outside the processors named below except where the law requires it.

Processors and where processing happens

• LinkedIn (Microsoft) — an identity provider you can choose to sign in with. You authenticate on LinkedIn's own pages under LinkedIn's terms. Alelyon receives only OpenID Connect assertions within the openid, profile and email scopes: the LinkedIn subject identifier, name, email address, and whether LinkedIn asserts that address as verified. It contacts no other LinkedIn endpoint and does not scrape public LinkedIn profiles.
• Google Cloud — Cloud Run runs the access service in the us-central1 region (United States); Firebase Hosting serves this website from a global content network; Compute Engine runs the Alelyon identity service, which holds accounts and Pages, in the same region; Secret Manager holds the service's credentials; Artifact Registry holds its container image. Cloud Storage holds the private artifact bucket the desktop build is served from. Cloud Run runs a cloud workspace when you start one, and background tasks you start. Vertex AI runs the free model from Google's global endpoint, so a message to it may be processed in any region where Google runs the model; Cloud Run runs the free-chat service in us-central1, and Cloud Storage holds its counts there.
• Apple, Google, Mozilla and Microsoft push services — when you turn on phone notifications for a device, its browser's push service delivers Alelyon's notices to it, encrypted to the device; the service sees the device's address, when a notice is sent and its size.
• Amazon Web Services — Amazon Bedrock runs the second free model, gpt-oss 120B, in the us-east-1 region (United States), for messages you send to that model.
• Cloudflare — stores the photos posted on Pages (R2, in its storage network) and delivers them frommedia.alelyon.com, where its CSAM Scanning Tool also checks them against known child sexual abuse material. It also stores an encrypted copy of the databases of the Alelyon identity service, kept for up to 7 days so that Alelyon can recover them if Google Cloud fails. Cloudflare cannot read it: only a key Alelyon keeps offline opens it.
• Microsoft — when its PhotoDNA service is used to check photos, receives each uploaded photo for that check alone.
• Supabase — operated this website's account page until 10 October 2026. An account made there holds an email address, a hash of the password and the session records of its sign-ins. Those accounts do not carry over to Alelyon accounts and are kept until 10 October 2027 at the latest, then deleted; to have yours deleted sooner, write to privacy@alelyon.com. This website no longer sends anything to Supabase.

Alelyon's own service logs record no email address, no name and no LinkedIn identifier. Google keeps its ordinary infrastructure request logs — IP address, user agent, URL, timestamp — under its own terms.

Alelyon Quantitative Services is established in the United States, and account, sign-in and Pages records are processed there. If you are outside the United States, using an Alelyon account or Pages transfers those records to the United States.

Retention and deletion

On Pages, a post stays until you delete it or your account. A deleted post that others replied to or quoted is kept as an empty marker, with its words and title erased. Closing your page hides your own posts until you open it again, and erases your title and biography. Deleting your account removes your own posts, or empties those that others replied to or quoted. Posts made as an organization stay with it, unless it closes with your account because it has no other members, in which case they go like your own. Notifications are deleted 90 days after they were made. A job application is deleted 180 days after its job closes. A bookmark goes when its post does, and your bookmarks go with your account. Your short links and their counts go with your account, and anyone's short link to a post of yours goes when your account deletion removes the post. On the Free plan, a Nexus chat topic on this website is deleted 30 days after it was last used; on a paid plan, or during a trial, topics stay until you delete them, use Forget everything, or delete your account. Usage counts go with your account. A cloud workspace's files are deleted 14 days after it was last used, or at once when you delete it or your account; its minutes used each month go with your account. A background task's goal, events, to-dos and summary are deleted 30 days after the task ends, or at once when you delete the task or your account. The free model's count for each pass is replaced when a later day's first free message is counted, and Google's storage deletes its kept copies 7 days after that. Keys for model providers kept with your account stay until you forget them, and go with your account. A CRM's records and activities stay until they are deleted, or until its account goes; an organization's CRM stays with the organization, and the records you own in it lose their owner when your account goes. A kept copy of a CRM stays until it is deleted, or until the CRM goes. A kept copy of a console's setup stays until it is deleted, or until the account goes. When your account is deleted, the leads added about you from Pages that were not made into a contact are deleted too. Your choice about being added to CRMs is kept for as long as the account exists. Reports and the moderation log are kept as long as they are needed to keep the service safe, to handle appeals, and to meet legal obligations. An opt-out from AI training is kept for as long as the account exists.

Records from the retired access-request process that already exist (access requests, their decisions and key digests) are kept for 12 months after they were made, and then deleted.

You can ask for your record to be deleted sooner, and it will be, unless a specific legal obligation requires Alelyon to keep it — in which case you will be told which.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or port personal data Alelyon holds about you, to withdraw consent, and to object to or restrict certain processing. Withdrawing consent does not affect processing already carried out.

Write to privacy@alelyon.com to exercise any of them. The same address is the security contact for reporting a vulnerability or a suspected exposure of personal data. It is not an access intake route — the access chooser is.

No response time is promised for either route. If you are in a jurisdiction with a supervisory authority for data protection, you may also complain to it.

On Pages you can also do several of these yourself, in the Alelyon app: correct your name and title, close your page, delete your posts, turn off the use of your public posts for AI training, and turn off being added to others' CRMs.

Children

Alelyon accounts are not for children under 13, or under the higher age that the law of their country sets for using a service like this one without a parent's consent. If Alelyon learns that an account belongs to a child below that age, it deletes the account.

Changes

Material changes are reflected in the date below. Alelyon is a small company and this notice describes software still in preview; where it is silent, treat the silence as a gap to ask about rather than as a permission.

Last updated: 6 November 2026.