Account

On the sign-in page, click "Forgot password". Enter the email on your account and we'll send a reset link that's valid for 30 minutes. The email comes from `accounts@floop.tech` — check spam if you don't see it. If your account was created via Google sign-in only, there's no password to reset; sign back in with the same Google account instead.

Yes. The sign-in screen has a "Continue with Google" button. If you already have an account with the same email as your Google address, the two are linked automatically — both methods work from then on. New accounts created via Google can add a password later under /account/security so they're not locked into one auth method.

Open /account/security → Two-factor auth, scan the QR code with any TOTP app (Google Authenticator, 1Password, Bitwarden, Authy, etc.), and enter the 6-digit code to confirm. Save the recovery codes we show you afterwards somewhere safe — they're the only way back into the account if you lose your authenticator. Once 2FA is on, every new browser session and CLI device authorisation will ask for a code.

Sign in with one of the recovery codes you saved when you enabled 2FA — at the code prompt, click "Use a recovery code instead". Each code works exactly once. Once you're back in, regenerate a fresh set under /account/security. If you've lost the device and don't have any recovery codes, contact support from the email address on the account; we'll verify your identity manually before unlocking the account, which usually takes 24–48 hours.

Open /account/profile, edit the email field, and click Save. We send a confirmation link to the new address — clicking it completes the change. The old address gets a notification (in case it wasn't you), and any pending sessions on the account are kept active. If your account uses Google sign-in tied to a Google address, change the Google email itself or unlink Google first under /account/security.

Open /account/danger-zone and click "Delete account". We send a confirmation email — clicking the link starts a 30-day grace window, during which your account is locked but recoverable. After 30 days everything is wiped: projects, GitHub repos we created, S3 assets, the project database, secrets, billing details on file, and audit logs. We notify you on day 7 and day 25 in case you change your mind.

Not directly through the dashboard, but support can do it. Email us with both account emails and tell us which one to keep as the primary. We move all projects, credits, custom domains, secrets, and team memberships from the secondary into the primary, then close the secondary. The whole process is usually done within 48 hours; we don't merge if either account has an active dispute or chargeback open.

Yes, but in separate browser profiles or windows. The dashboard stores its session in cookies scoped to the floop.tech domain, so a second account in the same profile would overwrite the first. The cleanest setup is one Chrome profile / Firefox container / Safari profile per account. The CLI handles this differently — `floop login --profile=work` lets you keep multiple credentials side by side and switch with `floop use work`.

It lets a project you build on FloopFloop talk to your Cryptohopper account through Cryptohopper's official OAuth2 REST API — list your hoppers, read trade history, place orders, and react to events. The integration is a one-click OAuth flow; no manual API key copy-pasting. Common use cases: a custom dashboard for your hoppers, automated reporting, signal generation hooked to your strategies, and notifications. The connection is per-user, so each project user authorises their own Cryptohopper account.

Open your project's Settings → Integrations and click "Connect Cryptohopper". You'll be redirected to Cryptohopper's login page; sign in if needed and approve the requested scopes. We get a refresh token (never your password), encrypt it, and store it as a per-user secret on the project. From then on, the project's code can call Cryptohopper's API on your behalf. The same flow works whether your project is hosted on a *.floop.tech subdomain or a custom domain.

Only the scopes your project actually uses. By default that's `read:hoppers`, `read:trades`, and `read:positions`. If your prompt asks for trade execution, the code will additionally request `write:orders`. The OAuth consent screen always shows you the exact list before you approve, and you can revoke it any time from Cryptohopper's authorised-apps page. We never request password-equivalent scopes, and we never store your Cryptohopper login.

Two equivalent options: (1) From the FloopFloop side — open Settings → Integrations on the project, find Cryptohopper, and click "Disconnect". We immediately delete the encrypted refresh token from the project. (2) From Cryptohopper's side — go to your Cryptohopper account's authorised-apps page and revoke FloopFloop. The next API call from the project will fail and the app will prompt the user to reconnect.

Only the OAuth refresh token is stored, never your password or your Cryptohopper API keys. The token sits in AWS Secrets Manager encrypted with AES-256, scoped to the user inside the project. At request time, your project's runtime exchanges the refresh token for a short-lived access token, makes the API call, and discards the access token. FloopFloop staff cannot read the plaintext token, and we never have access to your Cryptohopper account itself.

Free, Starter, and Pro are single-user accounts (you cannot invite teammates). The Business plan includes a workspace with up to 5 seats; if you need more, contact sales for an Agency tier with custom seat counts. Inviting a teammate is one click — open Workspace → Members, paste their email, choose a role, and they get an email with a sign-up link.

Owner: full control — billing, plan changes, workspace deletion, plus everything Admins can do. There is exactly one Owner per workspace; transfer the role from Workspace → Members → "Make Owner". Admin: manage members and projects, edit secrets, deploy, view usage; cannot change billing or delete the workspace. Member: build and refine projects assigned to them, deploy, manage their own secrets; cannot invite, remove, or change roles of other members.

Yes. As Owner, open the project's Settings → Workspace, pick the destination workspace from the dropdown, and confirm. The project's GitHub repo, deployment, secrets, custom domain, and credit-spend history all move atomically. The reverse also works — moving a project out of a workspace back to your personal account is the same one-click action. We never split a project across workspaces.

All your data lives in AWS, primarily in us-east-1 (N. Virginia). The platform database, project databases, S3 file uploads, and audit logs all sit there. CloudFront caches static assets at edge locations worldwide for speed, but the source-of-truth copy stays in us-east-1. We can move you to another region under contract if you have a hard data-residency requirement (EU mostly), but it's not yet self-serve.

Yes. Open /account/privacy and click "Export my data". We generate a ZIP within 72 hours containing your profile, billing history, list of projects, refinement chat history, audit log entries that reference you, and any uploaded files we still hold. We email a download link valid for 7 days. The export is GDPR Art. 20 compliant; you can also email privacy@floop.tech if you need it in a specific structured format.

Yes. Account deletion (see /account/danger-zone) covers GDPR Art. 17 — after the 30-day grace window everything personal is wiped. If you only want a specific item gone — a chat conversation, an uploaded file, an old support ticket — email privacy@floop.tech and we'll process it within 30 days. Some records (legally required tax invoices, fraud-investigation logs) we keep for the period the law requires, then delete. We'll always tell you what we kept and why.

Three channels, in order of speed: (1) the in-app support chat (bottom-right of every dashboard page) — fastest, AI-assisted with a human handoff for hard problems. (2) Email support@floop.tech — best for tickets that need attachments or back-and-forth. (3) For security issues specifically, email security@floop.tech — please don't open public GitHub issues. Response targets: Free 48 h, Starter 24 h, Pro 8 h, Business 2 h on business days.

Yes — status.floop.tech. It shows real-time uptime for the dashboard, the AI build pipeline, the deployment hosting layer, and each region of CloudFront. We post incident updates there during outages and a post-mortem within 5 business days for any user-impacting event over 30 minutes. You can subscribe by email or RSS to get notified. The status page is hosted independently of our main infrastructure so it stays up even when we're down.