Privacy Policy

Who is responsible for this site?

Lynara is operated by the person identified in our Legal Notice. That page contains the operator's identification and contact information. You can also reach us through the Contact page with questions about this policy or your personal data.

Calculator and citation inputs

Traditional calculator inputs and manually entered citation fields are processed in the browser and are not designed to be stored by Lynara.

DOI citation lookup

When you choose DOI import, the DOI is sent through a Lynara server endpoint to metadata services such as Crossref or the DOI registry. AMA and CSE lookups may also query PubMed/NLM for journal-abbreviation assistance. Imported metadata remains editable.

AI generation

AI generation is disabled on this build, so AI forms do not send study text to an AI provider.

Analytics

Lynara uses Google Analytics 4 for aggregate usage measurement. The production integration starts with analytics and advertising storage denied, Google Signals disabled and ad-personalization signals disabled. In that state Google may receive limited cookieless measurement pings, while storage-based analytics remains unavailable unless the applicable consent state is later updated.

Where consent is required for analytics storage, it will not be granted until the relevant consent controls are configured and the visitor makes the applicable choice.

Lynara's built-in tool-lifecycle analytics events use the tool slug, the current page path and a coarse lifecycle state such as start, completion, error or reset. Lynara does not add calculator values, citation text, AI prompt text or file contents to those built-in analytics event payloads.

Abuse protection

When AI is enabled, production endpoints use human-verification and rate-limit controls. Technical identifiers such as an IP-derived key may be processed for abuse prevention and cost control.

Google AdSense and advertising

Google AdSense advertising is not currently being served by this build. A Google publisher identifier may appear solely to verify site ownership; this does not mean advertisements or advertising cookies are active.

If AdSense is enabled in an approved future release, Google and its advertising partners may receive information such as the page URL and IP address and may use cookies or similar identifiers to deliver and measure ads, protect against fraud and, where applicable consent and settings permit, personalize advertising. Non-personalized ads may still involve data processing for delivery, measurement or fraud prevention.

Where a consent-management platform is legally or contractually required, advertising must remain disabled until the applicable controls are configured and visitors can make the relevant choices. Read how Google uses information from sites that use its services for details about Google's processing and controls. Publisher verification is separate from ad serving: the site's production-domain, consent, publisher and placement requirements must all be satisfied before ads can run.

Cookies and browser storage

Lynara does not intentionally grant analytics or advertising storage while the relevant consent state is denied. Essential infrastructure may use limited technical storage or security mechanisms needed to deliver and protect the service.

When you use Lynara's Save tool feature or browse tool pages, Lynara can store a small list of saved-tool identifiers and recently used tool links in your browser's local storage. This preference data stays in that browser and is not sent to a Lynara account or database by those features. You can remove recent tools from the homepage or clear site storage in your browser.

Cross-style citation handoff may temporarily use session storage so verified source fields can move to the next citation style without retyping. That handoff is cleared after the destination page restores it.

Data retention and your controls

Saved-tool and recent-tool preferences remain in your browser's local storage until you remove them or clear site data. Citation handoff data is temporary session storage. Hosting and security providers may retain technical logs under their own operational retention rules; Lynara does not promise a single retention period for records held by external providers.

You can manage or clear local browser storage in your browser settings. When optional analytics or advertising consent controls are made available, those controls should explain how to make or withdraw a choice. Withdrawing consent does not necessarily undo processing that took place before withdrawal.

Your privacy rights

Depending on the laws that apply to you and the data in question, you may be able to request access, correction, deletion, restriction or portability of your personal data, object to certain processing, and withdraw consent where processing depends on it. You may also have the right to complain to your competent data-protection authority. Send requests via our Contact page; please describe the relevant tool or interaction so we can identify records we actually control. Browser-only inputs may never have been collected by Lynara, while requests concerning Google or another provider's separately held data may also need to be directed to that provider.

Hosting

Infrastructure providers may process standard technical request logs for delivery, reliability and security.

Contact

Use the contact page for privacy or correction questions.