DocsOpen appApp

DOCUMENTATION / PUBLIC ALPHA

BUILD WITH
LESS EXPOSURE.

SHREDDAR compiles a sensitive document or request into the minimum useful context an AI task needs, keeps identity mappings inside a trusted boundary, and leaves a privacy-minimized receipt.

OPEN THE APP ↗SEE HOW IT WORKS →
PRODUCT
LOCAL-FIRST PRIVACY COMPILER
STATUS
PUBLIC ALPHA
LAUNCH
PLANNED / PONS V2
TOKEN ADDRESS
NOT DEPLOYED
A carbon privacy compiler turns a private stack of source documents into a small set of lime protected context bands while rejecting coral fragments
THE PRIVACY COMPILER / 01SOURCE IN. MINIMUM CONTEXT OUT.

01 / OVERVIEW

Your AI needs context.
Not identity.

Useful documents mix task-relevant meaning with names, contact details, credentials, exact values, wallet information, and proprietary facts. Sending the complete source to every model or tool creates exposure the job may not require.

SHREDDAR treats privacy as a compilation decision: which facts are relevant, how precise they must be, where they may travel, and what must stay inside the trusted boundary.

The product and the planned token launch are separate. The website and app do not connect wallets, and a token is not required to use the alpha. Any token transaction takes place through pons, outside the SHREDDAR product interface.

Explore the complete product system →

02 / ARCHITECTURE

A boundary you can
inspect end to end.

  1. 01

    DETECT

    Find sensitive entities, secrets, exact values, and linkable facts.

  2. 02

    DECIDE

    Apply the stated task and policy to determine what is actually necessary.

  3. 03

    TRANSFORM

    Pseudonymize, generalize, conceptualize, remove, block, or keep local.

  4. 04

    ROUTE

    Send only approved protected context to the configured model or tool.

  5. 05

    INSPECT + STITCH

    Guard the return and resolve authorized current-session references locally.

  6. 06

    RECEIPT

    Record policy, counts, route, timing, and integrity metadata—not the source.

One private document is divided into three bounded routes, with only one route carrying protected lime context to an external processor
SEMANTIC SHARD / 02LESS CONTEXT PER ROUTE.
01

PUBLIC APP

Browser-memory product demonstration using synthetic or authorized content. No account or wallet required.

02

SELF-HOSTED GATEWAY

OpenAI-compatible request path that runs inside the deployer's own trust boundary.

03

POLICY + VAULT

Explicit transformation rules and current-session identity mappings that remain local.

04

PRIVACY RECEIPTS

Transformation, routing, timing, and integrity evidence without prompt or mapping retention.

03 / PRODUCT GOALS

Reduce exposure.
Keep the task useful.

01

UTILITY

Preserve the meaning an AI task needs while reducing unnecessary disclosure.

02

CONTROL

Make outbound context visible before inference and keep identity mappings local.

03

SAFETY

Fail closed on credentials, local-only classes, unsafe reconstruction, and unknown routes.

04

EVIDENCE

Record transformations and integrity metadata without recording prompts or Vault mappings.

NORTH-STAR MEASURE

Sensitive context prevented from leaving trusted environments in successfully completed protected requests—reported with task utility and reconstruction accuracy, never by itself.

04 / PLANNED TOKEN LAUNCH

Fair curve.
Public terms.

STATUSPRE-LAUNCHNO SHREDDAR TOKEN CONTRACT EXISTS YET

SHREDDAR plans to launch through pons v2 on Robinhood Chain. Pons mints the fixed supply to a constant-product bonding curve, then graduates the launch into a permanently locked full-range Uniswap v4 pool. Final parameters and addresses will be verified onchain before they are presented as live.

01

CREATE

The fixed supply is minted to the pons curve. No private presale or pre-minted team allocation.

02

CURVE

Anyone can buy or sell against deterministic constant-product pricing. Larger orders create more price impact.

03

GRADUATE

When the curve reaches its threshold, graduation can complete permissionlessly.

04

LOCKED POOL

Trading moves to a full-range Uniswap v4 pool and the liquidity position remains permanently locked.

PLANNED LAUNCH TERMS

Venue
pons v2
Network
Robinhood Chain / 4663
Price discovery
Constant-product bonding curve
Private presale
None
Pre-minted team allocation
None
SHREDDAR creator fee
2% of the quote leg
Token address
Not deployed
Launch date
Not announced
TOKEN ROLE

