Privacy policy

Who we are

Shingle is run by SALMANDOTWEB LTD, a company registered in England and Wales (company number 16714338). Our registered office is 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom.

We're responsible, as the controller, for the personal information this policy describes about you, our customers. When your site collects information from its visitors, your business decides what happens to it and we handle it for you: see "Visitors to sites built with Shingle" below.

This policy covers shinglesites.com, the Shingle app and the emails we send.

What we collect

When you create an account

• Your name, email address and password. We store your password only as a scrambled hash (Argon2id) that can't be turned back into it.
• If you sign in with Google or GitHub: your name, email address and profile photo from that account, and an id that links it to Shingle. We never see your Google or GitHub password, and we don't keep the access they give us.
• Your settings: your photo link, time zone, theme, and whether we email you when a build finishes.

When you sign in

• For each session: when it started and was last used, the IP address it came from, and your browser's name and version. You can see these, and end any session, in Sign-in and security.
• If a sign-in fails: the email address typed and when, to stop people guessing passwords.

When you work in a team

• The team's name, its people and their roles, and its invitations, including the email addresses invited.
• Activity: a record of who did what in the team, such as publishing a site. It holds ids, roles and site names, never email addresses.
• Your teammates see your name, email address, photo and role.

When you build a site

• What you tell us about your business: your description, its name, location, phone, email address, booking link, opening hours and anything else you add.
• What we read for you, when you point us to it: your Google listing (its details, up to six public reviews with their authors' names, and up to eight customers' photos with their names) and the text of your website or the pages you name.
• Photos and logos you upload. We convert each one and remove its hidden details, such as the camera and where it was taken.
• Your sites' words, pictures, pages, versions and blog posts, and your forms' settings.

When you pay

• Your plan, its status and renewal date, any extra live sites, your credits and how they were used, and the ids Dodo Payments gives your customer record, subscription and payments.
• We never see or keep your card details or billing address: Dodo Payments collects those.

When you contact us or report a site

• What you write to us, and your email address.
• A report's reason, what you tell us, the page, and your email address if you give it. The site's owner never learns who reported it.

When you use Shingle

• Our servers log each request: what was asked for, the result, how long it took, and the ids of your account and team. They don't log your IP address or browser.
• To stop abuse, we count requests for a minute (an hour for reports) under a hashed form of your IP address, account or session, then delete the count.

How we use it

• To run Shingle for you: your account and teams; building, changing, previewing and publishing your sites; and your forms and visit statistics. We need this to give you the service you signed up for.
• To send the emails you need: confirming your address, resetting your password, invitations, form answers, a finished build (you can turn this off), and notices about your sites. We don't send marketing emails.
• To keep Shingle safe: preventing and looking into abuse, fraud and attacks, and reviewing reports. This is in our legitimate interests, and yours.
• To take payments and keep our accounts, with Dodo Payments, and to meet our legal duties.
• To help you when you contact us.

We don't sell your information, we don't show ads, and we don't use your information to build advertising profiles.

How we use AI

