Your CIMER profile

CIMER offers its own reader code sign-in when the Owner connects and enables a delivery service. The prepared provider is Supabase Auth, which processes the email or phone number you use to request a code and manages verification. No ChatGPT account is required for this flow. Existing hosted reader records are retained separately; CIMER does not merge accounts by matching an email address. CIMER stores your reader identifier, verified login contact, membership status and the profile details you choose to provide.

Your choices

Interests and the Read / Listen / Watch preference help order suggested content. Other details, including phone, organisation and location, are optional. An editable profile phone is not a verified login identity. Phone code sign-in must be enabled and verified separately.

Email and SMS marketing are separate optional choices, off by default. Saving a profile records those choices and their history. No automated marketing campaign is connected by this feature. You can update your choices in My CIMER.

Who can see it

You can view and update your profile. The publication Owner can view reader contact details and preferences for membership and consent-based audience work. Public registration never grants staff permissions or a paid membership.

Media and device preferences

Listening plays the article’s recorded narration when an editor has attached it; otherwise it offers clearly labelled browser/device narration. Watch uses a video attached to that article. AI-produced narration and illustrative video are labelled. Registered readers can submit plain-text article replies for editorial approval. Your chosen public reply name is shown, with a generic name used when your profile name is an email address; your login contact and reader identifier are not published. Owner/EIC can approve or hide contributions. The dismissible registration invitation remembers dismissal for the current browser session. Code sign-in normally lasts up to eight hours. If enabled, a trusted-device option can retain a reader session for up to 90 days, subject to the provider’s earlier limits. Tokens are held in secure HttpOnly cookies; CIMER stores token digests and expiry, not the raw tokens. Signing out revokes that CIMER device session. Temporary code requests and rate-limit records expire; they do not count as marketing consent. Staff EOS login remains separate.