Privacy Policy

Who runs this service

AutomateAutomate is a private automation workspace at automateautomate.com, oriented to members in Singapore. Schedules use Asia/Singapore. The operator’s legal name and postal address are not listed on this page. For privacy questions, contact the administrator who invited you. A public contact email is not listed yet.

The workspace is not Hollandse Club, not the Singapore Island Country Club (SICC), and not Snapchat.

What the workspace does

Signed-in members can store logins and ask the server to run jobs:

• Hollandse Club padel and tennis bookings.
• SICC tennis, pickleball, and golf bookings.
• SnapBot sends a scheduled Snapchat snap to shortcuts the member created in Snapchat.
• Slot waitlist watches a chosen date and time and can notify the member or attempt a booking when an opening appears.
• MCP account tools let an AI client act as that member: search availability, manage watches, schedule bookings, and read job or credential labels. The token cannot do more than the account is allowed to do.

There is no public signup. An administrator creates accounts and chooses services. A “Request access” page exists only as a coming-soon note. It has no form and stores nothing. There is no Stripe checkout and the site does not take payment card data.

Data the workspace holds

• Account username, a hash of the workspace password, whether the account is enabled, which services it may use, and whether a temporary password must be changed.
• Club and Snapchat credentials you save (a label, a login, and a password). Service passwords are encrypted at rest. They are decrypted when a job you asked for needs to sign in.
• Job settings: club, sport, date, time, court or tee preferences, player names, Snapchat shortcuts, captions, and an optional photo. With no photo, SnapBot sends a solid black frame.
• Slot waitlist settings: provider, activity, date, time window, notify or auto-book, and the result of checks.
• Run logs: status, timestamps, and a short result message. These describe what the job did. They are not a guarantee that a club booking or a snap was delivered.
• MCP tokens. The raw token is shown once. The database stores a hash and a short prefix so you can recognise and revoke it.
• A short-lived record of failed sign-in attempts, stored as hashes, so the login page can slow repeated guesses. Workspace passwords themselves are stored only as hashes.
• An administrator audit note when an account is created, changed, disabled, or when that administrator changes access.
• A session cookie that keeps you signed in.

Why it is held

The data is held to run the account you were given: sign you in, run the booking or snap you scheduled, show you the run log, and let an administrator manage access. It is not used for advertising, and it is not sold.

The service is aimed at members in Singapore. Personal data is used to run the account and the jobs described on this page.

Who else receives it

A job signs in to the service you named and submits what you asked for. That means Hollandse Club (through its booking site), SICC, or Snapchat may receive your login and the booking or snap payload. Their own privacy terms apply to what they do with that data after it arrives.

Other members cannot read your credentials, photos, or jobs. An administrator of this workspace can manage accounts and see audit notes. The administrator does not need your club or Snapchat password to grant or remove a service.

MCP clients you connect receive what the tool returns for your account. Credential tools return a label and login, not the stored password.

Cookies

The site uses one session cookie, named automateautomate, to keep you signed in for up to 12 hours. It is not an advertising cookie. On the public site it is sent only over HTTPS. The landing page, these legal pages, and the coming-soon request page do not ask you to create an account.

How long it is kept

Account, credential, job, and watch records stay while the account exists, including run history the member has not removed from view. Disabling an account stops sign-in and cancels queued work. After an account is closed, how long a remaining copy is kept is not stated as a number of days on this page. Ask the administrator who invited you if you need that copy deleted.

Failed-login hashes are kept only for the short rate-limit window. An MCP token stops working when you revoke it or when it is removed. The raw token is not stored.

Security

Workspace passwords and MCP tokens are stored as hashes. Club and Snapchat passwords are encrypted at rest. Jobs run on the operator’s server. No storage choice removes the risk of a club or Snapchat limiting an account that is used through automation. See the Disclaimers.

Your choices

You can change your workspace password, remove a saved service login when no waitlist entry depends on it, cancel a queued job, and revoke an MCP token. You cannot pull a booking or a snap back after the club or Snapchat has accepted the submission. To close an account, or to ask for a copy or correction of what this workspace holds, contact the administrator who invited you. A public privacy email is not listed yet.

Changes

If this policy changes, the date at the top will change. The version on this page is the current policy.