This page is written for two audiences. If you are a Raileon customer, it tells you what our Modules do, where they fail, and what we expect of you. If you received an email, message, or document that was produced with the help of a Raileon Module and you never agreed to anything with us, it tells you what you are looking at and how to raise a problem.
1. What our Modules are
SkyRaileon LLC is a Florida company that builds and operates AI Modules for businesses. A Module is software. It runs on a dedicated instance we operate for the customer, and it is configured by that customer to perform specific work.
Depending on how a customer configures it, a Module may:
- Read and triage incoming email and messages.
- Draft replies, follow-ups, notes, and other written material.
- Summarize documents, transcripts, and long threads.
- Extract structured data (names, dates, amounts, deadlines) from unstructured text.
- Look things up in the tools the customer has connected. Connecting a mailbox, calendar, or CRM grants access to the entire mailbox, every calendar, or the whole CRM. Raileon cannot narrow an OAuth connection to a folder, a single calendar, or a subset of records.
- Take scheduled or triggered actions, such as sending a reminder or posting to a chat channel.
A Module has no independent authority. It can only touch the systems a customer connects and can only do the things a customer switches on.
2. What is machine-generated
When a Module is involved, assume the following are produced by an AI system rather than typed by a person:
- Drafted emails and messages: including replies sent from a customer's address or chat account, whether or not a person edited them first.
- Summaries: of calls, threads, meetings, contracts, or files.
- Reports and analyses: including any figures, totals, or trends they contain.
- Extracted data: fields pulled out of a document and written into another system.
- Scheduled and automated actions: reminders, follow-up sequences, status updates, and similar routine steps.
A person may review and edit any of these before they go out. Whether that happened in a particular case is a decision made by the customer, not by us.
The same standard applies to content we publish ourselves. Where a post on this blog was drafted with AI assistance, its byline says so and credits the Raileon team rather than an individual; only posts written by a person start-to-finish carry that person's byline.
Business Audit. Parts of a Business Audit report are written with AI from our own measured results, and a person at Raileon reviews the report before it is published (the Google figures in it come from Google and are not part of that review). The report also shows how ChatGPT, Perplexity and Google's AI answers respond to questions a customer might ask; those answers vary by person, place and day, and the report says when they were sampled. If a business replies to the lead response test, an AI model drafts a grade of the reply and a person confirms it. See our Privacy Policy.
3. Known limitations
AI systems are useful and they are also unreliable in specific, predictable ways. We would rather say this plainly than bury it.
- They can be confidently wrong. A generated answer can be fluent, well-structured, internally consistent, and still false. A Module will not usually signal that it is unsure. Confidence in the writing is not evidence that the content is correct.
- They misread context. Sarcasm, hedging, an exception buried in a long thread, an unstated assumption inside a business, or a detail that matters only to one client. All of these get missed or flattened.
- They go stale. Model knowledge has a cut-off, and a Module only sees the data it has been given access to. Prices, rules, statuses, and contact details can be out of date without anything looking wrong.
- They are inconsistent. The same question asked twice can produce different answers.
- They invent specifics. Citations, case names, section numbers, dates, and figures are exactly the sort of detail an AI system will fabricate to complete a plausible-sounding sentence.
4. Human accountability
The customer is responsible for reviewing and approving consequential actions. This is not a disclaimer we hide in the terms. It is how the product is built.
- Approval gates. Payments, purchases, ad spend, e-signatures and public posts always wait for a person to approve them, and that cannot be turned off. Emails, texts and chat replies to customers wait for approval by default; an owner can turn that off, or set chat to reply automatically.
- Autonomy controls. Customers choose how much a Module may do on its own, per capability, and can narrow that at any time.
- Activity logs. Module actions are recorded so a person can see what happened and when.
We strongly recommend leaving approval on for anything that leaves the business, commits the business, or affects a legal deadline. If a customer turns approval off for messages, or sets chat to reply automatically, those messages go out without review, under the customer's name, and remain their responsibility.
5. Telling your own clients
This section is for Raileon customers. If your Module contacts the people you serve, they deserve to know when they are reading something an AI system produced.
What we do, as the provider
Every Module we ship carries a platform-level instruction, appended after and outside any customer or template configuration, to answer honestly if someone asks whether they are talking to a person or an automated system. No template can turn this off. Modules do not name the underlying AI vendor or model in conversation (our AI providers are listed on our sub-processors page); withholding that detail is a product decision, not a denial that the Module is AI.
What we expect of you
- Do not present an AI-generated message as something you personally wrote. Do not give a Module a human persona, a fabricated staff name, or a signature that implies a person composed the message.
- Where a Module is handling a conversation with little or no human review, say so: a single plain line is enough, for example that the message was drafted with AI assistance and is reviewed by your team.
- If someone asks whether they are talking to a person, answer honestly and promptly.
- Follow whatever your own professional body, regulator, or client engagement letter requires. Those obligations sit with you, and they are often stricter than ours.
Why this is the law, not just good manners
Article 50(1) of the EU AI Act applies from 2 August 2026, subject to any later amendment. It requires providers of AI systems that interact directly with people to ensure those people are informed that they are dealing with an AI system, unless that is obvious from the context. Other parts of Article 50 require certain AI-generated content to be marked or disclosed as such. A growing set of US state laws impose their own AI-disclosure duties, particularly around chatbots, marketing, and automated outreach, and the list grows with each legislative session.
We are describing the general direction of the law, not giving you legal advice. Whether a specific rule applies to your business and your outreach is a question for your own counsel. See our Acceptable Use Policy for the conduct rules that apply to your use of the platform.
6. Models and data
Module reasoning runs on large language models supplied by third-party AI providers. We access those models through commercial APIs under contract; the commercial terms of the provider behind Raileon-managed AI prohibit training on customer content. A customer may also choose to connect its own AI provider account. In that case the provider processes the data under its own terms, which decide whether it may train on that data, and bills the customer directly.
- Customer data is sent to a third-party AI provider only to produce the requested output. Raileon does not use it to train AI models, unless you hire us to train your own model. Then it's trained only for you, runs on your systems, and you own it.
- Each customer's Modules run in a dedicated, sandboxed container. Records such as conversation history are kept in our managed database, separated by workspace (see Security). Data is encrypted in transit with TLS 1.2 or higher and encrypted at rest.
- The full list of the providers we rely on, and what each one does, is published at raileon.com/subprocessors.
For how we collect, store, and delete information generally, see our Privacy Policy.
7. Not professional advice
Nothing a Module produces is legal, medical, tax, accounting, or financial advice, and no Module output creates a professional relationship of any kind with SkyRaileon LLC. Our customers are often licensed professionals; when they use a Module to help draft something, the professional judgment, the review, and the advice are theirs. The Module is a drafting tool, in the same category as a word processor with opinions.
8. Automated decisions about people
Raileon does not use Modules to make solely-automated decisions that produce legal effects concerning individuals or that similarly significantly affect them. Where a Module touches an inquiry about a person (for example helping a customer triage or prioritize leads), it gathers, summarizes, and prioritizes information; a person makes the decision.
Customers must not either. Using a Module to decide, without meaningful human involvement, whether someone gets a job, credit, housing, insurance, healthcare, education, or a legal outcome is prohibited by our Acceptable Use Policy. A Module may help gather and summarize information for a person who makes the decision; it may not be the one making it.
Regardless of where you live, we extend the same data-protection rights to everyone, including the right not to be subject to a decision based solely on automated processing. We do not gate those rights by country. To exercise them, contact privacy@raileon.com.
9. Reporting a problem
If you received a message you believe was AI-generated and something is wrong with it (it is inaccurate, misleading, unwanted, impersonates someone, or was not disclosed as AI-assisted), tell us. This applies whether you are a customer or someone a customer contacted.
- Email admin@raileon.com.
- Include the message if you can, or a screenshot, plus roughly when you received it and who it appeared to come from. That is what lets us trace it back to the account responsible.
- For a suspected security issue or data exposure, write to security@raileon.com instead.
- For data-protection requests (access, correction, deletion), write to privacy@raileon.com.
We will acknowledge reports about Module-generated messages and investigate. Where a customer has broken our rules, we act on the account. We cannot control what a customer writes with a Module any more than an email provider controls what is typed into an email, but we can and do enforce our policies against accounts that misuse the platform.
10. Changes to this statement
We will update this page as the technology and the law change. The effective date at the top shows when it was last revised. Questions about anything here can go to admin@raileon.com.
SkyRaileon LLC
Miami, Florida