Admin

Removing Gini

Take Gini out of a channel, out of the workspace, or out of your data entirely.

Three different asks, and people often want the second when they say the third.

Out of one channel

/remove @Gini in the channel, or remove it from the member list.

Access to that channel ends immediately: new messages and history both. Everything else keeps working.

Use this when a channel turned out to be a bad fit, or when a conversation is about to happen that shouldn't be in the room.

Out of the workspace

Slack → Manage apps → Gini → Remove app.

Gini loses access to every channel at once. Routines stop. Nothing can be asked of it.

Your data is still held on our side, so reinstalling later restores the wiki, skills and history. If you want it gone, that's the next section.

Out of your data entirely

Removing the app doesn't delete what Gini learnt. To delete that, email privacy@ginicomputer.com and ask for workspace deletion.

Deletion requests complete within 30 days. See Deleting your data for what's covered and what isn't.

Deletion is not reversible

The wiki, the skills your team wrote, the routine definitions and the run history all go. If you might come back, remove the app and leave the data. It costs you nothing and it's still there.

Cancelling a paid plan

Email team@ginicomputer.com. Cancelling stops the subscription; it doesn't delete anything and it doesn't remove the app.

You keep access for the rest of the paid period, then drop to Free limits: 10 channels, and whatever credits remain.

Disconnecting one tool

Not removal, but often the actual question. Go to app.ginicomputer.com → Integrations → Disconnect. Immediate, and it only affects your own connection.

Which one you want

What you wantDo this
It shouldn't be in that conversationRemove from the channel
Pausing while we evaluateRemove the app, keep the data
Stop the billEmail support to cancel
It shouldn't have our dataEmail privacy for deletion
It shouldn't reach my GmailDisconnect that integration

Before you go

If you're leaving because it didn't work, we'd genuinely like to know why, at team@ginicomputer.com. We read those, and the useful ones change what we build.