Privacy Policy

alwyse is built and operated by CVOYA LLC ("CVOYA", "we", "us"). This policy is the formal record of what we collect, why we collect it, and the control you keep over it. It covers the alwyse.ai website and waitlist, the alwyse apps and browser extension, and the managed alwyse service we operate (the hosting option we call Cloud — during the beta, the one most people use).

The plain-language version of our posture lives on Privacy & Trust, and the live status of every privacy claim we make, per hosting option, is published on the trust roadmap. This policy is written to match both. If you ever find a disagreement between them, tell us — the disagreement is a bug.

The short version

• Your content exists to serve you, and only you. No ads. No resale.
• Your content lives in an instance of its own — one application, one database, per person. Running the service never requires reading it.
• You choose which sources feed alwyse and can sever any of them. You also choose each model destination after seeing its handling facts, and every model crossing is recorded, content-free.
• You can export everything you said and everything alwyse concluded. Deletion removes and physically compacts content today; the remaining recovery guarantees are public.
• This website sets no cookies and runs no analytics.

This website and the waitlist

alwyse.ai is a static site. It sets no cookies, runs no analytics, and embeds no trackers. If you join the waitlist, we store the email address you give us and use it for exactly one thing: sending you an invite. Ask us to remove it at any time.

What we collect when you use alwyse

Your account

You sign in with your Google or Apple account. We receive your name and email address from them; we never see or store a password. We keep the session credentials needed to keep you signed in on your devices, and — if you enable notifications — the device push tokens needed to deliver them.

Your content

Everything you capture or connect — notes, conversations, images, documents, and what alwyse comes to understand from them — is stored in your own instance: one application, one database, that serve you alone. We store and process this content solely to run alwyse for you. We do not read it to operate the service, we do not use it for advertising, and we do not sell it.

Sources you connect

If you connect a source — a calendar, email, files, contacts — you grant alwyse read access through that provider's own consent screen. alwyse keeps what it understood, never a mirror of your account, and the access tokens are held inside your instance. You can sever any connection at any time, and delete what alwyse derived from it.

The alwyse browser extension

If you add the extension, it connects to your own alwyse with your alwyse sign-in in that browser. Bookmarks and open tabs are on by default once connected; Safari supports open tabs and keeping pages, but has no bookmarks extension API. The extension sends your alwyse:

• Bookmarks: the titles, addresses, and folders of pages you bookmarked, so alwyse can understand and remember what you kept.
• Open tabs: titles and site names only, never full addresses. These are held in your instance's volatile memory, expire after fifteen minutes, and never become memories by themselves.
• Pages you choose to keep: the address and title of a page when you choose Keep this page, through alwyse's ordinary capture path.

To maintain the connection, the extension stores your alwyse address, an extension-only credential, an opaque installation identifier, your sharing choices, and sync cursors in this browser's local extension storage. The credential identifies your alwyse account and expires after a week unless renewed from your sign-in or an existing connection. Requests also identify the browser. This storage is not synced between devices and is not used for analytics.

You can turn bookmarks or open tabs off, disconnect, or sign out from the extension's options. Turning a capability off stops this browser reading it and withdraws alwyse's consent for that capability across your connected browsers. Disconnect stops sharing and ends the credential's access once your alwyse receives the request. If your alwyse cannot be reached, the extension stops sharing immediately and holds the credential only to retry that request, until it succeeds or the credential expires. Sign out also ends your alwyse sign-in in this browser. Disconnecting does not delete memories already made from bookmarks or kept pages; you can delete those in alwyse.

The extension never reads your browsing history and contains no advertising, tracking, or third-party analytics. It sends browser data only to your configured alwyse to provide these features; processing and any sharing through infrastructure or capabilities you select are covered below. We never sell this data or use or transfer it for advertising, credit or lending decisions, or purposes unrelated to these features. CVOYA staff may read specific browser data only with your explicit consent, when necessary for security, or when required by law. Any transfer of browser data in a business acquisition or merger requires your explicit prior consent.

Our use of browser data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Model destinations you choose

