Privacy

This public ApexAi website is mostly informational. It has no payment collection, no advertising, and no third-party analytics. The server keeps aggregate counts of page requests to see how the site is used (see Website statistics). It has two forms—Custom Orders requests and Suggestions—and an optional website account you sign in to with Telegram, each described below.

Hosting and basic usage data

The site runs on a DigitalOcean server operated by ApexAi. DigitalOcean may process technical information needed to host it under its own privacy terms. The web server does not write access logs; operational error logs stay on the server.

Website statistics

Status. Switched on: page requests are being counted as described below.

What is counted. When a page is requested in full, the server adds one to counters for: the page; the day and hour (UTC); whether the request came from another site, a bookmark, or a typed address, or from a link or reload on this site; the name of the referring site (for example google.com, never the address of the page you came from); and the device type and browser family (for example mobile, Safari). Automated visitors that name themselves, such as search-engine crawlers, are counted separately by that name. Delivered Custom Orders requests and Suggestions are counted the same way, without their content.

What is not. No network address, full browser identification string, identifier, query string, or form content is stored, and nothing links one request to another. The counts cannot tell whether two page loads came from the same person, so they are not counts of people or visits. Moving between pages without a full reload is not counted, and neither are clicks on links or buttons.

How. Counting happens on the server, from the information your browser sends when it requests the page. No script, pixel, or cookie is added to your browser to count you.

Why. To see which pages are useful, where readers come from, and how search engines crawl the site, so the site can be improved. Never for advertising or profiling.

Where and how long. In a database on ApexAi's own server, separate from website accounts. No analytics provider or other third party receives it. Hourly counts are deleted after 35 days and daily counts after 25 months.

Your choice. Requests that send Global Privacy Control or Do Not Track are not counted. You can also stop counting in this browser; doing so sets one cookie that contains only that choice.

Custom Orders requests

What you submit. Your name, a reply email address, an optional organization, your description of the work—goal, problem, users, systems, requirements, and constraints—and any links you add. The form never asks for passwords, keys, tokens, or other credentials, and rejects text that looks like one.

Why. To review your request and reply to it.

What the site does with it. The server checks the request and sends it as one email to ApexAi's sales inbox, with your address as the reply-to so our answer reaches you. The website does not store the submission: it is not written to a database or a file, and it exists in server memory only while it is checked and sent. Server logs record a request reference and whether delivery succeeded, not what you wrote or your email address.

Abuse limits. To limit repeated submissions, the server keeps a salted, one-way digest of the sending network address in memory for up to 24 hours. It is never written to disk or logs and is discarded when the server restarts.

After delivery. The resulting email is kept in ApexAi's mailbox and handled by its email provider under that provider's terms, like any other email you send us.

When online submission is off. The form prepares an email in your own email application instead. Nothing is sent from the website; the message leaves only if you send it yourself.

Suggestions

What you submit. What the suggestion is about, the suggestion itself, and optionally why it would be useful, a link, and an email address. No name is asked for, and text that looks like a credential is rejected.

What the site does with it. The same as a Custom Orders request: the server checks it and sends it as one email to ApexAi, and does not store it. If you give an email address, it is used only as the reply-to so we can answer; without one, we cannot reply. The same in-memory abuse limits apply.

Website accounts

Signing in. You can sign in to an ApexAi website account with Telegram. Telegram confirms the sign-in and tells the website one stable identifier for your Telegram account. The website does not ask Telegram for your name, username, photo, or phone number, and does not ask for permission to message you.

What is kept. That identifier; when your account was created and last used; your active sign-ins, stored only as one-way hashes with their start, last-use, and expiry times; and a record of sign-in and sign-out events. None of these records contains a network address, a password, or a Telegram token. They are kept in a database on ApexAi's own server.

How long. A sign-in ends after 30 days, or after 7 days without a visit, and you can end every sign-in at once from your account page. The account itself is kept until you ask us to delete it at the address below.

What an account is not. A website account is not access to a product workspace and does not start a subscription or payment.

Twilio setup guide

The Twilio setup guide remembers your answers, the step statuses you set, and anything you type into its preparation worksheet in your browser's local storage on this device, so you can come back to them. They are never sent to the website or to ApexAi. Start over and Clear worksheet delete them, as does clearing this site's data in your browser. The worksheet refuses anything that looks like a Twilio credential, so none is stored.

SMS messages

How a number reaches us. This applies if you text an ApexAi messaging number. Texting it is what opts your number in; no number is messaged unless it has texted first. The message, the sending number, and the replies to it pass through Twilio, ApexAi's messaging provider, under Twilio's own terms, and are kept in the support conversation they belong to so the thread can be answered and its delivery verified.

What is never done with it. Mobile information and SMS consent are not shared, sold, or provided to third parties or affiliates for marketing or promotional purposes. Mobile numbers and SMS opt-in information are not used to build advertising audiences, and they are not added to any list.

Frequency and cost. Messages follow your own: replies within your conversation and status updates about it, with no recurring series. Message and data rates may apply.

Stopping. Reply STOP to end every message from that number; reply HELP for help information.

Email contact

Contact links use mailto:. Selecting one opens your email application; the website does not receive the message. Email providers process messages under their own terms.

Telegram and external links

Links to Telegram and other third-party services are governed by those services' own privacy practices. ApexAi does not control their data handling. Public Telegram channels and groups are visible to their members; keep private details out of them.

Future product features

If ApexAi later adds payments, other measurement, or other data-collecting features, this notice will be updated before those features become part of the experience.

Contact

Privacy questions may be sent to support@apexaiofficial.com.