Multi-language support and cookie consent updates

Credently now provides seven locale routes across the marketing site, authenticated workspace, and client-facing approval flows. This release pairs broader language coverage with updated cookie consent controls that keep optional analytics and marketing consent denied until the visitor makes a choice.

Why we shipped this

B2B teams send approval requests worldwide. Clients should read deadlines, decision buttons, and certificate details in a familiar language. Visitors to credently.co also deserve clear control over non-essential cookies before measurement scripts run. These updates address both needs.

Seven supported locales

Credently routes the public site and product chrome through locale-prefixed URLs. Supported languages are English (en), Turkish (tr), Arabic (ar), Spanish (es), French (fr), German (de), and Russian (ru). Every locale uses an explicit URL prefix — for example, /en/pricing or /de/pricing — so pages stay shareable and indexable. English remains the default.

The language switcher appears in the marketing header, dashboard navigation, and on client approval pages (request links, portal views, deliverable pages, and certificates). Choose a language from the dropdown; the site reloads in that locale on the same page where possible.

Right-to-left support for Arabic

Arabic is the only locale that renders right-to-left. When you browse in Arabic, the document direction is set to rtl and lang is set to ar. Navigation, forms, and approval layouts follow that reading direction. All other locales use left-to-right layout.

What is localized today

This release makes the product interface and site chrome locale-aware through seven message catalogs, covering navigation, pricing, dashboard labels, authentication screens, error messages, FAQ entries, legal pages, and the cookie banner. Translation coverage is most complete in English and Turkish; some strings in the other five locale routes may still fall back to English while coverage expands.

Long-form blog posts and news articles use a narrower model. Titles, summaries, and metadata may appear in Turkish where provided. Full article bodies are currently available in English and Turkish only. In Arabic, Spanish, French, German, or Russian, article bodies fall back to English when no dedicated translation exists, while surrounding chrome stays in your selected language. The FAQ hub is localized for all seven languages.

Language persistence

Anonymous visitors store the selected language in the NEXT_LOCALE cookie (see Cookie Policy), so return visits reopen in the same language. Signed-in users who switch language also save preferred_locale to their profile, aligning future transactional emails with the UI language when applicable.

Cookie consent updates

Credently now initializes Google Tag Manager (GTM) with optional analytics and advertising consent denied. Essential product functions continue while the visitor decides whether to enable optional categories.

Cookie categories

The banner defines four categories:

• Essential — always on. Required for sign-in, security, language memory, and consent storage.
• Analytics — optional. Aggregated marketing-site usage via Google Analytics through GTM.
• Marketing — optional. Campaign measurement for services such as Google Ads and LinkedIn when enabled in GTM.
• Functional — optional. Records the visitor's preference for optional product and checkout-related functionality.

On first visit, optional toggles default off. Accept all enables analytics, marketing, and functional cookies. Essential only keeps all optional categories disabled. Customize lets you set each category before saving.

Preferences save to localStorage (key cookie_consent) and a companion cookie_consent flag cookie for up to one year unless you clear site data or change settings.

How GTM and analytics load

Credently uses Google Consent Mode v2. Before GTM loads, consent defaults to denied for ad_storage, analytics_storage, ad_user_data, and ad_personalization when no prior choice exists. Saved preferences restore granted or denied states on return visits.

GTM injects after a short post-load delay (about 2.5 seconds) when configured in the deployment environment. Saving preferences immediately updates gtag consent signals.

Our CookiePageTracker sends page_view and pricing_page_view events only when analytics consent is granted. Without it, those events are not pushed to the data layer while essential functionality continues. Analytics and marketing choices update Google's consent signals; the functional preference is stored separately for flows that use it. See the current inventory in our Cookie Policy.

Changing preferences

Reopen Cookie preferences from the site footer anytime to adjust categories. Read how cookies relate to personal data in our Privacy Policy.

This reflects common privacy expectations — ask before optional measurement — but is not a claim of GDPR compliance, ISO certification, or legal adequacy. Review obligations with counsel where needed.

What changed for visitors and customers

Visitors can browse locale-prefixed versions of menus, pricing, and legal pages, with English fallback where a translation is not yet available. Client approval links include the language switcher so recipients can choose their preferred interface locale without an account. First-time visitors see a bottom cookie banner with Accept all, Essential only, and Customize options.

Dashboard users switch language from the nav bar; the choice persists on their profile. International clients can change locale on the approval page independently of the sender's language. Note that blog and news bodies may still appear in English for some locales until dedicated translations ship.

Why this matters

Clear language reduces friction in cross-border approvals. Consent-first analytics respects visitors who expect sites to ask before tracking, with controls documented in our policies.

Next steps

• Review plans on pricing.
• Sign up and set your language from the dashboard.
• Send a test approval link and switch locale on the client page.
• Read cookie-policy and privacy-policy; adjust preferences from the footer.
• Browse the FAQ in your locale.

We will keep adding editorial translations and refining consent behavior. Feedback: hello@credently.co.