Frequently asked questions

An Android app for recording and managing employee attendance: face-recognition punching, shifts, work calendars and holidays, working-hour rules, and attendance reports.

Any organization that records attendance: shops, offices, factories, schools, agencies and small businesses.

No. It is made for owners, managers and HR staff. Setup happens in the app, with no server or special hardware.

No. Elixir Attendance runs on one shared Android phone or tablet at your workplace, used as an attendance kiosk. Employees do not install anything. Using several kiosks for one organization is planned.

Your plan sets the limit, from 10 employees on Basic to 250 on Professional. For more, contact us.

Not yet. Attendance is managed in the app on the kiosk phone. With a plan that includes cloud sync, a copy of employees, shifts and punches is also kept in your organization's cloud backup.

Install the app, register with your email address, verify it from the email we send, and enter your organization's details. Two defaults are created for you: a Default Calendar and a General department.

A 30-day free trial with every feature, for up to 10 employees, is planned for every new organization. During early access the app is free to use.

When your organization is created. The end date is set by our server, so changing the phone's date does not extend it.

No. The planned trial needs no payment details, and during early access nothing is charged.

Nothing is deleted and attendance keeps working. To keep adding employees, shifts and calendars, and to keep cloud features, choose a plan.

Yes. An upgrade applies at once; a downgrade applies at the end of the period you have paid for. No employee or attendance record is deleted because of a plan change.

Go to Employees › Add employee, enter the employee code, name and mobile number, then register their face by following the on-screen steps.

Yes. The administrator can edit an employee's details, re-register their face, or deactivate them. Their past attendance stays in your reports.

A code your organization chooses to identify each employee, such as P01. It must be unique within your organization.

No. Employees punch at the kiosk with their face. Only the administrator signs in, plus an optional attendance-only user who can open the punch screen and nothing else.

The app refuses to add more employees and shows your options: upgrade, or deactivate someone who has left.

An employee stands in front of the kiosk, is recognised by face, and the punch is saved on the phone immediately. The app turns punches into worked hours using the employee's shift.

Three: two buttons (Punch in and Punch out, the default for new organizations), one button that works out in or out by itself, and touchless, where recognition alone records the punch. Change it in Settings.

Yes. Choose one of the button modes in Settings; a punch then needs a tap after the face is recognised.

Punches happen at the kiosk phone. You can also restrict punching to your workplace: in Settings › Workplace & GPS, punches outside the radius you set are refused.

It records either a site name you choose, such as “Head office”, or, on plans that include GPS punch, the phone's GPS position. The app never tracks location in the background.

The phone's date, time and time zone. Keep automatic date and time switched on for the kiosk phone.

Punch times will be wrong too, so keep automatic time on. If the clock is moved, the app notices and asks to verify your plan online before plan features work again; attendance keeps working.

You set a repeat-punch delay in Settings, so an accidental second scan is not recorded twice.

When adding or editing the employee, tap the face area and follow the prompts. The app captures a few views of the face on the phone.

No. Register once. Re-register if recognition becomes unreliable, for example after a big change in appearance.

Usually, if the face is well lit and clearly visible. If recognition struggles, register the face again wearing the glasses the employee normally wears.

Check that your whole face is inside the guide, the light is good and not behind you, the camera lens is clean, and you are following the on-screen prompt.

Common reasons: the repeat-punch delay has not passed, the punch was outside the workplace radius, the photo-protection check did not pass, or, in two-button mode, no button was tapped.

An on-device check that tries to tell a live face from a copy. The default check stops a face shown on a phone or monitor screen; a printed photo can pass it. The Head turn option asks the employee to turn their head, and is the check measured to refuse a printed photo. Choose it in Settings › Photo protection.

A face must also match a registered employee to be recorded. With the default check a printed photo can pass; the Head turn option is the one measured to refuse it. No face-recognition system is perfect, so administrators can review and correct attendance.

No. Face templates and enrolment photos are never sent to our cloud, and the cloud backup never holds face data. They leave the phone only in an encrypted backup file that an administrator chooses to export.

Yes, from each day's punches and the employee's shift: gross and net hours, late arrival, early going, half days, overtime and incomplete days.

Yes. A shift sets working hours, grace time for late arrival, and when a day counts as a half or full day. Employees without a shift use default hours.

Yes. A shift can include a break allowance, and break tracking can add break start and end buttons to the punch screen.

The break allowance comes out of time worked beyond the required hours, so a full working day still counts as a full day.

Yes. Reports show late arrivals, early going and overtime. Overtime follows the rules set on the shift, including a minimum before it counts.

The day is shown as incomplete, with the reason, and is left out of hour totals until it is corrected. The administrator can add the missing punch.

Yes, for past days. Corrections keep the original punch and record who changed what and why. You can lock a period, such as a payroll month, so it can no longer change.

