Track Every Spare Key, PIN and Guest Code in One Secure Access Log

1. Purpose of This Log and How to Use It

This log helps a household record which physical keys and digital access codes have been issued, who currently holds them, when access starts, when it should end, and whether it is still active. Complete it as accurately as you can, store it somewhere private, and update it whenever access is granted, changed or withdrawn. The wording here is general and neutral — adapt it to your own household routines and preferences.

Tip: avoid writing actual PINs, codes or precise hiding places directly into a shared document. Record where the secret is stored instead, and share the secret itself only through a channel you trust.


Name of this log (so you can recognise it later)

Date this log was created

Who will mainly maintain this log?


2. Household & Property Overview

Property nickname or address label used in this log

Property type


How many exterior doors or gates use a key, fob or keypad?

Which entry points are covered by this log?


Is there a secondary dwelling or guest suite with its own entrance?


Does a neighbour, caretaker or building staff hold any standing access to the property?


3. Primary Contact & Notification Preferences

Primary contact name

Preferred phone number

Email address


Is there a co-owner or co-manager who may also grant or withdraw access?


How would you like to be told when access is granted, extended or revoked?

Backup contact details for use when you are away or unreachable

Best time of day to reach the primary contact

4. Physical Key Inventory

List the physical keys you control so you always know how many copies exist and where each one is.


Which kinds of physical keys or fobs are tracked here?


Total number of spare house keys currently issued to people outside the household

Total number of spare house keys kept at home as unissued backups

Where is the main unissued spare key kept?


Are any keys or fobs marked with your address or household name?


Have you ever had a key copied by someone without your approval?


Anything else worth noting about your physical keys

5. Digital Access: Keypads, PINs and Smart Lock Codes

Digital codes are convenient because they can be created and removed without changing a lock, but they are only useful if each code has a clear owner and a clear end date.


Which digital access methods are in use at the property?


Does your keypad or smart lock support codes that expire automatically?


Where are active PINs and codes recorded?

Is the same code used by more than one person or for more than one door?


How often do you change or rotate keypad codes?

Typical number of digits in a guest code you issue

Can you lock or unlock the property remotely from a phone or computer?


Any other notes about digital access

6. Access Log: Keys, PINs and Guest Codes Issued

Add one row for every key, fob, PIN or guest code that has been given out. Use the Status column to show whether access is Active, Pending deactivation, Expired, Returned, Lost or Revoked. The final column estimates how many days remain before the deactivation date, which can help you plan ahead.


Spare Key & Digital Access Log

Key/Access Type

Holder/Assignee Name

Date Given/Activated

Expiration / Deactivation Date

Status

Access Scope/Notes

Days Until Expiry

Physical Brass Key
Neighbor Dan
4/12/2026
12/31/2026
Active
Front door spare key, used for plant watering while away
43
Garage Keypad PIN
Dog Walker (Priya)
5/2/2026
8/31/2026
Active
Weekday midday visits only; garage service door
-79
Smart Lock Guest Code
Sister (Maya)
3/15/2026
6/30/2026
Pending deactivation
Guest suite access during a family stay
-141
Physical Brass Key
House Cleaner (Luis)
11/1/2025
2/28/2026
Returned
Key returned and destroyed; no further access
-263
Garage Keypad PIN
Contractor (renovation crew)
2/10/2026
3/15/2026
Revoked
Code deleted after work completed
-248
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

How many rows in the log are currently marked Active?

Is every active entry in the table linked to a named individual?


7. Holder/Assignee Profile

Use this section for each person who currently holds access. If several people hold access, copy this section or repeat the answers for each one.


Full name of the holder

Relationship to the household


Best way to contact this holder

Who recommended or vouched for this holder?

Has the holder agreed in writing to the scope and end date of their access?


What is this holder permitted to do while using their access?


Any limits on this holder's access (days, times, rooms, alarm use)

Does this holder also have access to any neighbouring or related property of yours?


8. Access Rules & Boundaries

May a holder pass their key or code on to anyone else?


Are any rooms or areas off-limits to people holding spare access?


