How AIESEC Forms handles data

The short version

Answers people give in a form go straight to the destination the form's owner chose: their Google Sheet, their webhook, or their own database. AIESEC Forms does not store response answers or uploaded files.

What we keep

• For members who sign in: name, EXPA ID, email, profile photo, entity and position from EXPA, and when they last signed in.
• Form definitions: questions, settings, and who can edit each form.
• Destination settings. Passwords, keys and tokens are encrypted.
• How many responses a form received and whether deliveries are working, never the answers.
• An activity log of sign-ins and changes, with the browser name and a one-way hash of the IP address.

Signing in with AIESEC

We use AIESEC's sign-in. Your AIESEC access token is kept in an encrypted cookie in your browser so your session stays active; we don't store it on our servers. Signing out deletes that cookie.

Google access

When a form owner connects Google, AIESEC Forms asks only for permission to work with files it creates (the drive.file scope). It creates a response Sheet and an uploads folder, adds rows and receives uploads there, and cannot see anything else in the owner's Drive. Owners can disconnect at any time in Settings or in their Google account.

AIESEC Forms' use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Filling in a form

While you fill in a form, your answers are saved in your own browser so you don't lose them. They're cleared once your response is sent. The form's owner decides what happens to your answers after that; contact them with any questions.

Contact

AIESEC Forms is run by AIESEC in Lebanon. Questions about this policy go to the platform team of AIESEC in Lebanon.