Dieses Dokument ist auf Englisch. Maßgeblich ist die englische Fassung.
Rune
Privacy Policy
Last updated 13 November 2026
This Privacy Policy explains how Rune collects, uses, shares and protects Personal Data when you visit our website, request a free preview, use Rune as a customer, connect a website to Rune, or read a blog that Rune hosts or publishes for a customer. Please read it together with our Terms of Service.
1. Who we are and what this policy covers
Rune is an editorial desk for brands: it writes illustrated blog articles in a business’s voice and publishes them to that business’s website. Rune is provided by Overview, 1985 Del Amo Blvd, R7653, Torrance, CA 90501, USA (“Overview”).
In this policy:
- “Rune”, “we”, “us” and “our” mean Overview, as the provider of Rune.
- “Service” means rune.press and its subdomains, Previews, the Rune publishing service, the blogs and content feeds we host or publish for Customers, Rune’s plugin for WordPress, Rune’s app for Shopify, and related emails and support.
- “Customer” means a business with a Rune account. Its “owners” are the people who may sign in to the account and approve articles.
- “Customer Content” means material a Customer gives us or that we produce for it, such as briefs, brand materials, website content, product information, articles, images and notes.
- “Preview” means the sample articles Rune writes for a business before it becomes a Customer.
- “Personal Data” means information relating to an identified or identifiable individual.
Third-party services that the Service links to or connects with, such as Google, WordPress, Shopify, Webflow or a call-scheduling tool, are covered by their own privacy policies. For any question about this policy, contact hello@rune.press.
2. Our role: controller and processor
We are the controller (or “business”, under US state laws) for our website, Previews, sign-in and accounts, our communications with you, and running and securing the Service.
When we host or publish a blog for a Customer, we process Personal Data about its readers (such as request data and questions readers submit on articles), and Personal Data about other people in its Customer Content, on the Customer’s behalf and under our agreement with it. Here the Customer is the controller (or “business”) and we are its processor (or “service provider”).
If you read a blog that a Customer publishes with Rune, please see that Customer’s own privacy policy and send requests about your Personal Data to it. If you contact us instead, we will pass your request on and help the Customer respond.
3. Personal Data we collect
3.1 Website visitors
When you visit our website, including our sign-up pages and Previews, we collect:
- Technical data: your IP address, browser type, the pages you request, when, and similar request metadata. Our cloud hosting and content delivery provider processes it to deliver pages and protect the Service against abuse.
- Usage data: the pages you view, the links and buttons you click, and an identifier stored in your browser, through our product analytics and advertising measurement providers (see Section 6).
3.2 People who request a free Preview
Previews are public. Anyone who has the link to a Preview can open and read it, without signing in. Its address is hard to guess and we ask search engines not to index it, but that does not make it private: a link can be forwarded, and anyone who receives it can see the Preview. Please do not put anything in your brief that you would not want others to read.
To request a Preview, you sign in with Google (see Section 4) and give us your business’s website address and a short brief about who you write for and what the blog should do. We read the website’s public pages (such as its text, logo and product information), create a brand profile (voice, description, logo and image style) and write two illustrated articles. We keep the Preview’s status, brand profile, articles, timestamps, and whether you clicked to book a call. Requesting a Preview also opens an account for it, with its own review page where you can ask for changes to its articles; we keep your note and use it to rewrite them (Section 5.1). If the website contains Personal Data, such as names of staff, we use it only to create your Preview and, if your business becomes a Customer, to provide the Service.
If you book a call from a Preview, a third-party scheduling tool opens with your name, email address and the Preview’s link filled in, and we record the click.
3.3 Prospective customers whose Preview our team prepares
Our team may prepare a Preview for a business before anyone from it has signed up. For this we use the public content of the business’s website and a business email address for the person we are preparing it for, which we obtained through our dealings with that person or their business, or from a publicly available business source. We create a placeholder account under that address, review the Preview internally, and email you only when we send it to you. Like every Preview, it is public to anyone who has its link, including before we send it to you.
We rely on our legitimate interest in introducing Rune to businesses that may benefit from it. You can object at any time, or ask us to delete the Preview and placeholder account, by writing to hello@rune.press. When such a Preview is withdrawn, its placeholder account is deleted.
3.4 Customers and their owners
If your business is a Customer, or you are one of its owners, we collect:
- Account data: the business’s name, its owners’ email addresses, the name and Google account identifier of each owner who signs in, and billing status.
- Review records: when an owner approves an article, requests changes or rejects it, we record the article’s title and address, the decision, which owner made it, when, any note, and the live address once published.
- Customer Content, and connection data for the websites and platforms a Customer connects (see Section 13).
- Billing data: where a third-party payment processor handles payment, it collects payment details under its own terms, and we receive only what we need to manage the account, such as payment status.
We email owners when a draft needs review and about the account. Our emails never contain a link that approves an article in one click.
3.5 Readers of Customers’ blogs
On blogs Rune hosts for Customers, our cloud hosting and content delivery provider processes technical request data, such as IP address and browser type, to deliver and protect the blog. We run no analytics on Customers’ blogs.
On a published article, a reader can type a question and receive an AI-generated answer in the publication’s voice, without signing in. We store the question and answer, and may give the stored answer to other readers who ask the same question. Please do not include Personal Data, about yourself or anyone else, in a question. We process readers’ data on behalf of the Customer (see Section 2).
3.6 Anyone who contacts us
If you write to us, we keep your email address, your message and our reply.
4. Sign in with Google
Rune has no passwords of its own; you sign in with Google to request a Preview or use a Customer account.
- What we access. Only the basic sign-in scopes (“openid”, “email” and “profile”): your Google account identifier, name and email address. We have no access to Gmail, Google Drive, contacts, calendar or any other Google data, and never receive your Google password. We accept only email addresses Google has verified.
- What we store. Your Google account identifier, verified email address and name, and when you first and last signed in.
- How we use it. To sign you in and identify you, keep the Service secure and meet legal obligations. Beyond that, if you request a Preview, we use your Google name and email address only to send you your Preview and to help you book a call if you want one. If you are an owner of a Customer account, we also use your email address for review requests and account messages.
- Sharing. We do not sell Google user data or use it for advertising. We share it only with service providers that need it to run the Service (see Section 7), or where the law requires. We do not send your name or email address to our analytics provider.
- Deletion. You can ask us to delete the data we received from Google by writing to hello@rune.press, and you can remove Rune’s access in your Google Account settings.
Rune’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. How we use Personal Data and our legal bases
We use Personal Data for the purposes below. For people in the European Economic Area (EEA) and the United Kingdom, we show the legal basis for each.
- To provide the Service: sign-in, Previews, writing and illustrating articles, owner approval, publishing, hosting blogs and feeds, and answering reader questions. Basis: performance of a contract with you, or steps you ask us to take before one (such as requesting a Preview); for owners acting for a Customer, our legitimate interest in serving that Customer.
- To communicate with you: Preview-ready emails, review requests, account notices and replies to your messages. Basis: contract; legitimate interests.
- To prepare Previews for prospective customers (Section 3.3). Basis: legitimate interests.
- To understand and improve the Service: measuring how our website, sign-up and Previews are used, and fixing problems. Basis: legitimate interests.
- To keep the Service secure: preventing abuse of Previews and reader questions, protecting accounts and credentials, and investigating incidents. Basis: legitimate interests.
- To comply with the law and protect our rights: keeping required records, responding to lawful requests, enforcing our Terms of Service, handling legal claims, and in connection with a business transaction (Section 7). Basis: legal obligation; legitimate interests.
Where we rely on legitimate interests, we have balanced them against your rights, and you can object (Section 11). Where we rely on consent, you can withdraw it at any time.
5.1 AI processing
Rune uses third-party AI model providers to analyse public website content, write and revise articles, generate and edit images, and answer reader questions. For each task we send the provider the content it needs (for example website text, a brief, an owner’s note or a reader’s question) and it returns the result. We use these providers’ business services, and our agreements with them govern how they handle that data. Rune does not itself train AI models on Customer Content or Personal Data.
AI-generated content can be inaccurate. Articles are drafts until a Customer publishes them; if one contains inaccurate information about you, contact the Customer or us. We do not use Personal Data for decisions based solely on automated processing that produce legal or similarly significant effects for you.
6. Cookies and similar technologies
- Strictly necessary. When you sign in, we set a session cookie (
__Host-rune_session). It is sent only over secure connections, cannot be read by scripts on the page, and expires after 30 days or when you sign out. We store only a hash of the session token. Sign-in cannot work without it. - Analytics. Our product analytics provider stores an identifier in a first-party cookie and your browser’s local storage, and records page views and clicks; our servers also record key steps such as signing in, requesting a Preview and booking a call. We identify you to analytics only by an internal Rune user ID and the domain of your Preview’s website, never by name or email address. Analytics requests are routed through rune.press, the data is hosted in the EU, and the analytics identity resets when you sign out.
- Advertising measurement. If you arrive from one of our ads, our advertising provider’s cookies help us measure whether the visit led to a Preview request or a purchase. We do not use them to personalise ads.
- Third-party content. Some content, such as web fonts, loads from providers’ servers, which receive your IP address and browser information.
Analytics run only on Rune’s own pages: our website, sign-up pages and Previews. We never place analytics on the blogs we host or publish for Customers.
Your choices. You can block or delete cookies and local storage in your browser settings, or use a browser extension that blocks analytics. Blocking the session cookie prevents sign-in, but blocking analytics does not affect the Service.
7. How we share Personal Data
Service providers. We use service providers to run the Service and share with each only what it needs to perform its services for us. Their categories are:
- cloud hosting, content delivery, databases and file storage;
- content management system hosting;
- AI model providers, for text and images;
- email delivery;
- product analytics, hosted in the EU;
- advertising measurement;
- authentication (Google, for Sign in with Google);
- scheduling, for booking calls;
- payment processing, where paid billing applies;
- source-code hosting and build automation, which run our publishing jobs;
- secrets management, which stores publishing credentials.
Within a Customer’s account. A Customer’s owners can see the account’s articles and review records, including which owner approved, requested changes to or rejected an article, when, and any note.
Connected platforms and the public. At a Customer’s instruction, we send articles, images and related data to its website or platform, such as WordPress, Shopify or Webflow. Published articles and content feeds are public, and Previews are public to anyone with their link. Drafts awaiting an owner’s review can also be opened by anyone with their link on the publication’s Rune address, though we ask search engines not to index them.
Other disclosures. We may share Personal Data with professional advisers bound by confidentiality; with parties to a merger, acquisition, financing or sale of all or part of our business, subject to confidentiality, provided any successor protects it in line with this policy; where we believe in good faith that the law, legal process or a valid request from a public authority requires it, or that it is needed to protect the rights, property or safety of Rune, our Customers or others; and when you ask us to.
We do not sell Personal Data, and we do not share it for cross-context behavioural advertising or use it for targeted advertising.
8. International transfers
We are based in the United States, and our team and service providers may process Personal Data in other countries, including Israel and EU member states. For transfers from the EEA or the United Kingdom, we rely on an adequacy decision where one applies (the European Commission and the United Kingdom recognise Israel as providing adequate protection, for example), or on a recognised safeguard, such as the European Commission’s standard contractual clauses (with the UK International Data Transfer Addendum where applicable) or, where the recipient participates in it, the EU–US Data Privacy Framework and its UK extension. Contact us to learn more about these safeguards.
9. How long we keep Personal Data
- Sessions expire after 30 days; signing out ends your session immediately.
- Previews are kept while they exist. We may remove a Preview at any time, after which its link no longer works, and you can ask us to remove yours. When a Preview our team prepared is withdrawn, its placeholder account is deleted.
- WordPress connections: unused connection codes are deleted about a day after they expire. A connection is deleted when an administrator disconnects it or deletes the plugin (Section 13); otherwise we keep it until it is replaced or the Customer asks us to remove it.
- Shopify connections are deleted when the store uninstalls Rune’s app, or when Shopify asks us to erase the store’s data; otherwise we keep a connection until it is replaced or the Customer asks us to remove it.
- Accounts and Customer Content are kept while the account is active.
Otherwise we keep Personal Data only as long as needed for the purposes in this policy, including meeting legal, tax and accounting obligations, resolving disputes and enforcing our agreements, and then delete or anonymise it. Copies may remain in our providers’ backups for a limited period. You can ask us to delete your Personal Data sooner (Section 11).
10. Security
We use technical and organisational measures designed to protect Personal Data, appropriate to the risks. For example, data travels over encrypted (HTTPS) connections; we store only hashes of session tokens; WordPress publishing credentials and Shopify access tokens are encrypted so that only our publishing system can open them, and other platform credentials are kept in a dedicated secrets management service; and approving an article always requires signing in. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If a security incident affects your Personal Data, we will notify you and the relevant authorities where the law requires.
11. Your rights
Depending on where you live, you may have these rights:
- EEA and United Kingdom: to access, correct or delete your Personal Data, restrict or object to its processing (including processing based on legitimate interests), receive it in a portable format, and withdraw consent. You may also complain to the supervisory authority where you live or work or where an alleged infringement took place.
- Israel: under the Protection of Privacy Law, 5741-1981, to inspect Personal Data about you held in a database and ask us to correct or delete it if it is inaccurate, incomplete, unclear or out of date. You may also complain to the Privacy Protection Authority.
- United States: residents of certain states, such as California, may have rights to know what Personal Data we collect, use and disclose (see Sections 3, 5 and 7), to access, correct and delete it, to opt out of its sale, sharing or use for targeted advertising (we do none of these), to use an authorised agent and to appeal our decision. We will not discriminate against you for exercising your rights.
To exercise a right, write to hello@rune.press. We may need to verify your identity first, and will respond within the time the law requires. If we process your Personal Data for a Customer (Section 2), we will pass your request to that Customer.
12. Children
Rune is a service for businesses, intended only for people aged 18 or older acting for a business. We do not knowingly collect Personal Data from anyone under 18. If you believe a child has given us Personal Data, contact us and we will delete it.
13. Connected websites and the Rune plugin for WordPress
Rune’s plugin for WordPress (listed on WordPress.org as Rune Publishing) is free software licensed under the GPL (version 2 or later), distributed through WordPress.org and rune.press. It works only with a Rune account and a publication our team has set up.
- Before connecting. The plugin sends nothing to Rune about your site or its content until a site administrator clicks Connect to Rune. The only exception is the update check in copies downloaded directly from rune.press (see Updates below).
- Connecting. When an administrator clicks Connect to Rune, your browser opens rune.press with your site’s address, its WordPress return address and a temporary state value, and an owner of the Rune account signs in with Google and confirms. The plugin then sends Rune, over HTTPS, a one-time connection code, your site’s address, the plugin version, and the username and a newly generated WordPress Application Password of a dedicated, restricted “Rune publisher” user.
- Checking the connection. Rune reads the plugin’s authenticated status endpoint, which returns the plugin version, the site and article-section addresses, the permalink format, the active SEO plugin, the byline, and the publishing user’s ID and slug.
- What the Rune publisher user can do. Write and publish only Rune’s own article type and upload images. It cannot touch your regular posts, pages or products, change themes, plugins or settings, or manage any user account, its own included: it cannot change its profile or create further passwords.
- What Rune stores. Your site’s address, the publishing username, the Application Password in encrypted form (sealed with a public key; only our publishing system holds the private key), the plugin version, connection timestamps, the email address of the owner who connected the site, and a hash of a disconnect token. Our team is emailed when a site connects or disconnects, with the publication, the site’s address and, on connection, the owner’s email address.
- While connected. Rune uses the WordPress REST API to read and publish its own articles, their SEO fields and images. The plugin collects no analytics about your visitors and does not send Rune your other posts or content.
- Disconnecting and deleting. Disconnecting, or deleting the plugin, first revokes every Application Password of the Rune publisher user on your site, then asks Rune to delete the stored connection. If Rune cannot be reached, its access is still revoked; write to hello@rune.press and we will delete the stored record. Your articles stay on your site, and if you delete the plugin they become regular WordPress posts. Disconnecting does not delete your Rune account or the articles held in Rune.
- Updates. Copies from WordPress.org update through WordPress.org. A copy downloaded directly from rune.press checks rune.press for updates while it is active, whether or not it is connected; these requests include your server’s IP address and standard WordPress HTTP headers, which may include your WordPress version and site address. A successful check is reused for 12 hours.
Other connections. Rune can also host a Customer’s blog, at a rune.press address or under the Customer’s own domain through its reverse proxy (see Section 3.5), or publish to other platforms:
- Shopify. A store connects by installing Rune’s app, from a private install link our team sends, and opening it in its Shopify admin. Shopify then gives Rune an access token for the store, limited to reading and writing its blog articles and uploading files. Rune keeps the store’s myshopify address and name, the access granted, the token in encrypted form (sealed with a public key; only our publishing system holds the private key), the Shopify ID of the staff member who opened the app, and connection timestamps. Rune uses the token only to read the store’s blog and to create and update the articles it wrote, with their images and SEO fields; it reads no customer or order data, and the app adds nothing to your storefront. Our team is emailed when a store connects or uninstalls the app. Uninstalling the app revokes the token and deletes the stored connection; articles already published stay in your store.
- Webflow. The Customer gives us a Webflow API token, which we keep in our secrets management service and use only to create and update the Customer’s articles and images in its Webflow site. The Customer can revoke it in Webflow at any time.
- Headless content feed. The Customer’s own website reads its articles from a public feed on rune.press that needs no key and that anyone can read. It contains only published articles, except that a ready Preview’s articles can be read through it by the Preview’s identifier, and are public to anyone who has it.
14. Changes to this policy
We may update this policy, for example when we change the Service or the law changes. We will post the updated policy here with its effective date and, for material changes, also tell Customers and other affected people by email or through the Service where appropriate.
This policy is effective from 13 November 2026.
15. Contact us
For questions, requests or complaints about this policy or your Personal Data, write to hello@rune.press, or to Overview at the address in Section 1.