Yes. Each work calendar has its weekly offs and holidays, and shows them on a calendar view.

Yes. A holiday can be a full day, or the first or second half of the day.

Yes. Create several work calendars and assign each employee to one. Your plan sets how many calendars you can have.

Yes. A new weekly pattern can start from a date you choose, so earlier attendance is not recalculated.

Yes. Choose a report (daily attendance, employee summary, late coming, early going, absent, half day, overtime, work hours, missing punch or multiple punches) and filter it by dates, employee or department.

• Employee name and code
• Date, punch in and punch out, and every punch
• Gross and net hours
• Late arrival, early going, half days and overtime
• Incomplete days and the reason
• Location, where recorded

Yes: as CSV, as an Excel file, or printed or saved as PDF, and shared from the phone.

It is a good starting point. Check the figures against your own payroll rules and applicable law before paying.

Not for attendance. Face recognition, punching and reports all run on the phone. Plan features such as adding employees need an online check at least once every 7 days.

Punches are saved on the phone first. With cloud sync, they are uploaded when the phone is back online.

Anything that exists only on the phone is lost with it. Cloud sync, on plans that include it, keeps a copy of employees, shifts and punches that you can restore to a new phone; faces must be registered again. A backup file you exported from Settings, Backup & restore, brings back faces too. Keep cloud sync on, or export a backup regularly, if this matters to you.

Yes, on every paid plan, without internet. Settings, Backup & restore exports two files: employees with their faces, shifts, calendars and departments, and attendance with the employees it belongs to. Files are encrypted and can be imported only by the same organization. Importing adds what is missing and never creates duplicates or changes what is already on the phone. The free trial does not include it.

Cloud employee backup is on every plan. Cloud punch sync and restoring attendance start with quarterly billing. See Pricing.

Five plans, Basic, Starter, Growth, Business and Professional, differing by employees, calendars, shifts, history kept on the phone and cloud features. Elixir Attendance is free to use during early access. The proposed plans show what each paid plan would include once they launch.

Monthly, quarterly, half-yearly and yearly. Longer periods cost less per month, and cloud features start with quarterly billing.

No. There is a free trial for new organizations, then a paid plan.

Once paid plans launch, subscriptions will be bought through Google Play, inside the app. Nothing can be bought during early access.

No. Google Play shows the price in your local currency, including local taxes; in India, in rupees (₹).

The website shows list prices. Google Play's price is the one you pay, and can differ because of currency, tax or regional pricing.

In the Google Play Store app: profile › Payments & subscriptions › Subscriptions › Elixir Attendance. You keep your plan until the end of the period you paid for, and no data is deleted.

Refund requests are handled under Google Play's refund policy and our Terms. Cancelling stops the next renewal; it does not refund the current period by itself.

Google Play retries. Your plan keeps working for a short grace period while you update the payment method in Google Play; after that it pauses until payment succeeds. Attendance keeps working throughout.

Make sure the phone is signed in to the Google account that bought it, then open Settings › Subscription & plans › Restore purchases. If it still does not appear, email elixirinfotechindia@gmail.com.

A subscription belongs to the organization it was bought for. After reinstalling or moving to a new phone, sign in and tap Restore purchases. It cannot be moved to a different organization.

Yes, in Settings, while signed in as the administrator.

One administrator signs in to manage it. You can add one attendance-only user who can take attendance and nothing else.

Use a strong password, do not share the administrator sign-in, keep the kiosk phone in a controlled place, and use the attendance-only user for day-to-day punching.

Tap Forgot password? on the sign-in screen and follow the email we send.

Only what attendance needs. The Privacy Policy lists every item and why.

To register faces and recognise them when employees punch.

Only if you record GPS positions or restrict punching to your workplace. It is not used otherwise, and never in the background.

No. Features that need a permission you refused will not work; everything else does.

Yes. The administrator can request deletion in the app or on the Account Deletion page. Data is permanently deleted after 30 days, and the request can be cancelled until then. Check your own record-keeping duties before deleting attendance.

Close and reopen it, restart the phone, and update the app from Google Play. If it still fails, email elixirinfotechindia@gmail.com.

Check the camera permission, close other apps using the camera, clean the lens, and restart the phone.

Check the repeat-punch delay, the workplace radius and location permission, automatic date and time, the punch mode, and that the face is registered.

Turn on location services, allow the app location access, and punch from inside the workplace radius set in Settings › Workplace & GPS.

Move to even light, face the camera straight on, and hold the phone steady. If it stays slow, register the face again.

Check the day's punches, the employee's shift (hours, grace, break, overtime), and whether the day is a holiday or weekly off.

Email elixirinfotechindia@gmail.com with your organization name, the phone model, the app version (Settings), what happened, and a screenshot if you can. Never send your password.

Android phones and tablets running Android 7.0 or later, with a front camera. The app is available in 13 languages.