Gloslyn

Support

Help for installation, translation, Discord permissions, billing, and privacy. Legal pages: Privacy · Terms.

Human contact: support@example.com(set SUPPORT_EMAIL / LEGAL_CONTACT_EMAIL)

Topics

Installation

Sign in, open Servers, use Add to Discord (least privilege — never Administrator).

Discord permissions

View Channel, Send Messages, Embed Links, Read Message History on linked channels.

Translation groups

One language per channel in a group. Auto-translate posts without /translate each time.

Languages

Assign ISO-style language codes per channel; keep sibling channels in the same group.

Glossary

Approve terminology so clan slang and proper names stay consistent.

Quota

Billable characters = source × targets. At 100%, translation stops — no silent overage.

Billing

Stripe checkout when configured; otherwise Join Beta / Contact Us from Pricing.

TradLinker migration

Paste /6-show_groups URL in Import — dry run, preview, conflicts, then apply. No secrets.

Voice

Optional / premium / beta and kill-switched until validated.

Common errors

Missing intents, missing channel access, worker down, provider not configured, quota exhausted.

Privacy

Message/audio storage defaults off; tenant isolation. See Privacy Policy.

AI support assistant UI is prepared — OpenAI-backed answers stay off until provider economics are explicitly approved.

FAQ

How do I install the bot?
Sign in on the dashboard, open Servers, and use Add to Discord. The invite uses least-privilege permissions — Administrator is never required.
Translations are not posting
Confirm the translation group is enabled, Message Content Intent is on for the Discord app, the bot can read the source and send to targets, the worker is running, and a real provider (DeepL or LibreTranslate) is configured.
Missing permissions / Missing Access
Check channel overwrites for the bot role. It needs View Channel, Send Messages, Embed Links, Read Message History (and Connect/Speak only if voice is enabled).
Billing or cancel
Use the dashboard Billing page / Stripe Customer Portal when configured. Removing the bot from a server stops new guild events but does not by itself cancel a paid subscription.

Request deletion

During beta there is no fully automated self-service erasure portal. Email support@example.com from the address linked to your Discord login when possible.

Include:

  • Discord user ID (optional but speeds verification)
  • Workspace name / guild ID(s) in scope
  • What to delete: account/session data, guild configuration, glossary, translation memory, and/or the whole workspace

What we can delete or anonymize:

  • Dashboard user/session records for your account
  • Guild/server configuration and translation groups for scoped servers
  • Glossary entries and translation memory / suggestions for that workspace
  • Operational job/cache artifacts tied to that tenant when still present

What may be retained:

  • Stripe invoices and accounting records required by law or payment processors
  • Minimal security/abuse logs for a limited period when needed to protect the service

Removing the bot from Discord stops new processing for that guild but does not cancel Stripe or erase historical billing metadata. Full details: Privacy Policy.

Talk to a human

For security incidents, refunds, legal notices, or deletion confirmation, email support@example.com. The Ask assistant cannot change plans, refund, or access other tenants.

Knowledge base

  • How do I add the bot?

    Open the dashboard Servers page and use Add to Discord / the invite URL. Required scopes: bot + applications.commands. Least-privilege permissions include View Channels, Send Messages, Send Messages in Threads, Embed Links, Attach Files, Read Message History, Use Application Commands, plus Connect/Speak if voice features are enabled later. Administrator is never required.

  • Which Discord permissions are required?

    If translations fail with Missing Access / Missing Permissions, check channel and role overwrites for the bot role. The bot needs view + send in source and target channels, and read history for replies/edits. Do not grant Administrator.

  • How do I configure languages / translation groups?

    Create a translation group linking a source channel/language to one or more target channels/languages and enable auto-translate. Example: #italiano (it) → #english (en). Messages from humans in the source are queued; the worker translates with a real provider and posts to targets while preserving URLs and mentions when supported.

  • Why isn't my message translated?

    Checklist: (1) bot online in the guild, (2) translation group auto-translate ON, (3) Message Content Intent enabled on the Discord application, (4) bot can read the source channel and send to the target, (5) worker process is running, (6) a real translation provider is configured (DeepL or LibreTranslate) — mock providers are not valid for live tests, (7) kill switch TRANSLATION_ENABLED is true.

  • Which languages are supported?

    Supported languages depend on the active translation provider (for example DeepL Free/API or LibreTranslate). Configure language codes in translation groups using the provider’s language codes (e.g. it, en). If a language pair is unsupported by the provider, translation jobs fail with a provider error rather than inventing output.

  • How much does it cost?

    Public plans: Free (basic text), Starter (more text/channels), Pro (voice + premium capabilities when enabled), Community (higher usage). During Beta, displayed amounts may say “Beta pricing” until Owner locks Stripe prices. Checkout uses server-side Stripe price IDs — never client-supplied price IDs.

  • How do quotas and usage work?

    Usage is recorded per workspace in the usage ledger (characters, provider, estimated cost, correlation id). When monthly character or cost caps are hit, translation may degrade or stop according to the plan cost policy. Workspace A never consumes workspace B’s quota.

  • How does voice translation work?

    Voice translation is gated by plan entitlements and kill switches (VOICE_TRANSLATION_ENABLED, LIVE_VOICE_ENABLED, etc.). In the controlled Beta text test, voice features stay OFF. When enabled on Pro/Community, the bot needs Connect and Speak; audio defaults do not store voice content (STORE_VOICE_AUDIO=false).

  • How do I cancel?

    Manage subscription from the Billing page (Stripe Customer Portal when configured). Removing the bot from a Discord server stops new events from that guild but does not by itself cancel a paid Stripe subscription. For account deletion / data erasure requests, use Talk to a human.

  • Common errors

    Frequent causes: invalid Discord bot token, Message Content Intent off, provider API key missing/invalid, DATABASE_URL unreachable, worker not running, free-tier host spin-down, missing channel permissions. Check service health endpoints and Render/host logs for migration, Discord login, and provider failures.