Are holders expected to arm or disarm an alarm when they enter?


Which house rules are shared with holders?


Please rate how well the following statements describe your household right now

Strongly disagree

Disagree

Neutral

Agree

Strongly agree

Every holder knows exactly what their access covers

Every holder knows when their access ends

Holders know who to contact in an emergency

Keys and codes are returned or removed promptly when no longer needed

Codes and key locations are kept confidential

This access log is reviewed on a regular schedule

House rules or expectations you would like to add

9. Key Handling & Everyday Security Habits

Which precautions do you currently follow?


How are spare keys usually handed over?


Do you keep a photo or record of each key so it can be identified later?


How confident are you that every issued key and code is currently accounted for?

Overall, how organised would you say your key and code management is today?

Where is this log stored, and who can see it?

10. Incidents, Lost Keys & Revocation

In the past twelve months, has any key, fob, PIN or code been lost, stolen or shared without your knowledge?


Have you ever had to rekey a lock, replace a lock or delete a code because of a concern?


If a key went missing tomorrow, what would your first step be?


Date of the most recent access review

Immediate steps to take if a key or code is believed to be compromised

Incident notes or lessons learned

11. Review Schedule, Confirmation & Sign-off

How often will you review this access log?

Next scheduled review date

What should be checked at each review?

I confirm that the information recorded in this log is accurate to the best of my knowledge

I understand that this log should be stored privately and shared only with people I trust

I agree to review the log according to the schedule chosen above and to remove access promptly when it is no longer needed

Name of the person completing this log

Signature

Date of signature

Final comments, reminders or follow-up actions

Analysis for Spare House Key & Digital Keypad Access Log for Homeowners

Important Note:

This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.

AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.

This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.

Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.



Overall Summary

The Spare House Key & Digital Keypad Access Log for Homeowners is a thoughtfully structured household record-keeping tool that brings together physical key tracking, digital code management, holder profiles, access rules, security habits and incident history into a single document. Its strongest design qualities are the clear separation of concerns across sections, the use of conditional follow-ups that keep the form short when a topic does not apply, and the inclusion of a central access table with a calculated expiry countdown. The form is written in neutral, non-legalistic language and repeatedly encourages the user to adapt it to their own routines, which makes it approachable for a general homeowner audience. A few areas could be tightened — most notably the repetition of similar free-text fields in the Holder/Assignee Profile section when multiple holders exist, and the reliance on open text for the Status column where a fixed option list might reduce inconsistency — but overall the form balances depth with usability effectively.


Purpose of This Log and How to Use It

This opening section sets expectations and establishes the administrative identity of the document. It is a good operational choice to explain up front how the log should be maintained and stored, because it frames every later answer as part of an ongoing record rather than a one-off questionnaire.


Name of this log (so you can recognise it later) — This field gives the document a recognisable label so that a household holding more than one property or more than one log can tell them apart. It supports basic record organisation and retrieval.


Date this log was created — Recording a creation date establishes a baseline for the document and makes later review cycles easier to interpret. It is left optional here, which keeps the opening friction low.


Who will mainly maintain this log? — Assigning clear ownership of maintenance is a practical way to reduce the risk that the record goes stale. The conditional follow-up for the Other option correctly captures a free-text role description without forcing every respondent through an extra field.


Household & Property Overview

This section scopes the physical perimeter that the log covers, which is essential context for interpreting every later key or code entry.


Property nickname or address label used in this log — A short label links all subsequent entries to one property and is especially useful in multi-property households. Asking for a nickname rather than a full street address is a sensible, privacy-conscious choice.


Property type — Property type helps the reader understand the likely number and arrangement of entry points. The Other follow-up allows for unusual configurations such as mixed live-work units.


How many exterior doors or gates use a key, fob or keypad? — A simple count gives an immediate sense of the scale of the access surface being managed and provides a sanity check against the entry-point list that follows.


Which entry points are covered by this log? — Selecting from a broad list of common entry points (front door, garage service door, garden gate, mailbox and so on) produces consistent, comparable data and makes it easy to spot an entry point that has been overlooked. The Other follow-up captures less common cases.


