What We Do: Welcome.inkwelcome.ink/What We Are.md
✎ Edit This

What We Do: Welcome.ink

We are Welcome.ink. A sub-service of Creaddinscart, we provide encrypted redirect services. In short, we turn a plain web link into a protected, algorithmically obfuscated URL that users must pass through before reaching the final destination. ---

Our Core Purpose

Our purpose is simple: give you control over how your links are shared and accessed. Whether you are a creator distributing private content, a community manager gating a Discord server, or a developer testing link protections, Welcome.ink acts as a secure gateway. We do not host your content; we encrypt the path to it. In a world where a URL is often treated as a trivial string of characters, we treat it as something more: a gate, a filter, and a first line of defense. A link is not just an address—it is a promise, a permission, and sometimes a vulnerability. Welcome.ink exists to make that promise harder to break, that permission harder to bypass, and that vulnerability harder to exploit. We are not a hosting provider. We are not a CDN. We are not a link shortener in the traditional sense. We are an encryption and obfuscation layer that sits between the person sharing a link and the person receiving it. The destination remains yours; the path becomes ours to protect. ---

How We Operate

Our workflow is manual and community-driven, not a fully automated public signup. This is intentional. We believe that link protection should not be a faceless, instant commodity. It should involve a human on our side, a real approval step, and a clear chain of responsibility. Here is the exact process:
  • Submit a domain request. You tell us which domain you want to use. This is the domain that will appear in your encrypted redirect. It becomes your public-facing identifier.
  • Join our QQ / Discord and @mention the admin. We are reachable through community channels. There is no ticket system, no chatbot, no automated queue. You talk to a person.
  • Admin approves and gives you an API key with tokens. This is your access credential. The API key is your identity in our system. The tokens are your currency for generating encrypted redirects.
  • Sign in at Dashboard with your API key. The dashboard is your control panel. It is where you manage your domain, check your token balance, and generate links.
  • Generate your encrypted redirect. You choose your algorithm and protection. The system shows you the cost before you commit.
  • Tokens are consumed based on algorithm strength. Regenerating is FREE.
    • That last point is important: you only pay (in tokens) for the initial generation. If you want to change the algorithm, you can regenerate at no extra cost. This encourages experimentation. You are not punished for wanting to try a stronger hash or a different enhancement. You are only charged when you create something new. This model also means that the cost of a link is transparent. You see the price before you generate. There are no hidden fees, no surprise deductions, no fine print. The dashboard tells you exactly what you are spending and why. ---

    Our Features

    We offer a modular system for link encryption and protection. Each component can be combined with others to create a redirect that fits your specific needs. You are not locked into a single preset. You are given a toolkit.

    8 Slug Algorithms

    The slug is the obfuscated portion of the URL—the part that replaces the original link. We support eight algorithms, each with different characteristics:
  • Random — A purely random string. No deterministic relationship to the input. Good for maximum unpredictability.
  • MD5 — A widely known hash function. Fast, but not cryptographically secure. Suitable for casual obfuscation.
  • SHA-256 — A strong, standard hash. Longer output, higher security. A good default for many use cases.
  • SHA-512 — Even stronger than SHA-256. Longer output, more computational cost. For when you want maximum hash strength.
  • HMAC — A keyed hash. Adds a secret key to the process. Useful when you want the slug to be verifiable only by someone with the key.
  • Base64 — Not a hash, but an encoding. Produces a readable, reversible string. Good for aesthetic purposes or when you want a predictable pattern.
  • UUID — A universally unique identifier. Standardized format, globally unique. Good for tracking and uniqueness.
  • BLAKE2b — A modern, fast, cryptographic hash. Strong and efficient. A favorite among security-conscious users.
    • Each algorithm has a different token cost. Stronger algorithms consume more tokens. This is not arbitrary—it reflects the computational resources and security guarantees involved. You choose the trade-off.

    4 Enhancements

    Enhancements modify the visual and structural properties of the slug. They do not change the underlying algorithm; they change how the result looks and feels.
  • Mixed Case — Alternates between uppercase and lowercase letters. Makes the slug harder to read at a glance.
  • Symbols — Inserts special characters. Breaks up patterns and makes the slug less predictable.
  • Underscore — Adds underscores at intervals. A subtle visual modification that can improve readability or aesthetics.
  • Split — Divides the slug into segments. Can make long slugs easier to parse or copy.
    • These enhancements can be combined. For example, you can have a SHA-256 slug with mixed case and symbols. The result is a string that is both cryptographically strong and visually obfuscated.

    4 Protection Providers

    Protection providers add a human-verification step before the redirect is followed. This is the gate within the gate.
  • None — No protection. The redirect happens immediately. Good for low-risk links or when you trust your audience.
  • Math Question — A simple arithmetic question. Easy for humans, difficult for bots. A lightweight barrier.
  • Cloudflare Turnstile — A modern, privacy-friendly CAPTCHA alternative. Invisible to most users, effective against bots.
  • Google reCAPTCHA — The classic CAPTCHA. Widely recognized, widely supported. A strong barrier against automated access.
    • You can also bring your own Turnstile / reCAPTCHA keys. These are stored with AES-256 encryption. This means you can use your own Cloudflare or Google account, keeping control over your verification settings and analytics.

    Token-Based Cost System

    Every generation costs tokens. The cost depends on the algorithm and protection you choose. The dashboard shows you the cost before you generate. This transparency is a core principle. Tokens are not unlimited. They are allocated by the admin when you are approved. This prevents abuse and ensures that the service remains available to serious users.

    Regenerate Link with New Algorithm

    Once you have generated a link, you can regenerate it with a new algorithm or enhancement for free. No tokens are consumed. This is a deliberate design choice: we want you to experiment. We want you to find the right combination for your needs. We do not want you to feel locked in. ---

    Who We Are For

    We are for anyone who wants a link that is not immediately obvious or immediately accessible. That includes:
  • Communities that want to prevent bots from scraping invite links. A Discord server invite is a valuable thing. A bot that scrapes invites can cause chaos. An encrypted redirect with a protection provider stops that.
  • Individuals who want to share a resource but add a small barrier. Not everyone deserves instant access. Sometimes a small hurdle—a math question, a CAPTCHA—is enough to filter out casual visitors.
  • Developers who need a quick, token-based redirect API with multiple algorithms. If you are building something and need a redirect service with a clean API, multiple hash options, and a token system, we are a practical choice.
  • Privacy-conscious users who want to obfuscate the final destination. Sometimes the destination itself is sensitive. An encrypted redirect hides it until the last moment.
  • Anyone who understands that a URL is not just an address. If you have ever looked at a link and thought, "I wish this were less obvious," we are for you.
    • We are not for everyone. We are not a mass-market link shortener. We do not have a free tier with unlimited links. We do not have a mobile app. We do not have a browser extension. We are a focused tool for people who care about link protection. ---

    Our Identity

    We are Creaddinscart · Welcome.ink · Admin · shit.pub. We are a small, admin-mediated service. We are not a giant platform. We are a tool for people who understand that a URL is not just an address—it is a gate. Welcome.ink is the gate. We are part of a larger ecosystem. Creaddinscart is the parent service. Welcome.ink is the encrypted redirect component. Admin is the human who approves requests and manages tokens. shit.pub is a related domain in our network. This identity matters because it tells you what we are not. We are not a faceless corporation. We are not a venture-backed startup. We are not trying to scale to a billion users. We are a small, deliberate, human-operated service. That is our strength. That is our promise. ---

    Why Encrypted Redirects Matter

    In an era of pervasive tracking, automated scraping, and link-based attacks, the humble URL has become a battleground. A link can leak information about the sender, the recipient, and the content. A link can be harvested by bots, shared without permission, or used as a vector for phishing. Encrypted redirects are a response to this reality. By obfuscating the destination, we make it harder for automated systems to understand what a link leads to. By adding protection providers, we make it harder for bots to follow the link at all. By using strong algorithms, we make it harder for anyone to reverse-engineer the original URL. This is not about paranoia. It is about practical privacy. It is about giving individuals and small communities the same level of control that large platforms have. It is about making the web a little less transparent to those who would exploit it. ---

    How to Get Started

    If you want to use Welcome.ink, here is what you do:
  • Join our QQ or Discord. This is the entry point. There is no web signup form. You talk to us.
  • Submit a domain request. Tell us what domain you want to use. We will review it.
  • Wait for admin approval. If approved, you will receive an API key and a token allocation.
  • Sign in at the Dashboard. Use your API key to access your control panel.
  • Generate your first encrypted redirect. Choose your algorithm, enhancements, and protection. See the cost. Generate.
  • Share your link. The world sees a Welcome.ink URL. Only the right people get through.
    • That is it. No hidden steps. No complicated onboarding. No upsells. ---

    Our Principles

    We operate on a few simple principles:
  • Transparency. You see the cost before you generate. You know what you are paying for.
  • Control. You choose the algorithm. You choose the protection. You bring your own keys if you want.
  • Experimentation. Regeneration is free. Try different combinations. Find what works.
  • Human mediation. A real person approves your request. A real person manages the service.
  • Privacy. We do not host your content. We do not track your users. We encrypt the path and step back.
    • These principles are not marketing slogans. They are design decisions. They shape how the service works and who it is for. ---

    Conclusion

    Welcome.ink is an encrypted redirect service. We are a sub-service of Creaddinscart. We are a small, admin-mediated, community-driven tool for people who want more control over their links. We offer eight slug algorithms, four enhancements, four protection providers, a transparent token system, and free regeneration. We are for communities, individuals, developers, and privacy-conscious users. We are not for everyone, and that is okay. If you understand that a URL is not just an address—that it is a gate—then you understand what we do. Welcome.ink is the gate.