Compliance

Compliance overview for the current site

This page explains the legal posture Scientific Revenue is aiming for today: a still-narrow publication model with consent-based analytics and a limited funding-alert signup database that keeps privacy and accessibility obligations manageable while the site remains mostly static.

Last updated

March 30, 2026

Scope of this page

This is a practical compliance overview for the site's current feature set. It is not a substitute for jurisdiction-specific legal advice, especially if Scientific Revenue adds outbound alert campaigns, accounts, submissions, advertising, or other broader data workflows later.

EU-facing expectations

For EU and EEA readers, the key issues for a site like Scientific Revenue are a clear privacy notice, transparent explanation of legal bases, a truthful cookie posture, restraint around non-essential tracking, and an accurate explanation of the reader details now saved through the funding-alert signup form.

The current site still keeps that scope relatively narrow with opt-in analytics, no ad-tech, no reader accounts, and no broader profiling, but it now does maintain a small reader contact database. If the site later expands analytics, introduces embedded third-party tools, or broadens personal-data collection, it should add the necessary consent and request-handling workflow before launch rather than after.

U.S.-facing expectations

For U.S. readers, the main pressure points today are transparency about what is collected, whether personal information is sold or shared, whether the service is directed to children, and whether the public-facing site is accessible.

Scientific Revenue's current posture is intentionally narrow: no sale or sharing for behavioral ads, no child-directed features, no paywall identity layer, a limited alert-signup database, and analytics that can be declined.

Accessibility and public-facing obligations

Because Scientific Revenue is a public-facing publication, accessibility should be treated as part of compliance rather than only as a design preference. The site therefore maintains a separate accessibility statement and should continue to use recognized technical guidance such as WCAG in future development.

What keeps the current posture workable

  • Scientific Revenue is a public-facing publication with no reader accounts, paid memberships, or comments on the public site.
  • The site includes a funding-alert signup form that asks for name, email address, and country and stores those details for later alert list use.
  • The site can load Google Analytics 4 only after a reader opts in. It does not enable Google Signals, ad personalization, or behavior-based profiling tools.
  • Readers can open Scientific Revenue pages and then follow outbound links to official funder or programme pages for primary funding details.
  • If Scientific Revenue adds outbound alert campaigns, accounts, submissions, ad tech, or other broader data workflows later, these notices will be updated before those features go live.

What would trigger another legal pass

  • Launching reader accounts, profiles, or subscriptions
  • Adding contribution forms or user-generated content
  • Expanding analytics beyond the current consent-based setup, or turning on ad tech or third-party embeds that store non-essential identifiers
  • Starting outbound alert campaigns or broader CRM-style use of the signup database without adding the right unsubscribe, retention, and request-handling workflow
  • Collecting direct reader correspondence or other personal submissions at scale
  • Offering paid products, membership, or commerce flows

Funding alerts

Keep the next serious funding page from slipping by.

Get new funding opportunity alerts saved for later outreach use. We ask for your name, email, and country so the list stays usable once the desk starts segmenting alerts by geography and audience.

What lands

Open calls, deadline shifts, and funder moves worth a real second look.

What we save

Your name, email address, and country for future alert list use.

What we do not do

No spam blasts, no ad-audience handoff, and no confirmation email today.

No spam. No confirmation email. Your details are stored for future funding alert use only. Read the privacy notice.