Participation, not product access.

The planned token does not gate the SHREDDAR app, unlock privacy processing, or replace strict PAYG product pricing. No wallet connection is being added to the website or app.

Holding the token does not represent equity, ownership, revenue share, a claim on treasury assets, guaranteed utility, or an expectation of profit. Any future rights or functions require separate implementation and documentation before they can be claimed.

READ PONS V2 DOCS ↗REVIEW PONS SOURCE ↗ROBINHOOD CHAIN NETWORK ↗

05 / DEVELOPERS

Run the boundary
where you trust it.

01 / RUN
docker compose up --build
02 / POINT
OPENAI_BASE_URL=http://127.0.0.1:8787/v1
03 / VERIFY
curl http://127.0.0.1:8787/healthz

OPENAI-COMPATIBLE

Existing clients.
Protected messages.

from openai import OpenAI

client = OpenAI(
    base_url="http://127.0.0.1:8787/v1",
    api_key="local-dev"
)

response = client.chat.completions.create(
    model="configured-upstream",
    messages=[{"role": "user", "content": private_context}],
    extra_body={
        "shreddar_task": "Review termination obligations",
        "shreddar_policy": "strict-v1"
    }
)

print(response.model_extra["shreddar"]["receipt"])
METHODENDPOINTJOB
POST/v1/analyzeClassify risk and preview policy actions.
POST/v1/protectCompile raw task context inside your boundary.
POST/v1/reconstructResolve authorized current-session placeholders.
POST/v1/chat/completionsProtect, infer, inspect and STITCH.
POST/v1/shardCreate semantic compartments for local routing.
GET/v1/receiptsInspect privacy-safe execution evidence.

06 / ROADMAP

Evidence before
expansion.

  1. 01LIVE

    PRODUCT ALPHA

    Browser-local playground, policy controls, SHARD previews, receipts, and a self-hosted OpenAI-compatible gateway.

  2. 02ACTIVE

    VALIDATION

    Five permissioned non-team developers complete useful protected requests and inspect the outbound context and receipt.

  3. 03PLANNED

    LAUNCH READINESS

    Publish final terms, fee recipient, risk review, creator-wallet policy, launch URL, and verified contract address.

  4. 04PLANNED

    PONS FAIR LAUNCH

    Launch through the public pons v2 curve only after the readiness record is complete. No private round.

  5. 05AFTER LAUNCH

    OPEN REPORTING

    Track product evidence, creator-fee receipts, treasury use, and launch state separately from token price or volume.

A protected data boundary emits sparse lime context and a separate abstract evidence receipt without source content
VERIFY, THEN TRUST / 03RECEIPTS ARE EVIDENCE—NOT A GUARANTEE.

07 / RISKS + LIMITS

Know what can
still go wrong.

PRODUCT

Detection can miss sensitive data or remove useful context. Review protected output before external inference.

MARKET

A launch token can be volatile, illiquid, or lose all value. Nothing in these docs is a return promise or investment advice.

PROTOCOL

Smart contracts, wallets, RPCs, indexers, the bonding curve, and graduation can fail or behave unexpectedly.

LINKABILITY

Pseudonymized or sharded information may remain linkable. Exposure reduction is not anonymity or cryptographic secrecy.

08 / QUICK ANSWERS

Before you act.

Does SHREDDAR require a wallet?

No. The website, public app, and self-hosted privacy gateway do not require or include wallet connection. A future token trade would happen on pons.

Is the token required to use the product?

No. Product access and token participation are separate. The alpha remains open without a token.

What does the 2% fee mean?

It is the planned SHREDDAR creator fee on the quote side of each trade. Pons' current 1% base fee applies separately, making the expected ordinary total 3% if that base rate is unchanged at launch.

Where is the contract address?

There is no SHREDDAR token contract yet. The verified address, launch transaction, terms, and official pons page will be published together after deployment.

ALPHA + PRE-LAUNCH BOUNDARY

The public playground is browser-local. The gateway behind https://app.shreddar.pro is authenticated and reserved for operator verification; it is not anonymous hosted private-data processing. The planned pons launch has not occurred, no SHREDDAR token contract exists, and these launch terms are not an offer, return claim, or representation that a token has current utility.

Review product security and limitations →