alwyse presents only the interactive and background model destinations available to you, together with their handling facts. Nothing is sent until you accept the exact current facts. A key you bring is held by your instance and used only for your requests. If you choose an Alwyse-funded destination, Alwyse holds the provider account and can see the provider-side usage metadata disclosed before you accept it. Model content goes directly from your instance to the selected provider, never through our control plane.

Operational data

To run and pay for the service we keep content-free measurements: request counts, token counts, and bytes — never what the requests said. Our service logs are content-free by construction: when your instance makes a model crossing, the record names the destination authority, never the content, path, or query. This is not a filtering promise — the content is never captured in the first place.

Feedback

If you send feedback from inside the app, we receive what you chose to send, de-identified. Nothing is sent unless you send it.

What we can and cannot see

We say this precisely, because it is the heart of the product. On Cloud, we do not claim operator-blindness: we operate your instance, and an administrator with infrastructure access could reach the data at rest inside it. What we have built, and do claim, is content-blind operation: your content lives in an instance of its own; the control plane that handles your account never receives it; inference goes from your instance straight to the model vendor, never through us; and our logs cannot hold your content because it is never captured. If you run alwyse on your own hardware, the question does not arise — nobody but you runs it. The full claim-by-claim status lives on the trust roadmap.

When your content crosses the boundary

Everything alwyse holds about you lives inside a trust boundary. You choose each model destination after seeing its handling facts; the relevant content then goes directly from your instance to that provider under its terms, and every model crossing is recorded content-free. You separately choose and can sever each connected source. Other capabilities, such as web search, can also cross the boundary when invoked. The broader consent dial and unified egress gate for every kind of crossing do not exist today, so we do not claim that blanket guarantee. Run local models on your own hardware and model requests stay inside.

How we share information

We do not sell personal information, and we do not share it for advertising. Information leaves our systems only in these cases:

• Through capabilities you select: accepted model destinations, search providers you invoke, and sources you connect.
• Infrastructure providers: the hosting providers our service runs on, bound by their contractual obligations to us.
• Legal requirements: if the law compels us. Unless we are legally prohibited, we will tell you.
• Business transfers: if CVOYA is acquired or merges, with notice to you before your information becomes subject to a different policy.

Retention and deletion

We keep your content for as long as your account is active — it is your memory, and holding it faithfully is the product. Deletion is in your hands:

"Deleted means gone — removed from everything I show you right away, and then erased for real. Not hidden."

When you delete something in alwyse, it is gone from every screen, search, and answer immediately, and the removal cascades through what alwyse inferred from it. Physical compaction ships, copies in service-readable backups expire within 30 days, and the first owner-sealed quarantine-restore path ships. The remaining total-loss recovery guarantees are published, honestly, on the trust roadmap.

To close your account entirely, contact us at privacy@cvoya.com. We delete your instance and its database, and backup copies expire on the same 30-day ceiling.

Taking everything out

You can export everything you said and everything alwyse concluded, in open formats. A rebuilt instance recomputes the recall search index rather than exporting it. The export is served by your own instance, never by our control plane.

If you self-host

Run alwyse on your own machine and your content stays there unless you select an external capability. It never passes through our control plane. What we hold is what operating your account requires: your name and email, your instance's registration, and content-free service records. Nothing else.

Your rights

Wherever you live, we honor the same set of rights, because the product is built on them: access what alwyse holds about you; correct its understanding conversationally or through a confirmation; delete or export your content; withdraw a source grant; and ask us to correct your account information. There is no per-fact edit or remove control in the understanding view. Most of these you can exercise directly in the app; for anything else, or to exercise rights under the law of your residence (such as the GDPR or the CCPA), contact privacy@cvoya.com. We respond within 30 days. We do not sell personal information, so there is nothing to opt out of, and we will never treat you differently for exercising a right.

Children

alwyse is not directed to children. During the beta you must be 18 or older to hold an account. If we learn we hold an account for someone younger, we will close it and delete its data.

Changes to this policy

When this policy changes, we post the new version here and update the effective date. If a change is material, we tell you in the app or by email before it takes effect — and any change is checked against the trust roadmap, so our promises cannot quietly weaken.

Contact

CVOYA LLC · privacy@cvoya.com · or via the Support page.