What Access checks and records

Before you install or grant permissions

Browsing this website or using its download recommendation does not turn on your camera or microphone. The desktop app requests permissions separately during setup and participation.

For a round that requires a permission, refusing or removing it can prevent entry or interrupt participation. Ask your organizer about alternatives before assessment day.

What is checked, and where information goes

Camera and presence

Purpose

Test the camera, complete calibration and check face presence during a session.

Information handling

Calibration captures stay on the device in the reviewed flow. Separate presence-check stills can be sent with session events. Presence detection does not, by itself, verify identity.

Microphone

Purpose

Check microphone access and open the media stream used by the session.

Information handling

The reviewed flow requests access but does not include continuous audio recording or upload. Read your round’s notice for any additional service or arrangement.

Device and connection

Purpose

Check whether the computer and its environment meet the round’s requirements.

Information handling

Operating system, app version, a device identifier and the results of permission, display, running-application and connection checks can be included in readiness reports sent before entry.

Session activity

Purpose

Record events that help explain what happened during the assessment.

Information handling

Focus changes, connection and camera status, presence results and other assessment-control events are queued locally and sent with timestamps. Failed delivery may leave records pending on the device.

Answers and submissions

Purpose

Save work, evaluate submitted code and show results and attempt history.

Information handling

Editor drafts are saved on your device for recovery. Code and any custom test input are sent to assessment services when you use Run or Submit; results and attempt history come from those services. A local save is different from a successful scored submission.

Incident reports

Purpose

Help investigate a problem reported during a round.

Information handling

A report can contain your description, session identifiers and time, device/display details, camera or presence status, and restricted-application findings. Check for a delivery confirmation; if sending is unconfirmed, use your organizer’s support channel.

Camera images and microphone access are different

Camera checks support device setup and face presence during a session. Local calibration images are separate from session images: when a presence check finds no face or more than one face, a still image can be included in the activity sent to the assessment service.

The app requests microphone access during setup and when opening the live session media stream. Permission to use a microphone is not, by itself, evidence that audio is recorded or stored. The reviewed 2.3.1 flow does not include continuous audio or video recording.

Calibration images are stored temporarily on the device. The app attempts to remove them when the secured session ends and at its next startup; a crash or file-access problem can delay removal. This cleanup does not delete separate session images or records already sent to the service.

What can change during a secured session

Depending on the operating system and round, Access can keep the assessment window in focus, check running applications, limit keyboard actions and restrict network access. These are session controls, separate from the information recorded about the round.

Use the app’s exit process so it can restore device settings. Some restrictions can remain after an interruption or crash until restoration completes. Contact your organizer or support if your device does not return to its normal state.

What checks and activity mean for your result

• Code judging can produce automated evaluation results.
• Required readiness and entry checks can prevent participation when they are not met.
• Session activity provides context for review. An activity flag alone is not proof of misconduct.
• Your organizer should explain how results are decided, how technical issues are considered and how to request a review.

Who can see records, and how long are they kept?

Assessment services receive submitted work, readiness information and session activity. Authorized organizer, administration or support workflows can use these records. The exact people, permissions and media access for your round need confirmation from its organizer and AMS.

AMS has not yet confirmed a universal retention period, a complete hosting/provider list or a finalized policy for these pages. Do not assume records are deleted when the app closes, when you sign out, or when you uninstall it.

Some setup checks can contact a Google connectivity service as well as assessment services. The endpoint operator can receive ordinary request information, such as IP address, time and user agent.

Local calibration cleanup is separate from queued event records and server-held assessment data. Pending events can remain on the device after a connection problem. Avoid clearing app data during a live round without support guidance.

Read the notice for your version and your round

Access 2.3.1 includes a desktop privacy policy dated 27 May 2026. Find it in Settings → About → Privacy, or through the privacy link before setup. Read it alongside your organizer’s notice; the website notice supplements this information and does not replace either.

Before the round, confirm which checks apply, whether session images are available to reviewers, who can access records, how long they are kept, and how to ask for a correction or review.

For invitation, participation or result questions, start with your organizer. For privacy questions about Access or uncertainty about where to ask, email team@amshq.in. Keep passwords, invitation codes and assessment answers out of an initial message.