Is there a secondary dwelling or guest suite with its own entrance? — A secondary entrance often carries its own access credentials and can easily be missed. The conditional follow-up asks for the entry method and tracking approach only when relevant.


Does a neighbour, caretaker or building staff hold any standing access to the property? — Standing third-party access is one of the most common sources of forgotten credentials, so surfacing it early is operationally useful.


Primary Contact & Notification Preferences

This section establishes who is accountable for the log and how that person prefers to be told about access changes.


Primary contact name — Identifying a single point of contact makes it clear who should act when access needs to be granted, extended or withdrawn.


Preferred phone number and Email address — These provide direct channels for routine notifications. Both are left optional, which is a reasonable choice for a personal household document, though a respondent who leaves both blank may find follow-up harder.


Is there a co-owner or co-manager who may also grant or withdraw access? — Knowing who else can authorise changes helps prevent conflicting instructions to a holder. The follow-up correctly asks for contact details only when a second authorised person exists.


How would you like to be told when access is granted, extended or revoked? — Capturing notification preference supports timely communication and reflects the reality that households use very different channels.


Backup contact details for use when you are away or unreachable — A fallback contact is a practical continuity measure, particularly for households that travel.


Best time of day to reach the primary contact — A light-touch scheduling field that helps anyone reading the log understand when a response is realistic.


Physical Key Inventory

This section moves from context to concrete inventory and is one of the form's strongest areas.


Which kinds of physical keys or fobs are tracked here? — A broad checklist covering brass keys, restricted keys, fobs, padlock keys, remotes and alarm keys produces a consistent inventory vocabulary. The Other follow-up accommodates unusual key profiles.


Total number of spare house keys currently issued to people outside the household — A headline count of issued keys is a quick indicator of exposure and is easy to compare across review cycles.


Total number of spare house keys kept at home as unissued backups — Distinguishing issued keys from unissued backups is a useful distinction that many informal logs blur.


Where is the main unissued spare key kept? — Recording the storage location (without the code) supports recovery planning. The conditional follow-up for the lockbox option explicitly asks the respondent not to include the code, which is a well-judged privacy prompt.


Are any keys or fobs marked with your address or household name? — This question surfaces a practical risk factor. The no branch provides a short, informative note rather than leaving the respondent with nothing, which is a nice touch of guidance.


Have you ever had a key copied by someone without your approval? — Asking about unauthorised copies gives context for why a lock may have been rekeyed and encourages the respondent to record the remedial action taken.


Anything else worth noting about your physical keys — An open catch-all for details such as differing key profiles that structured fields would not capture.


Digital Access: Keypads, PINs and Smart Lock Codes

This section mirrors the physical inventory for digital credentials and recognises that codes have different lifecycles from keys.


Which digital access methods are in use at the property? — Listing keypad PINs, guest codes, intercom codes, alarm codes, temporary digital keys and app-based unlock covers the main categories a modern household is likely to encounter.


Does your keypad or smart lock support codes that expire automatically? — Understanding whether expiry is automatic or manual determines how much calendar discipline the household needs. The no branch offers a proportionate suggestion about setting a reminder.


Where are active PINs and codes recorded? — Pointing to a storage location rather than the secret itself is consistent with the guidance given at the top of the form and is a sensible data-minimisation approach.


Is the same code used by more than one person or for more than one door? — Shared codes complicate revocation, so identifying them is operationally valuable.


How often do you change or rotate keypad codes? — Rotation frequency is a useful indicator of how current the credentials are likely to be.


Typical number of digits in a guest code you issue — A small technical detail that can help when estimating how quickly a code could be guessed or shared informally.


Can you lock or unlock the property remotely from a phone or computer? — Remote capability changes both convenience and exposure. The follow-up checklist covers the main functions a remote account typically provides.


Any other notes about digital access — A catch-all for maintenance habits such as battery replacement schedules.


Access Log: Keys, PINs and Guest Codes Issued

This is the operational heart of the form and the element most directly aligned with the stated purpose.


