Skip to content
Docs

Move a site off the older saved data

On Thursday 17 December 2026 at 17:00 UTC, Simple Host turns off the older ways a site saves data: shared state, collections, and the data kinds Page info, Submissions, Personal and Shared board. After that, pages that use them can’t read or save that data. The pages stay online.

Move to SQLite, key-value or file storage with rules saying who can read and change what.

Your AI app can do these steps with Simple Host connected. Share this guide and name the site.

Before you start

What this is
  1. Download the site export from your Simple Host page. It keeps everything the site saved so far. It doesn’t hold other people’s Personal records. Each person keeps those in their own account export.
  2. Old data doesn’t move automatically. Copy only entries whose access the new storage preserves. Keep Personal records in each person’s private export, as explained below.

A form only you read (a private Submissions list)

What this is

For contact or lead forms: visitors add entries; only you read them.

  1. Make a SQLite database with these rules. Visitors may add. Only you may read, change or delete.

    {"kind":"sqlite","rules":{"version":1,"policies":[
      {"name":"add","command":"add","check":"true"},
      {"name":"owner","command":"all","using":"auth.role == \"owner\""}]}}

    If only signed-in visitors should send the form, write auth.signed_in in place of true.

  2. Make a table with one column for each field of the form, such as name and message.

  3. Change the page. Where it saved an entry to the Submissions list, it now adds a row to the table: SH.storage.sqlite("<database>").table("<table>").add({...}).

  4. Send one test entry from the page. Then ask your AI app to “show the entries”. The test entry should be there.

To read the entries later, ask your AI app to “show my new leads”.

One entry per person (Submissions with one entry each)

What this is

Here each signed-in visitor gives one answer and can change it later.

After the move, each person can add, read and change only their own entry. You can read all of them.

  1. Make a SQLite database with these rules:

    {"kind":"sqlite","rules":{"version":1,"policies":[
      {"name":"own","command":"all","using":"visitor_id == auth.id"},
      {"name":"add","command":"add","check":"auth.signed_in"},
      {"name":"owner","command":"all","using":"auth.role == \"owner\""}]}}
  2. Make an entries table with the answer’s columns. Simple Host adds visitor_id for authorship. Use owner SQL to enforce one entry per person:

    CREATE UNIQUE INDEX entries_one_per_person ON entries(visitor_id);
  3. List the person’s rows; edit the existing row or add one if absent. On row_conflict, fetch and edit the existing row. The unique index prevents duplicate submissions, including from two tabs.

  4. Visitors sign in on the site’s own address, as before.

  5. Submit twice as one person: only one row should remain. Sign in as another person in a private window: they must not see the first person’s answer.

Other older saved data

What this is
  • Page info: a key-value store that any visitor reads and only you change.
  • Shared state: key-value rules preserving signed-in visitors’ existing writes from the site’s own address and public reads. Owner-only writes break those pages.
  • A shared list or Shared board: a SQLite table. Choose rules for who may add, change and delete.
  • Personal: storage does not preserve Personal’s owner-exclusion guarantee. Owner tools bypass row rules (API keys, connector and site exports included). Removing the owner policy cannot prevent this. Keep each person’s private export until a suitable migration is agreed; do not copy Personal records into these tables.

More about rules is in the guide Storage and saved data.

Questions

What this is

Reply to the email we sent you, or write to support@simple-host.app.