Terms & Privacy

What Codescape is. Codescape is a platform that event organizers use to run their events — publishing a programme, selling tickets, and collecting talk proposals through a call for speakers. Each event on Codescape belongs to its organizer. We provide the software; the organizer runs the event.

Your account. You need an account to submit a proposal or buy a ticket. Keep your password to yourself, give us an email address you actually read — organizers use it to reach you about your submission — and don't impersonate anyone.

Submitting a proposal. Submitting is not acceptance. The event's programme committee decides what goes on the schedule, on their own criteria and timeline, and neither they nor we owe you a reason. You keep ownership of what you write. By submitting, you give the organizer and Codescape permission to publish your talk title, description and speaker profile as part of the event's programme, and to keep them in the event's public archive afterwards.

What you submit must be yours. Don't submit material you have no right to publish, and don't submit anything unlawful. We can remove content and suspend accounts that breach this.

The organizer's own terms. Individual events may add their own terms — a speaker agreement, a code of conduct, travel conditions. Those sit alongside this page rather than replacing it, and the organizer is responsible for them.

Availability and liability. Codescape is provided as-is. We aim to keep it running but do not guarantee uninterrupted service, and we are not liable for indirect losses arising from its use. Nothing here limits liability that cannot lawfully be limited.

This describes what happens to your data when you use a call for speakers on Codescape. Codescape Limited is the data controller for your account; the event organizer is a controller for the submissions you send them.

What we collect

• Account — your name, email address and password (stored hashed, never in readable form).
• Speaker profile — tagline, biography, photo, and whichever of Facebook, X, LinkedIn, Instagram, blog and company website the organizer asks for. This profile is shared across every event you submit to.
• Each submission — talk title, description, format, level, private notes to the organizers, and any co-speaker email addresses you enter.
• If you buy a ticket — the buyer's name, email address and phone number, the name and email address on each ticket, and whatever the organizer asks for at checkout or at the door (a T-shirt size, a dietary need — the organizer chooses the questions, and they appear on the form). Card details go to Paystack and never reach us. We keep whether and when each ticket was checked in.
• Feedback — a rating, any words you leave about an event or a session, and the organizer's own questions if they ask any. It is anonymous unless you add your name, which is optional and kept as you typed it. Nothing links it to an account. So that you can change or remove an answer for ten minutes after sending it, and so that sending twice does not count twice, your browser keeps a random id in a cookie (cs-feedback, a year) and it is stored hashed with the answer; without the cookie a hash of your address and browser for the day stands in. Neither identifies you, and neither is shown to anyone. The organizer sees what you wrote; a speaker may see what was said about their own session; anything shown on a live screen at the event is only what you wrote.

Attendee data

Ticket and check-in details are used to run the event you bought a ticket for: issuing the ticket, sending you updates about that event, checking you in at the door, and the organizer's own headcount and reports. They are visible to the organizers of that event and to nobody else — an organizer never sees the attendees of an event that is not theirs.

Analytics

We run no analytics of our own — no tracking pixels, no usage recording — on the dashboard, the events site or the apps. The one exception is Google Analytics on a call for speakers, and only when the organizer of that event has turned it on for their call: it then loads on that call's pages and receives Google's standard, pseudonymous usage data, under Google's own terms. It is never on by default.

What is public, and what is not

This distinction is shown on the submission form itself, field by field.

• Published if your talk is accepted: talk title and description, and your name, tagline, biography and photo. These appear on the event's public schedule and speaker pages, and through the public API that powers the event's website and apps.
• Never published: your email address, your notes to the organizers, and the co-speaker addresses you enter. These are visible to the organizers of the event you submitted to.

Who else sees it

• The organizer of the event you submit to — everything above, so they can review and schedule your talk and contact you.
• Anyone you add as a co-speaker is emailed to tell them you added them to a session.
• Google Analytics, only on calls whose organizer has turned it on for their own event — see Analytics above.
• Our email provider, to deliver notifications about your submission.
• Paystack, if you buy a ticket. Card details go to Paystack directly and never reach us.

We do not sell your data, and we do not share it with organizers of events you have not submitted to.

How long we keep it

Your account and speaker profile are kept for as long as the account exists. Submissions are kept by the event they belong to, including after the event, so the programme archive stays intact.

You can delete your account yourself, at any time, from Your data in the account menu. Because a past event's programme is a historical record, you choose what happens to sessions you have already given:

• Keep my talks. Your login, email, photo, biography and links are erased. The sessions stay in their programmes with your name on them — and we keep that name only because you ask us to, on a tick box whose exact wording we store alongside it. You can come back and have the name removed.
• Remove my profile too. The sessions stay in the archive, attributed to a removed speaker. No name, no profile page, no link.
• Delete everything, including the sessions you submitted, from past programmes as well. Talks you only co-authored stay, because they are somebody else's submission — you are detached from them instead.

Deletion is immediate and cannot be undone, so the same page offers a copy of everything we hold about you first, as a JSON file.

One thing we ask you to do first: if you run an organization here, hand it over or close it before deleting your account. Its events, tickets and payments belong to other people too, and should not be left without an owner.

Under Kenya's Data Protection Act 2019 you can ask us to show you the personal data we hold about you, correct it if it is wrong, delete it, or stop a particular use of it. You can also complain to the Office of the Data Protection Commissioner.

Most of your data you can change yourself from your speaker profile, and both access and erasure are self-serve from Your data in the account menu — no need to ask us. For anything else, email us and we will handle it.

Contact: [email protected]