Spare Key & Digital Access Log — The table captures the five data points named in the form's brief — Key/Access Type, Holder/Assignee Name, Date Given/Activated, Expiration/Deactivation Date and Status — and adds two useful extras: an Access Scope/Notes column for context and a Days Until Expiry column that is calculated from the deactivation date using a formula. The worked example rows demonstrate a realistic mix of active, pending, returned and revoked entries, which helps the user understand the intended vocabulary.


How many rows in the log are currently marked Active? — A quick tally that gives an at-a-glance measure of current exposure.


Is every active entry in the table linked to a named individual? — This is a good accountability check. The no branch asks which entries lack a holder and how the gap will be resolved, turning a simple yes/no into an actionable follow-up.


Holder/Assignee Profile

This section collects per-person detail and is designed to be repeated for each holder.


Full name of the holder — Naming each holder is the foundation of the whole record and makes later revocation straightforward.


Relationship to the household — A structured relationship list (family, neighbour, pet care, cleaner, contractor, tenant and so on) produces consistent categories for later filtering.


Best way to contact this holder — Contact details for the holder are needed to arrange handover, extension or return.


Who recommended or vouched for this holder? — A light-touch provenance question that adds context without being intrusive.


Has the holder agreed in writing to the scope and end date of their access? — Asking about written agreement, with an optional file upload and a gentle note in the no branch, supports clarity of expectations. The form does not overstate this as a legal requirement, which is appropriate.


What is this holder permitted to do while using their access? — A permitted-activity checklist makes the scope of access concrete and reviewable.


Any limits on this holder's access (days, times, rooms, alarm use) — Free-text limits capture the nuances that a checklist cannot.


Does this holder also have access to any neighbouring or related property of yours? — Cross-property access is easy to lose track of, so surfacing it here is a sensible safeguard.


Access Rules & Boundaries

This section turns individual holder records into a consistent household policy.


May a holder pass their key or code on to anyone else? — Onward sharing is one of the fastest ways a credential list becomes inaccurate, so an explicit policy is valuable. The conditional follow-up for prior approval asks how such requests should be recorded.


Are any rooms or areas off-limits to people holding spare access? — Off-limits areas are a practical boundary that is often communicated informally; recording them makes the expectation explicit.


Are holders expected to arm or disarm an alarm when they enter? — Alarm handling is closely tied to physical access and deserves its own question. The follow-up asks how the alarm code is shared and rotated.


Which house rules are shared with holders? — A checklist of common household rules, with an emergency-procedure follow-up, keeps expectations in one place.


Please rate how well the following statements describe your household right now — This matrix rating is a useful self-assessment covering holder awareness of scope and end dates, emergency contacts, prompt return of keys, confidentiality and regular review. It gives the respondent a quick sense of where their process is strong or weak.


House rules or expectations you would like to add — A free-text close for anything the checklist missed.


Key Handling & Everyday Security Habits

This section captures routine habits rather than one-off facts, which is a good complement to the inventory sections.


Which precautions do you currently follow? — A checklist of practical precautions (no address markings, controlled copying, prompt destruction of returned keys, rekeying after loss and so on) lets the household see at a glance which habits are in place. The None of the above follow-up invites the respondent to name a starting point, which is encouraging rather than judgemental.


How are spare keys usually handed over? — Handover method affects both convenience and exposure; the lockbox follow-up asks how the code is shared and rotated.


Do you keep a photo or record of each key so it can be identified later? — The optional image upload is paired with a reminder to blur identifying details, and the no branch offers a lighter alternative (tag colour and lock description), which is well judged.


How confident are you that every issued key and code is currently accounted for? and Overall, how organised would you say your key and code management is today? — Two short rating questions that provide a simple before-and-after measure of the household's confidence.


Where is this log stored, and who can see it? — Recording storage and access arrangements for the log itself closes the loop on the privacy guidance given earlier.


Incidents, Lost Keys & Revocation

This section provides a structured place for the events that most often force a change to the access list.


In the past twelve months, has any key, fob, PIN or code been lost, stolen or shared without your knowledge? — A yes/no screen with a detailed follow-up keeps the section short for households with no incidents while capturing full context when something has happened.