Shingle writes, designs and changes your sites with Claude, an AI model made by Anthropic. To do that, we send Anthropic what the work needs: your description and business details, what we read from your listing or website (including public reviews and their authors' names), your site's current words and pictures, and screenshots of its drafts. We don't send your password, or any id that identifies you or your account.

Anthropic's commercial terms don't allow it to train its models on what we send.

Images we create for your site come from image-generation models, such as Google's Gemini and OpenAI's GPT Image, which we reach through Treg. They receive a written description of the picture, with ids for your team and the request. For stock photos, we send Pexels only the search words.

What AI writes can be wrong, so our Terms of service ask you to check your site before you publish it.

Who we share it with

We share personal information with the companies that help us run Shingle, each for its own part of the work:

• Hetzner runs our server and database, in Helsinki, Finland.
• Cloudflare connects you to Shingle securely, serves previews and published sites, and stores images, site files and backups in Western Europe.
• Anthropic writes and designs sites with its AI.
• Treg looks up the public business listings and websites you point us to, through the services it works with (Serper, Litescrape, DataForSEO and crawl4ai), and creates images.
• Pexels finds stock photos from our search words.
• Resend sends our emails.
• Dodo Payments takes payments as our reseller and Merchant of Record. It decides how it uses the payment details it collects, under its own privacy policy.
• Google and GitHub, if you choose to sign in with them.

We also share information with your team, as described above; with everyone, once you publish a site; when the law requires it, or to protect people or Shingle; and with a buyer, if our business is sold, who must protect it as this policy does.

Where it's processed

Our server is in Finland, and our files are stored in Western Europe. Cloudflare serves sites from its network around the world, close to each visitor. Some of our providers, including Anthropic and Resend, process information in the United States.

When your information leaves the UK or the European Economic Area, we rely on the safeguards in our providers' data protection terms, such as standard contractual clauses and the UK's addendum to them.

How long we keep it

• Your account, until you delete it. Then we remove your email address, password, photo and sign-in links, and the IP addresses and browsers of your sessions, straight away. Your name stays in the history of the teams you were in.
• A team's sites and everything in them — versions, images, forms and their answers, visit statistics and reports — until the team deletes them. Deleting a site deletes everything in it, and deleting a team deletes everything in it, its Activity included.
• Form answers, until the business deletes them or its site.
• Images you no longer use, deleted within about two days.
• Emails: what's needed to send each one, for 24 hours after it's sent, or 7 days if sending fails.
• Backups of our database, for 30 days.
• Payment records: the ids of each payment event, for as long as we need them for our accounts and to settle disputes.
• Invitations, with the team's records until the team is deleted. Their links stop working after 7 days.
• Anything else, only as long as we need it for the reason we collected it.

Visitors to sites built with Shingle

When someone visits a site built with Shingle, the business that owns it decides what's collected and why, and we handle that information for the business.

• Form answers: what a visitor types into a form, and the page they sent it from, are kept for the business and emailed to the people it chose. We don't keep the visitor's IP address with them.
• Visit statistics: for each page view, and each click on a phone number, an email address or a link to another site, we record the page, the name of the site the visitor came from, their type of browser and device, and any campaign labels in the link. To count visitors without keeping their IP address, we combine it and their browser with a secret key into a code that changes every day. We use no cookies for this, and we don't count visitors whose browsers ask not to be tracked.
• The cookie banner: if a site's banner is on, visits are counted and its map is shown only once the visitor allows them.
• Maps: a map on a site is loaded from OpenStreetMap, which receives the visitor's IP address.
• Reports: every page on a Shingle address links to our report page.

Shingle adds a privacy page to each site, written from the business's details. If you visited a site and want to see, correct or delete what it holds about you, please ask the business. If you ask us, we'll pass your request on.

Cookies and storage

On shinglesites.com we use only the cookies Shingle needs to work, so we don't ask you to accept them:

• acme_session keeps you signed in. It lasts 30 days and renews while you use Shingle.
• acme_oauth_google and acme_oauth_github last 10 minutes, during a sign-in with Google or GitHub.
• acme_left lasts one minute, so the sign-in page can say why you were signed out.

Previews use one more, __Host-shingle-preview, on our preview addresses, to show your team its unpublished site. It lasts up to a minute and renews while you look.

Shingle also keeps a few conveniences in your browser's own storage: your theme, your recent picks in the command palette, the preview size you chose, how you last signed in (the method, never the address), and, for the tab you're in, a description you started on our home page and a few notes on your progress.

There are no advertising or analytics cookies, and no third-party trackers, on shinglesites.com.

Published sites set no cookies. If a site uses its cookie banner or age check, the visitor's choice is kept in their own browser: for a year for the banner, and up to 30 days for the age check.

How we protect it

• Every connection to Shingle and to published sites is encrypted.
• Passwords are stored as Argon2id hashes, and sign-in secrets only as hashes.
• Each team's information is kept apart in our database, so no team can reach another's.
• Card details never reach us.
• Our stored files and backups are encrypted by our storage provider.
• Only the people who run Shingle can reach its systems.

No system is perfectly secure. If something puts your information at risk, we'll tell you, and the regulator, as the law requires.

Your rights

Under UK and EU data protection law, you can ask us to:

• give you a copy of the personal information we hold about you;
• correct it;
• delete it;
• limit how we use it, or stop using it where we rely on our legitimate interests;
• give it to you, or to someone else, in a common format.

You can change most of your details in Shingle, and delete your account in Sign-in and security. For anything else, email [email protected] from your account's address. We'll reply within one month.

If you're unhappy with how we handle your information, please tell us. You can also complain to the UK's Information Commissioner's Office, at ico.org.uk, or to your local data protection authority.

Age

Shingle is for people aged 18 and over. We don't knowingly collect information about children. If you think a child has given us information, email us and we'll delete it.

Changes to this policy

We'll update this policy when what we collect, or how we use it, changes, and the date at the top of this page will change too. If a change matters, we'll email teams' owners before it applies.

Contact us

Email [email protected], or write to SALMANDOTWEB LTD, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom.