Effective and last reviewed: 1 November 2026.
About these terms
These Terms of Use (“Terms”) govern access to and use of rausr.com, its articles, Graphic Design Wiki, portfolio and service pages, search, contact and newsletter links, and any authorised use of the Rausr Publisher macOS application, Safari Web Extension, publishing adapters, and Reddit research bridge (together, the “Services”).
The Services are operated by:
rausr s. r. o.
Čiližská 5
821 07 Bratislava, Slovakia
Company ID: 57401322
Tax ID: 2122704980
Email: hello@rausr.com
By using the Services, you agree to these Terms. If you use them for a company or another organisation, you confirm that you have authority to bind that organisation. If you do not agree, do not use the affected Service.
Any design project, consultancy, production work, licence, or other paid engagement is governed by its quotation, order, statement of work, licence, or contract. If those terms conflict with these Terms, the specific written agreement controls for that engagement.
Who may use the Services
rausr.com is publicly accessible and does not currently offer visitor accounts. You may browse it if you can lawfully do so. If you have not reached the age at which you can form a binding contract where you live, use the Services only with the involvement of a parent or legal guardian.
Unless rausr separately authorises access in writing, Rausr Publisher is a private operational tool for rausr and approved collaborators. Describing the app publicly does not grant a download, installation, source-code, credential, API, or publishing licence. An authorised user must also comply with any installation instructions, platform permissions, and supplemental terms supplied with the app.
Website content and functionality
Editorial and educational material
Articles, Wiki guides, reports, examples, diagrams, images, opinions, and search results are provided for general information and education. They are not legal, financial, tax, medical, technical-security, or other regulated professional advice. Design, marketing, production, accessibility, technology, and platform practices change; you should verify information that matters to a decision or project.
Search results are generated from rausr’s public content index. A result, tag, related-content suggestion, source link, or ranking is an aid to navigation, not an endorsement or guarantee of completeness.
Portfolio, case studies, services and quotations
Portfolio and case-study pages illustrate selected work and may include rausr-owned material, client work, third-party assets, mockups, prototypes, concepts, or historical versions. They do not promise that another project will achieve the same result. Availability, timing, scope, production specifications, fees, usage rights, and deliverables are agreed separately in writing.
Nothing on the website is a binding offer. Sending a contact form or message does not create a client relationship, duty to accept a project, exclusivity obligation, or confidentiality agreement. Do not send confidential information until we have agreed how it will be handled.
Newsletter, contact and external links
The newsletter link opens rausr’s publication on Substack. Social, messaging, source, and partner links open third-party services. Their terms and privacy notices apply when you use them. A link does not mean that rausr controls or endorses every statement, product, security practice, or later change on the destination website.
Acceptable use
You must not use the Services to:
- break applicable law, infringe another person’s rights, or encourage unlawful conduct;
- upload, send, publish, or distribute malware, deceptive code, spam, harassment, unlawful personal data, or content you are not entitled to use;
- probe, scan, disrupt, overload, reverse engineer, or bypass security, authentication, rate limits, access controls, consent controls, or technical restrictions, except where applicable law expressly permits security research that cannot be restricted by contract;
- impersonate rausr, an author, client, platform, or another person, or falsely suggest sponsorship, partnership, certification, or endorsement;
- scrape or extract the Services in a manner that is abusive, defeats
robots.txt, creates an unreasonable load, reconstructs a database, or is used to train or improve a machine-learning or generative-AI model without prior written permission; or - use contact details or public content for unsolicited bulk marketing.
Normal browsing, linking, quoting within applicable law, RSS use, accessibility tools, and indexing by conventional search engines that respect our technical instructions are permitted. If you need broader automated access, archival rights, republication, or a data feed, contact us first.
Intellectual property and content permissions
rausr materials
Unless stated otherwise, the website design, rausr name and branding, original text, illustrations, software interfaces, compilations, taxonomies, and rausr-created media are owned by or licensed to rausr and protected by copyright, trademark, database, and other laws. All rights not expressly granted are reserved.
You may view the website, share links to public pages, and make a reasonable temporary or personal copy for lawful, non-commercial reference. You may quote limited passages with clear attribution and a link where allowed by law. You may not republish a complete article, guide, image collection, portfolio project, source compilation, or substantial part of the website without written permission.
Client, partner and third-party material
Names, logos, images, trademarks, and other material belonging to clients, partners, authors, platforms, or other rights holders remain theirs. Display in a case study, source list, article, or interface does not grant you a licence to reuse it. Nominative references to Apple, Google, Blogger, WordPress.com, Automattic, Medium, Substack, LinkedIn, Meta, Facebook, Contra, Reddit, Devvit, or other services identify interoperability only.
AI-assisted material
Some editorial imagery or drafts may be created or edited with generative-AI tools under human direction. AI assistance does not change your obligation to respect applicable rights, nor does it guarantee that an output is accurate, unique, or suitable for a particular use. You may not treat an illustrative or conceptual image as documentary evidence.
Messages, supplied material and feedback
You retain rights in material you send to us. You give rausr a limited, non-exclusive permission to receive, copy, review, and use it as needed to answer your request, assess a possible project, perform an agreed service, protect the Services, or comply with law. You confirm that you are entitled to provide it.
If you voluntarily send product feedback or suggestions without a separate confidentiality agreement, rausr may use them to improve the Services without payment or an obligation to implement them. This does not transfer ownership of your unrelated work or confidential client material.
Rausr Publisher
Purpose and local project access
Rausr Publisher is a custom macOS companion app and Safari Web Extension for authorised editorial work. It can read metadata and content from a user-selected local Hugo project, display article status, prepare excerpts and social copy, call local publishing adapters, open third-party editors, copy prepared material to the clipboard, upload a selected public header image where supported, and keep local destination mappings and activity history.
Subject to these Terms and any separate written instructions, rausr grants an authorised user a limited, non-exclusive, non-transferable, revocable licence to install and use the supplied Publisher build solely for approved internal editorial work. The user may not redistribute, sell, sublicense, publish, or provide the app or its credentials to another person, except where a component or source file is expressly governed by a separate open-source licence or rausr gives written permission.
The app may create a new local Hugo research brief only after an explicit user action. A generated brief is saved with draft: true; it is not automatically published. Users should keep appropriate repository backups and review file changes before committing or deploying them.
Direct and assisted publishing
Publisher supports two kinds of workflow:
- Direct API workflows may create, update, schedule, draft, or publish content through supported Blogger, WordPress.com, Medium, or Facebook interfaces, depending on the connected account, available API, selected mode, and platform permissions.
- Assisted workflows prepare content for services such as Medium, Substack, LinkedIn, Facebook, or Contra, copy it to the clipboard, and open the relevant third-party page. The user remains responsible for reviewing, pasting, completing, and submitting the external post and for recording its status in Publisher.
Browsing the article library, filtering, selecting, previewing, or opening the review step does not itself authorise an external write. In a direct workflow, pressing the final publish confirmation is your instruction to perform the described remote action. Remote publishing can make content public immediately, notify subscribers or followers, consume platform quotas, and create or update a record that must be corrected on the third-party platform.
Assisted-workflow status and URLs are records entered by the user. They are not independent proof that an external draft or post exists, remains available, has the displayed visibility, or was published at the recorded time.
Partial editions, source links and canonical URLs
Publisher can prepare partial editions of rausr articles for Blogger, WordPress.com, and Medium, and teasers or social posts for other destinations. Cut points, excerpt percentages, tags, titles, images, canonical fields, and source links are conveniences. The authorised user must verify formatting, attribution, image rights, canonical configuration, disclosure, and the destination’s rules before publication.
Platform capabilities differ. For example, an API may not offer portable canonical settings, updates, unpublished posts, scheduling, or image handling in the same way as the platform’s own editor. Publisher may skip an existing mapping or require an assisted workflow to reduce accidental duplicates, but it cannot guarantee that duplicates, broken layouts, stale metadata, or conflicting canonical signals will never occur.
Credentials, accounts and permissions
Authorised users must connect only accounts, pages, blogs, sites, publications, and communities they are entitled to manage. They are responsible for obtaining required administrator roles, API approval, OAuth consent, platform permissions, and any separate commercial-use approval.
Publisher stores configuration, mappings, activity records, and supported credentials locally in the app’s private Application Support area or the relevant local configuration directory. A credential may permit remote publishing. Keep the Mac account, repository, OAuth client file, access tokens, Devvit managed token, and backups secure; never commit them to source control or share them in screenshots, issues, or chat. Revoke and replace a credential promptly if it may have been exposed.
The app is not a password manager or backup service. Removing the app, changing a path, clearing local data, revoking a token, or changing a third-party account can make mappings or publishing functions unavailable.
Editorial responsibility
The user who authorises publication is responsible for the final content, claims, sources, spelling, disclosures, permissions, privacy, advertising compliance, and destination settings. Generated summaries, hashtags, excerpts, topic suggestions, schedules, and research briefs are starting points and can be incomplete or wrong. Review primary sources and the actual destination preview before publishing.
Reddit Radar and the Devvit bridge
What the feature does
The Publisher Ideas workspace can request a bounded daily design-signal report through a private app hosted on Reddit’s Developer Platform (Devvit). A managed devvit_at_… App Token authenticates Publisher to the approved external endpoint. Devvit handles Reddit authentication and reads the configured public communities through Reddit’s supported interface.
For a scan, the bridge accepts no more than eight valid safe-for-work community names and requests bounded hot and daily-top listings. It returns only the public post ID, title, community name, permalink, score, comment count, and creation time needed for local editorial comparison.
Publisher then performs deterministic local clustering, ranks recurring questions by discussion strength and community breadth, and compares them with titles, descriptions, summaries, and SEO tags in the local rausr Blog and Wiki. It can omit ideas too similar to existing coverage and keep source links visible for human review.
What the feature does not do
The bridge does not return or intentionally store Reddit usernames, profiles, comment text, post bodies, cookies, private messages, or browser sessions. It does not post, comment, vote, follow, message users, moderate communities, or try to identify or profile Reddit users. Reddit material is not used to train a machine-learning or generative-AI model through this feature.
The implementation does not use browser-account cookies, rotating identities, scraping bypasses, or retries intended to evade Reddit limits. r/all, r/popular, and r/nsfw are rejected by the bridge.
Caching, cooldown and draft creation
Publisher builds one cached report per local calendar day under normal operation, deletes the cached report after 48 hours, and applies a 15-minute manual-scan cooldown. These controls reduce repeated requests but do not replace Reddit’s own limits or approval requirements.
A source title is a demand signal, not evidence for an article. If the user explicitly creates a research brief, Publisher uses generic signal labels rather than presenting Reddit titles as rausr authorship and instructs the editor to find primary sources, documented examples, and original analysis. The user must verify the resulting work and preserve any attribution required by law or platform terms.
Reddit terms, access and attribution
Use of the bridge is subject to Reddit’s Developer Terms, Data API Terms, applicable Developer documentation, community rules, rate limits, approval conditions, and any separate agreement required for commercial use. External Endpoints are a limited-access Devvit capability and can be changed, suspended, or withdrawn by Reddit.
The Devvit managed token is a long-lived secret and requests execute as the app account. Only authorised trusted services may call the endpoint. Rausr Publisher and Reddit Radar are independent rausr tools; Reddit does not sponsor, endorse, or partner with rausr merely because Devvit or public Reddit signals are used.
Third-party platforms and services
The Services interoperate with or link to third parties including Apple/Safari, Netlify, CookieHub, Google/Blogger, WordPress.com/Automattic, Medium, Substack, LinkedIn, Meta/Facebook, Contra, Reddit/Devvit, Zapier, and content-delivery providers. Each third party controls its own service, terms, fees, review, permissions, data handling, uptime, formats, APIs, moderation, and account decisions.
You must follow the terms and policies of every connected destination. rausr cannot grant rights in a third-party API or account and is not responsible for a platform rejecting, editing, restricting, labelling, demonetising, removing, or duplicating content; revoking a token; changing an API; applying a fee; suspending an account; or ending a feature.
No reference to or interoperability with a third party creates an agency, partnership, sponsorship, warranty, or endorsement. Third-party names and marks belong to their owners.
Privacy and data protection
Our Privacy Policy & Cookies explains website logs, contact forms, search, CookieHub, Analytics, advertising measurement, service providers, public content, data retention, and your rights. It forms part of these Terms where relevant.
Publisher users must handle credentials, drafts, client material, subscriber information, social-platform data, and any personal data lawfully and securely. Do not use Publisher to upload personal data or confidential material unless you have an appropriate legal basis, authority, destination, and security arrangement.
Availability, changes and security
We may maintain, improve, limit, suspend, or discontinue any part of the Services. Content, taxonomies, search indexes, layouts, integrations, adapters, supported platforms, excerpt rules, API versions, research sources, and system requirements can change. We do not promise uninterrupted availability, backward compatibility, support, or a particular publishing result.
We take reasonable measures to protect the Services, but no website, local app, extension, API, clipboard, computer, or third-party platform is completely secure or error-free. You are responsible for a secure device, current backups, appropriate access controls, and checking remote results.
If you discover a security problem, stop using the affected function and report it privately to hello@rausr.com. Do not exploit it, access unrelated data, or disclose details before there has been a reasonable opportunity to investigate and remediate the issue.
Disclaimers
To the extent permitted by law, the Services are provided “as is” and “as available”. rausr does not warrant that content is complete, current, error-free, non-infringing, or suitable for a specific purpose; that a generated draft or suggestion is original or accurate; that a remote platform will accept or preserve a post; or that an integration will remain available.
You remain responsible for professional judgment, source checking, production testing, legal review, backups, credentials, account permissions, and every final publication decision. Nothing in these Terms excludes a warranty or right that cannot lawfully be excluded.
Limitation of liability
To the fullest extent permitted by applicable law, rausr is not liable for indirect, incidental, special, punitive, or consequential loss; lost profits, revenue, opportunity, goodwill, traffic, rankings, or data; unauthorised account access caused by a user’s credential handling; or losses caused by a third-party platform, API change, content removal, outage, account action, assisted-workflow error, or failure to review a publication.
For claims relating only to free website access or an authorised no-fee Publisher copy, rausr’s aggregate liability is limited to EUR 100. For a paid licence or service, aggregate liability under these Terms is limited to the amount paid for the affected Service during the twelve months before the event giving rise to the claim. Separate client contracts may set different limits.
These limits do not apply where liability cannot be limited under applicable law, including liability for fraud, wilful misconduct, or death or personal injury caused by negligence where such an exclusion is prohibited. Mandatory consumer rights remain unaffected.
Responsibility for misuse
If you use the Services for a business or organisation, you agree to defend and indemnify rausr against third-party claims and reasonable losses arising from your unlawful misuse of the Services, content you publish through Publisher, infringement caused by material you supplied, or use of an account or credential without authority. This obligation does not apply to the extent a claim was caused by rausr or cannot lawfully be imposed. Consumers are not required to indemnify rausr beyond what mandatory law permits.
Suspension and termination
We may restrict or end access to a non-public Service, integration, credential, or authorised Publisher copy if access is no longer approved, creates a security or legal risk, breaches these Terms, infringes rights, threatens a third-party account, or could harm rausr, a platform, or another person.
You may stop using the Services at any time and may revoke connected third-party tokens through the relevant provider. Provisions that by their nature should survive—such as ownership, accrued payment duties, disclaimers, liability limits, responsibility for misuse, and dispute terms—continue after access ends.
Changes to these terms
We may update these Terms when the Services, Publisher integrations, platform rules, or law change. The effective and review date at the top identifies the current version. Material changes will be highlighted on this page or communicated through another appropriate channel before they apply where required by law.
Continued use after an updated version takes effect means acceptance where that is legally valid. A change that requires separate consent will not be treated as accepted merely because you continued browsing.
Governing law and disputes
These Terms are governed by the laws of the Slovak Republic, without prejudice to mandatory conflict-of-law rules or consumer protections that apply in your country of residence.
Before starting formal proceedings, please contact us and give both sides a reasonable opportunity to resolve the issue. Unless mandatory law provides otherwise, courts with jurisdiction in Bratislava, Slovakia, have exclusive jurisdiction. An EU or EEA consumer may retain the right to bring a claim in the courts of their home country.
General provisions
If a provision is found invalid or unenforceable, it will be limited to the minimum extent necessary and the remaining provisions will continue. Failure to enforce a provision is not a waiver. You may not transfer an authorised Publisher licence or access without written permission. rausr may transfer these Terms as part of a merger, reorganisation, sale of business, or transfer of the relevant Service, subject to applicable law.
These Terms, the Privacy Policy & Cookies, and any applicable written service or licence agreement form the agreement between you and rausr concerning the relevant Service and replace earlier discussions on that subject.
Contact
Questions about these Terms, permissions, security reports, or content complaints can be sent to:
rausr s. r. o.
Čiližská 5
821 07 Bratislava, Slovakia
Email: hello@rausr.com