Have you ever had to rekey a lock, replace a lock or delete a code because of a concern? — Recording the remedial action taken (rekey, replace, delete code, change alarm code, pause access) produces a useful history.


If a key went missing tomorrow, what would your first step be? — A forward-looking question that encourages the household to think through its response in advance. The follow-up for the rekey option asks who would perform the work.


Date of the most recent access review — Anchors the review cycle described in the final section.


Immediate steps to take if a key or code is believed to be compromised and Incident notes or lessons learned — Two free-text fields that capture the household's own playbook and reflections.


Review Schedule, Confirmation & Sign-off

The closing section converts the log into a maintained process rather than a static document.


How often will you review this access log? — Choosing a review cadence sets an expectation of ongoing upkeep.


Next scheduled review date — A concrete date makes the cadence actionable.


What should be checked at each review? — A checklist of review items (holder entitlement, expiry accuracy, removal of returned keys, deletion of expired codes, contact details, secure storage) gives the reviewer a clear agenda.


I confirm that the information recorded in this log is accurate to the best of my knowledge, I understand that this log should be stored privately and shared only with people I trust and I agree to review the log according to the schedule chosen above and to remove access promptly when it is no longer needed — Three confirmation checkboxes that record the respondent's acknowledgement of accuracy, privacy and upkeep. These are framed as personal confirmations rather than legal attestations, which suits the informal household context.


Name of the person completing this log, Signature and Date of signature — A conventional sign-off block that identifies who prepared the record and when.


Final comments, reminders or follow-up actions — A closing free-text field for outstanding items, which is a practical way to carry action points forward to the next review.


Strengths and Areas for Improvement

Strengths. The form covers the full lifecycle of household access — issuance, scope, monitoring, review and revocation — in a logical order. Conditional follow-ups are used consistently and appropriately, so respondents only see detail that applies to them. The central table is well designed, combining free-text and date columns with a calculated expiry countdown and worked example rows. Guidance notes are proportionate and practical, particularly the reminders about not recording actual PINs or codes and about blurring identifying details in uploaded images. The tone is neutral and adaptable throughout.


Areas for improvement. The Status column in the access table is currently an open single-line text field; offering a fixed set of values (for example Active, Pending deactivation, Expired, Returned, Lost, Revoked) would make entries more consistent and easier to filter. The Holder/Assignee Profile section is designed to be repeated manually for each holder, which works but may become cumbersome for households with many holders; a note about how many times to repeat it, or a small count field, could help. A few optional contact fields in the Primary Contact section might reasonably be promoted or given a short note explaining when they become important. Finally, the form is quite long, and while the section structure mitigates this well, a short progress indicator or section index could further reduce perceived effort on screen.


Mandatory Question Analysis for Spare House Key & Digital Keypad Access Log for Homeowners

Important Note:

This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.

Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.

Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.

Please delete this section before publishing your form. See our Terms of Service for further information.


Mandatory Question Analysis

Name of this log (so you can recognise it later)
Recommendation: Requiring a log name supports basic document identification and retrieval, particularly for households that maintain separate records for more than one property or location. A short, recognisable label makes it easier to file, find and reference the record later. The specific naming convention is a matter of household preference, so the form appropriately leaves the format open.


Property nickname or address label used in this log
Recommendation: Marking this field as required ensures every subsequent key and code entry can be associated with a specific property. It supports consistent record-keeping and reduces the chance of entries being mixed up between locations. Because the field asks for a nickname or label rather than a full address, it also aligns with a data-minimisation approach to the information stored in the log.


How many exterior doors or gates use a key, fob or keypad?
Recommendation: Requiring a numeric count of secured entry points provides a quick measure of the access surface being managed and helps the reader interpret the entry-point checklist that follows. It also gives a simple reference figure for later reviews. Whether this count needs to be exact or approximate depends on how the household intends to use the log.


Primary contact name
Recommendation: Identifying a primary contact as required establishes clear ownership of the record and makes it obvious who should be approached when access is granted, extended or withdrawn. It supports timely operational follow-up and reduces ambiguity when more than one household member is involved. The form does not prescribe a particular format for the name, which is appropriate for a personal household document.


