Privacy

Technical access data

When the website is accessed, technically necessary access data is generated, such as the requested URL, time, HTTP status, browser/device information, referrer and IP address. This data is required to deliver the website, detect abuse, analyse technical errors and ensure stable operation.

Where rechtundgesetz.ch processes its own usage, search, security or statistical data, the IP address is not stored as a plain-text profile. Where possible, it is processed technically only for a short period and then shortened, hashed or used in pseudonymised form. This allows repeated technical processes to be recognised without keeping a directly readable IP address in the application data.

Server and security logs of the hosting operation may separately contain technically necessary access data. This data is not used for public statistics, convenience functions or personal usage profiles.

Search, rate limits and retry logic

Search queries are processed to calculate results, limit abuse and ensure the technical stability of the search. Pseudonymised technical characteristics may be used for fair-use limits, retry logic, technical retries or abuse protection.

The application is designed not to store plain-text IP addresses for these purposes in statistical, convenience or search-history data. Search and security data is handled separately from public content and used only for as long as required for operation, stability, error analysis or abuse protection.

User account and community functions

When an account is created or a community function is used, data including email address, username, profile information, roles/rights, verification status, logins, ratings, comments, tags, links, moderation information and technical security evidence may be processed.

For public proposals, the normalised legal-content reference, submission and moderation status, publishable reasons for decisions, and the version and hash of the accepted community rules are also stored. Internal moderation notes are not public and are not shown to the submitting person.

Private tags, their names, symbols, sorting and assignments are account-bound organisational data. They are not returned in public tag or community queries and are not shared with team members.

Subscriptions, payments and invoices

For User+ and Team/Professional, data including product, subscription status, monthly contractual period, cancellation status, payment status, invoice references, amount, currency, tax status and technical provider references is processed. Payment instruments such as full card details are processed by the payment service used and are not stored in the application.

Provider events whose signatures have been verified are logged idempotently so that payments, failed attempts, refunds and disputes can be reliably assigned. Only the scope necessary for operation, support, fraud prevention, accounting and statutory retention is stored.

Teams and workspaces

For teams, the name, owner, memberships, roles, invitation status, ownership transfers, seat usage and security- and billing-relevant audit events are processed. Members generally see only the profile data required for collaboration and role management.

For unambiguous administration of active memberships, the current team owner is additionally shown the login/system email address stored in the user account for each active team member. This address is not visible to ordinary team members and is not made available to them through the individual display-name setting or the directory mode. It is used in particular to identify members reliably before removal or an ownership transfer.

Personal dossiers, favourites, histories and private tags remain assigned to the personal user account and are not transferred to the owner when joining or leaving a team. Team data is assigned to a separate team workspace. Active members can read and edit its team dossiers; only the owner can permanently delete them and export the complete workspace. By default, the owner has no access to personal content or individual quota usage; an enabled statistic can display numerical totals only.

When a transfer of a personal dossier is expressly confirmed, its workspace assignment together with its content and notes is atomically changed to the team and logged as an audit event. The dossier then remains team data even if the transferring person leaves the team. On final account deletion, personal creator and transfer references are removed from retained team data.

After a team subscription ends, the team workspace may remain available to the owner for 30 days in read/export mode and is then archived. Team memberships, invitations and audit data may, where necessary, be retained separately from the personal account.

Dossiers, templates and change monitoring

Dossiers and custom templates may contain names, descriptions, notes, sorting and references to legal content. Monitoring processes the monitored dossier item, the last checked legal status, detected version changes, check times and delivery records.

Optional digest emails are disabled by default. Eligible users can independently choose off, daily, monthly or yearly. The summary includes only undelivered events from personal workspaces or teams of which the person is currently a member; deliveries are deduplicated per event and user.

Deactivate or delete account

An account can be deactivated or permanently deleted. Deactivation blocks access and turns off the optional monitoring summary; personal account data is retained for possible reactivation.

On final account deletion, login data, email address, display name, 2FA data, tokens, favourites, personal history, personal dossiers, personal templates and personal monitoring settings are removed. Ratings may be retained without user attribution as anonymised content signals. Comments and personal community submissions are removed. Team dossiers remain with the team; references to the deleted person are removed from them. Usage and search data is separated from the account; aggregated or no-longer-personal signals may be retained to optimise the site.

Communication

When contact is made, the submitted information is processed so that the enquiry can be answered and documented in a traceable manner.

Supporter redirect and click counting

When an approved advertising material or an entry on the Supporters page is clicked, the click may be routed via an internal redirect from rechtundgesetz.ch to the supporter’s target page. For supporter reports, only aggregated daily values such as date, campaign, advertising material, slot or Supporters page, format, language and target host are counted.

For this supporter reporting, no plain-text IP addresses, user IDs or personal user profiles are provided to supporters or advertising customers. The evaluation is used to document the booked advertising presence and remains separate from personal community, account or search usage.

Public legal data

Legislation, ordinance, article and systematic-classification data comes from publicly accessible sources. This content is generally not personal data of users; it is processed for search, presentation, linking and classification.

Technically necessary

Required for language, session, form protection, security and storage of the cookie choice. This category cannot be disabled.

Functional / first-party

Optional convenience functions and internal relevance measurement on our own infrastructure. These include, for example, recently read content, anonymous public-rating identifiers and aggregated usage signals to make frequently requested content more visible.

Some convenience functions can only be used with this consent. Fair use.

Third-party / analytics

Optional third-party analytics, in particular Google Analytics. This category is loaded only after consent and is separate from internal first-party measurement.