Total number of spare house keys currently issued to people outside the household
Recommendation: Requiring this headline count gives an immediate indication of how many credentials are currently outside the home and provides a baseline that can be compared at each review. It is a simple, low-effort field that supports quick monitoring. Households that prefer not to track an exact figure may still find a rounded estimate useful.


Where are active PINs and codes recorded?
Recommendation: Requiring a storage location for active codes — rather than the codes themselves — supports continuity if the primary contact is unavailable and is consistent with the form's guidance to avoid writing secrets into a shared document. It prompts the respondent to think about where sensitive details are kept. The appropriate storage method will vary between households and is left to their discretion.


Full name of the holder
Recommendation: Requiring a holder name is central to the purpose of the log, because every key or code entry needs to be traceable to a person in order to be reviewed or revoked efficiently. It supports accountability and makes follow-up straightforward. The form appropriately allows for informal names or roles where a full legal name is not necessary.


Best way to contact this holder
Recommendation: Marking holder contact details as required supports practical coordination around handover, extension or return of access. It ensures that the household can reach the holder without searching elsewhere. The field accepts a range of contact methods, which reflects the variety of ways households communicate with service providers, relatives and neighbours.


Name of the person completing this log
Recommendation: Requiring the name of the person completing the log records who prepared the information and provides a point of reference for later questions or corrections. It complements the signature and date fields in the sign-off block. Whether a first name alone or a fuller identifier is needed depends on how the household intends to use the record.


Date of signature
Recommendation: Requiring the signature date anchors the record at a point in time and makes it easier to judge how current the information is at a later review. It pairs naturally with the signature field and the review schedule chosen earlier in the form. The date format is left to the respondent, which suits an informal household context.


Overall Mandatory Field Strategy Recommendation

The form limits its required fields to ten questions spread across the document, which is a proportionate approach for a form of this length and depth. The mandatory set concentrates on document identity, property identification, headline exposure figures, primary and holder contact points, and the closing sign-off — in other words, the minimum information needed for the log to function as a usable record rather than a set of disconnected answers.


  • Balance depth against completion. The form collects a large amount of optional detail across ten sections. Keeping the majority of these fields optional is a sensible way to protect completion rates while still allowing a thorough respondent to provide full context. Consider whether any currently optional field is genuinely necessary for the household's intended use before promoting it to required.

  • Use conditional logic to limit detail. The form already uses conditional follow-ups effectively — for example, the lockbox location prompt appears only when a lockbox is selected, and the alarm-sharing prompt appears only when alarm duties apply. Extending this pattern to the Holder/Assignee Profile section, so that only fields relevant to the holder's role are shown, could further reduce effort.

  • Placement and grouping. The mandatory fields are reasonably distributed, with three in the opening and overview area, four in the middle operational sections and three in the closing sign-off block. This spread avoids a long run of required questions at any single point. The two required holder fields sit together within a section that is designed to be repeated, which is logical but means the respondent meets them once per holder.

  • Repetition considerations. Because the Holder/Assignee Profile is intended to be completed for each person holding access, the required fields within it will be encountered multiple times. If the household has many holders, this repetition may become tedious; a brief note about how many times the section should be repeated, or a count of holders at the start of the section, could help respondents plan their effort.

  • Periodic review. As with any record-keeping form, it is worth revisiting the required field set periodically in light of how the log is actually used. If certain optional fields are consistently completed, they may be candidates for promotion; conversely, if a required field is frequently left at a default or placeholder value, its necessity may warrant reconsideration.


Overall, the required field selection supports the form's purpose of producing a complete, attributable and maintainable access record without placing an excessive burden on the respondent. The remaining optional fields provide depth for households that want it while keeping the minimum viable completion relatively light.


Don't see the calculations that make your data do a happy chicken dance? With Zapof, you can create forms with tables that automatically crunch the numbers like a digital hamster on a tiny abacus!
This form is protected by Google reCAPTCHA. Privacy - Terms.
 
Powered by Zapof